Stephen A. Fuqua

Tech Congress 2025 is just over a month away and Project Tanager Milestone 0.4.0 has been reached. Can you help us show off what it is (or might be) capable of?

Think of this as a call for posters. If you're not familiar with academic conferences and posters... then maybe you can imagine a science fair board. Do something cool, show it off in a few words and some pictures, and you get a few minutes to narrate for your audience. Complete your "poster" before April 17 so that I have time to incorporate it into a slide deck for an April 23 Tech Congress session showing off the Data Management Service in Action.

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.

What's Changed​

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:

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.

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.