Details
-
Story
-
Resolution: Done
-
Major
-
TPDM v0.8, TPDM v1.0.0
-
None
Description
The Period reference in the EducationOrganizationIndicator entity has the following description: "The time period or as-of date for the indicator." with the referenced element definition being: "The time period for which the information is applicable or effective.". Consequently, it's clear the model doesn't support longitudinal information for Indicators but merely indicate the data's timeframe.
CSU's TPDM implementation requires keeping Indicator longitudinal information in a multi-year ODS, leading to the only possible workaround of creating school-year dependent Indicator descriptors, which increases the querying complexity.
The following are examples of high priority data elements being mapped to TeacherCandidate.Indicators that CSU would like to track trends through time:
- Student Standing: e.g. pursuing admission to credential program, admitted to credential program
- Enrollment Status: e.g. first-time freshman, transfer student, continuing student
- Credential Emphasis: many values, could change over course of study
- Added authorizations: many values, could change over course of study
- Credential Status Value: e.g. in the pipeline to a credential program, enrolled in a credential program
- Center: status as studying at an off-campus center or not
- Credential Class Level: e.g. preliminary, intern, can change over course of study
Note: The proposed path forward from the implementation team is to make Begin date in the TeacherCandidate.Indicator a part of the key so repeating values in a different time period would not be overwritten. The "BeginDate" is currently being generated for all these indicators so there is low/no risk of data loss from missing this data.
The CSU implementation is a TPDM v0.8 version https://schema.ed-fi.org/tpdm-handbook-v08/Ed-Fi-Data-Handbook-Index.html#/TeacherCandidateIndicator
Data use scenarios:
- Many/most of these high priority indicators will be displayed on the Candidate Profile page, and the filters for that page allows the user to filter by year/term. The data displayed for a given year/term selected should reflect the values for the candidate at that year/term, rather than their most current values.
- Some of these fields will likely be displayed or used for disaggregation on the Certifications/Credentials Recommendations page. We haven't done the use case definition or UI work for that page yet.
- There are non-dashboard research use cases for most of the EducationOrganizationIndicator fields that we would use the ODS data to support: e.g.:
a. What percentage of our candidates started as transfer students (so we would need to know that they were transfer students at one point in time, and not have that value overwritten as 'continuing student')?
b. What proportion of students with a cred stat value of 'in the pipeline to a credential program' eventually join the program?
c. What proportion of our candidates spend a portion of their studies at an off-campus center at some point in time?
Attachments
Issue Links
- relates to
-
TPDMX-233 Candidate Indicator on CandidateEducatorPreparationProgramAssociation needs to be a collection
- Scheduled for Release
-
DATASTD-1561 Need to support ELL status and proficiency changes multiple time in a school year
- In Development
-
TPDMX-233 Candidate Indicator on CandidateEducatorPreparationProgramAssociation needs to be a collection
- Scheduled for Release
-
TPDMX-188 EducationOrganizationIndicator - Longitudinal use case
- Closed
-
TPDMX-202 Deep dive in multi year ODS for TPDM
- Closed