...
Analytics Middle Tier 2.0 is becoming a full citizen in the Ed-Fi platform in 2020, rather than just a proof-of-concept on the Ed-Fi Exchange. As it grows up, it needs to correct some architectural concerns that came up as feedback from the field. It also needs to be up to par with the latest release of the ODS/API, version 3.3. This document aims to inform about the challenges and elicit feedback on the utility of the proposed solutions.
...
The demographics on the view are secondary to the student-school relationship. A data analyst might naturally look for school enrollment data. Therefore we will have a new view called StudentEnrollment to show active enrollment/school association information, with a StudentEnrollmentKey that combines the StudentUniqueId and SchoolId (maintaining the principal of needing only one column for a join). The early warning views would then change to use the single StudentEnrollmentKey instead of in addition to the two separate StudentKey and SchoolKey columns. The original keys are retained to facilitate aggregating by student or school.
The StudentDimension would continue to exist in a reduced form, providing only name and primary contact information. The Program views would continue to have the StudentKey in them.<create diagrams here>
Gliffy name StudentEnrollmentDimension pagePin 3
Problem
What if someone wants to build queries that analyze program participation by demographic data?
...