TAG Meeting 2015-11-11

Roadmap Discussion

Dan Retzlaf
Don Dailey
Duy Nguyen
Geoff McElhanon
Mark Reichert
Mark Walls
Matt Warden
Neal Schuh
Chris Moffat
Itzel Torres
Eric Jansson

Auditing capabilities - time spent diagnosing transmission issues and problems is large, and generates need for subsequent software development, and creates re-submission of data
- visual tools for auditing data transfers; validation is important for clients submitting data as well
- one possibility is via publishing an API with audit results
- related: more robust error messages for failures
Scalability of the software solution
- performance: how long it takes to get data into the ODS
- unclear community benchmarks - creation of benchmarks would help set clear expectations for implementations; for this strategy, define a baseline architecture that numbers are based on
- XML bulk load and the multi-pass strategy to populating the data slows loading: to build up dependencies, files often need to be processed several times; some success in publishing best practices on how to submit data in what order
Longitudinal ODS features - lack of clarity on this in the market today

Certification process for vendors: how to get vendors certified at a standard level, so that agency certifications can focus on local extensions

How can we make it clear to vendors the immediate business value - key to ecosystem growth
- because the size of the problem Ed-Fi addresses, its hard to clearly see value of Ed-Fi
- define profiles of use cases and clearly explain each - keep them simple and discrete
- tie to end-user benefits, as that value drives the market
- "chicken and egg" problem of ecosystems: have to try and do the supply and demand simultaneously
Security and privacy concerns - how to implement Ed-Fi securely - could use guidelines on this

Support for HTTP PATCH would solve the problem of having to read records and then write them back to avoid loss of data. Profiles will help here, but those were not designed to solve this problem