Page Comparison

T-ODS Snapshot capability: What is the anticipated periodicity of snapshots?

A total of 8 snapshots per year

Initially we plan two distinct snapshots, Fall and End of Year. 

• However, each of those snapshots occurs once per month for 4 months per year: October, November, December, January
• Those snapshots will be taken concurrently for two years of data: Fall snapshots from the Current Year ODS and End-of-Year snapshots from the Prior Year ODS.

A total of 18 different snapshots per year

• Florida State Reporting Periods (There are 17 periods)
• End of Year

 We currently have 2 years of daily historical data for our Synergy SIS, but we have not yet determined the feasibility of using this data. 

This data does allow us to pull any point, such as Term, Semester, EOYr, 10th day, 40th day, 100th day or other points

T-ODS query: Do you anticipate querying temporal data natively (via SQL queries) ,through an application, or both?

Both.

• SQL Queries/Stored Procedures for Data Quality System
• Applications:
• PowerBI for EWS Project
• Tableau for HCMS Project

Both.

SQL queries and API calls from another application

 Both.

• We us Power BI and SSRS to access our current DW and hope this to eventually be one stop for all data reporting.

T-Bulk: Is bulk-load of prior years of data required?

If so, are you able to produce or acquire prior year data in Ed-Fi XML format?

No.

For the current project vision, no, we do not need bulk-load of prior year of data.  The T-ODS will be used for creating snapshots from which downstream data warehouses and data marts will be populated.

If our project vision changed to include bulk-load of prior years’ data into the T-ODS, it will likely not be for at least 5 years.

Yes.

We are bulk-loading prior years of data, and yes, we are able to produce these data in Ed-Fi XML format

Do you anticipate needing to modify temporal data?

If yes, indicate how/where you anticipate performing the modification

 Yes.

• Use Case: Districts occasionally have to return to previous year data in the SIS to update grade changes, GPA’s, and Credits Earned
• Business Process: It would be great if the district was able to make the update in the SIS and the SIS update then gets sent to the T-ODS. However, we would also be able to submit a manual change through SQL scripts if the district were to submit a help ticket to our Help Desk
• Domains of Data: Student Grades
• Additional Info: FLDOE DOE Reporting Presentation
  

Probably so...but we are not yet certain. One case where we anticipate needing to modify the temporal data is delayed entry of compliance based data. For instance, most compliance data in Oklahoma is reported as of October 1. In the event that a student has been tested and qualifies as an English Language Learner but that data is not in the source system, it will be important to be able to add that data in to be reflected on the tested date (not the entry date) in order to make sure compliance reporting is accurate and to make sure the correct $ amount is received from the state (assuming reporting is done through the ODS).

How/where update would be made: Via ODS/API. The current process is that these changes are updated in our source system. In an ideal state, the update in the source system would trigger a change in the ODS but this may have unintended consequences.

 No.

We would like to support point in time/repeatable results type data sets.

•  We have reached out to Wisconsin to evaluate the multi-year modifications that they made to the ODS
• We have considered simply using a new instance of the ODS for each new school year. (We hope that the T-ODS will be a usable alternative to using this approach)

As mentioned above we have historical-lized the complete Synergy database (300GB of non-image data). 

The method used was dynamically built merge statements using Effective Begin and End Dates with current row identified as Effective End Date of 29990101.