Discover about the Ed-Fi Alliance's work in 2024 for seeking opportunities to strengthen the use of Unifying Data Model and reducing implementation and operation costs for vendors.
The gifts arrive early this week: we are excited to announce three important releases: Data Standard 5.2, ODS/API 7.3, and MetaEd 4.5. In semantic versioning these are minor updates (no breaking changes), but they include major new features. Read on for a quick summary.
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.
This second milestone on our way to a production-ready release of the Data Management Service adds full referential integrity handling to the basic validation support from the first milestone:
Prepare for the production release and Ed-Fi support for API Publisher v1.1 and including the following tickets into this release:
Access the code at tag 0.1.0
This first milestone release of the new Ed-Fi Data Management Service provides a PostgreSQL-backed Ed-Fi API with the following features:
The recent Ed-Fi blog post New Cloud-Native Functionality Coming to the Ed-Fi Alliance Technology Suite introduced a piece of software under active development, the Ed-Fi Data Management Service.
Eventually, this software will replace the Ed-Fi ODS/API Platform. Unsurprisingly, a few themes emerged in the questions and conversations at Ed-Fi Tech Congress 2024. We've begun addressing those in a new Frequently Asked Questions page in the Project Tanager repository. And we'll continue adding questions and answers on that page as they come upk.
Project Tanager, as explained in the project's readme, is a code name for the project to create new products, of which the Data Management Service will be the key component.
The Ed-Fi tech team has produced a lot of content over the years. Yet, we continue to face challenges with our documentation. On the one hand, discoverability and awareness seem to be low; on the other, our technical processes for managing the content are at odds with our typical daily workflows.