Vinaya Mayya

Overview​

The Ed‑Fi Data Management Service (DMS) is evolving toward a relational backend, shaped by community feedback and real‑world implementation experience. Building on the proven Ed‑Fi ODS/API foundation, DMS modernizes the storage layer to address long‑standing operational challenges—such as wide composite keys and complex joins—through targeted structural changes.

By prioritizing a relational backend, DMS preserves the core strengths of the ODS: predictable schemas, strong referential integrity, and compatibility with relational tooling. The result is a service that feels familiar to teams with ODS experience and lowers the cognitive and migration cost of adoption.

What This Means for Implementers​

If you work directly with the ODS database today, DMS's data store will feel familiar, but with important structural differences:

• You still work with the same Ed‑Fi entities and natural keys
• Joins are simpler and narrower due to surrogate keys
• Person identity is clearer and no longer mediated by ODS-only integers
• Optional document caching can accelerate API reads

The sections below explain why these changes exist and how they affect database design and operations.

This post is written for database administrators, backend developers, data engineers, and solution architects who work with the Ed‑Fi ODS/API at the database level and are evaluating or planning a transition to DMS. Familiarity with the ODS schema and relational database concepts is assumed.

The Ed-Fi Alliance and 1EdTech® are working together to better align standards and simplify rostering across the K–12 EdTech ecosystem.

State, regional, and local education agencies, vendors, and managed service providers (MSPs) are asking for simpler, more consistent ways to roster students and provision learning tools at scale. Today, managing multiple rostering patterns across states and products introduces friction — and slows down onboarding at the moments when students and teachers need systems to “just work.”

The Ed‑Fi Alliance and 1EdTech® have partnered to address that challenge through a coordinated solution that brings OneRoster 1.2 capabilities directly into the Ed‑Fi ODS/API. As part of this effort, we are preparing the Ed-Fi OneRoster API release and subsequent enhancements in ODS/API 7.3.2. Together, these updates streamline deployment and security, making it easier than ever for agencies to provide a OneRoster-compliant endpoint using data they already have.

We’re excited to announce the 0.7 release milestone for the Ed-Fi Data Management Service (DMS).This release focuses on multi-tenancy foundations, operational cost optimizations, and improved performance for scalable deployments.

We are excited to announce the release of Ed-Fi ODS/API v7.3.1 and MetaEd 4.6. ODS/API v7.3.1 adds support for Data Standard 6.0, alongside existing support for versions 5.2 and 4.0. Below is a summary of what’s new.

We’re thrilled to announce the Release Candidate 1 / v0.6.0 release milestone for the Ed-Fi Data Management Service (DMS). This release introduces Swagger UI, template databases, and completes critical end-to-end and compatibility testing. It also lays the groundwork for smoother integration and a better developer experience.

We’re excited to announce the 0.5 release milestone for the Ed-Fi Data Management Service (DMS), marking another step forward on our path toward the upcoming Release Candidate 1. This release delivers key features to support authorization, extensibility, and interoperability.

With the recommendation to use the ODS for single year data collection and the announcement of end of support for the Migration Utility, we committed to delivering lightweight SQL migration scripts for non-breaking changes — and today, we’re delivering on that promise.

We are excited to announce the release of ODS-API Upgrade Scripts v1.0. Specifically, these scripts contain instructions and scripts for upgrading from Ed-Fi ODS/API version 7.1 to 7.2 and Ed-Fi ODS/API version 7.2 to 7.3, designed to streamline the upgrade process for your Ed-Fi ODS/API installations.

What's Changed​

The fourth milestone on our journey to a production-ready release of the Data Management Service (DMS) introduces Configuration Management Service backed by configuration data store, namespace-based authorization, and Keycloak integration as the identity provider.

In this video, we explore the new enhanced API error handling introduced in ODS / API 7.2. This update focuses on improving the clarity and consistency of error messages, making it easier for both end-users and developers to diagnose and resolve issues.