...
- Major points
- There is a growing need for ODS-to-ODS replication via API in the community, but the scale of that pattern is not yet clear.
- There is ambiguity about the best product supports to allow agencies to derive value from their ODS
- The dominant opinion of the participants is that the ODS database is not an effective analytics store, and that in many – if not most cases – the data will leave the ODS before analysis. The roadmap emphasis should therefore be on bulk data movement and replication
- This advice is counter to the advice of the former Data Out SIG, which encouraged the view that the ODS database was the analytics store.
- On the Analytics Middle Tier: seems useful as a way to support some basic analytics, but likely limited in utility for more mature implementations.
- There is evidence of performance issues for medium to large LEA implementations for the Suite 2 API, but Suite 3 API has not been tested.
- Prioritize development of regular (i.e. with each release) data out benchmarking for the ODS API.
- Default size should be at least a mid-sized school district, but comparison of performance at multiple scales is most desirable
- Include a benchmark that is a comparison of API extraction time to extraction via SQL time
- Focus on endpoints lest likely to scale due to large natural keys, significant denormalization in the database ORM, or other similar issues
- Action: TAG input captured here:
Jira Legacy server Ed-Fi Issue Tracker serverId e04b01cb-fd08-30cd-a7d6-c8f664ef7691 key ODS-2947