How to Use the Student Dimensions
Overview
There are two dimensions in the Core View
Collection that provide lists of
students: StudentSchoolDim
View and
StudentLocalEducationAgencyDim
View.
These dimension provide student names and a few key demographic values with
cardinality of one (e.g., student recorded with a single "sex"). For demographic
information with cardinality "many" (e.g., student record with multiple tribal
affiliations or multiple languages), the Core Collection provides
a DemographicsDim
and two bridge views that link the student dimensions to
the demographic dimension: StudentSchoolDemographicsBridge
View
and StudentLocalEducationAgencyDemo.
This article illustrates the relationships between these views and demonstrates
realistic usage scenarios.
Design Note
Why are there two similar views (StudentSchoolDim
View and
StudentLocalEducationAgencyDim
View),
instead of a single StudentDim
?
- We wanted to include demographic / enrollment information directly in the Student dimension.
- In the Ed-Fi Data Standard v3.x, demographic information can be recorded either on the school relationship or the local education agency (LEA) relationship.
- To create a single view, we would have to coalesce the data, choosing either the school or LEA information as the primary information.
- Which one is primary? It depends on the implementation. → Combining into a single view would oversimplify the necessary complexity in the Ed-Fi ODS database and lead to incorrect results in some implementations.
In short, we decided that it's better to be transparent than to disguise this challenging point.
The sample queries and results below are based on the Glendale sample database. The article provides a few simple examples of what can be done with the views, but not all facets are explored.