Friday, April 8, 2022
10:30 AM - 11:45 AM | Many Ed-Fi implementations have started in a multi-year model where an ODS will store multiple years of data within the same database. As the community learns about the pros and cons of multi-year data ODSs, more implementations are moving towards single-year implementations to allow more flexibility in the database as necessary changes occur between each year in education programs. This session will discuss what is needed to transition from the multi-year model to a single-year model and best practices in those migrations. |
| Note |
|---|
These broad session notes attempt to capture the spirit of the discussion and should not be interpreted as a transcript. Although Ed-Fi Alliance staff were involved in capturing these observations, the notes below should not be construed as official, complete, or 100% accurate. |
The multi-year to single-year opened with a background on why the recommendation changed and transitioned into a summary of the resources available to support the single year ecosystem. During this discussion a few topics came up:
- challenges of running the Ods in a multi-year environment
- Multi-year support still exists. The only change is in the recommendation to single year. Future roadmap plans will likely optimize for single year
- Challenges of transitioning keeping multiple years in a single Ods and then single years afterwards. This challenge was mainly centered on the challenge of supporting vendors making the change.
- Support for the data migration tool independent of the single year recommendation
- AMT's existing support for single year Ods