Details
-
Improvement
-
Resolution: Done
-
Minor
-
Data Standard v2.0
-
None
-
None
Description
In our SIS, we have what we call "Special Programs." This is an area for tracking various program enrollments or student statuses over a date range. Some examples are Early Childhood, Limited English Proficiency, and Homeless Status. This data is often needed for state reporting.
Our Special Programs match up with Ed-Fi's StudentProgramAssociations. However, most Special Programs have additional fields besides the date range. I feel it would be beneficial to allow StudentProgramAssociations to store additional attributes.
studentProgramAssociation { ... programAttributes: [ { programAttributeTypeDescriptor: [identify attribute type] programAttributeValue: [string] } ] }
This follows the pattern of the Student / identificationCodes array, which has a descriptor field to hold the type and a code field to hold the value. It also allows each state set up the attributes they need by adding descriptors, rather than by extending StudentProgramAssociation.
I'm sure that storing additional values this way is not as useful as having a real field for each value. So there will probably still be StudentProgramAssociation extensions. But I think this would at least reduce them.
Attachments
Issue Links
- relates to
-
DATASTD-1162 Expand federal program capture to drive state standardization and reduce field fragmentation
- Closed
-
DATASTD-1158 Add new subclasses of StudentProgramAssociation to cover federal programs
- Closed