TAG Meeting 2021-06-28 - Subgroup on Data Standardization

Attendees

First Name	Last Name	Organization
Patrick	Devanney	ClassLink
Mindy	DuFault	Infinite Campus
LaQuinta	Extine	Leon County Schools
Jean-Francois	Guertin	EdWire
Eric	Jansson	Ed-Fi Alliance
Audrey	Shay	Wisconsin Department of Public Instruction
Sayee	Srinivasan	Ed-Fi Alliance
John	Watson	San Diego County Office of Education
Patrick	Yoho	InnovateEDU Inc

TAG review of issues in data standardization

See designs at: Data Model

Indicators with Option Sets discussion

Noted that updating the Period elements in this fashion can be awkward for API clients.
Noted that periods/dates are missing from many source systems, and discussion of if longitudinal tracking should be in the ODS/data model at all or part of some downstream system.
Some discussion that that could degrade the current use of descriptors by removing them from the schema
Action: design/show this as a model on its own / detached from StudentEdOrgAssociation

Longitudinal Indicators discussion

Much discussion of if it is bad for a system to invent dates
Some discussion that lack of all identity could degrade data quality, but also noted that the other designs also allow for inconsistent and conflicting date information to be stored
Action: show this as JSON (the model overlap with the first topic was confusing)

Designs for Flexible Referentiality

Major issue here is having the referent to be "flexible" / optional as part of the key. That should not be allowed.
Are there possibly error-reporting solutions?
Action: consider a design pattern that has a slimmed-down key and an optional reference (e.g., the LMS Toolkit section connection)