Details
-
Improvement
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
Summary of outcomes for Data Standard 3.2
- Problem Addressed: There was not a place to store a locally defined "Section Name" on the Section entity.
- High-level Reasoning: There are use cases where the SectionIdentifier and a section's name are not the same thing. It makes sense to add an optional element SectionName for these use cases.
- Changes Made: Added an optional element SectionName to Section.
Original ticket description follows:
Hello all,
I wanted to flag a data element that our districts will periodically have that we are unable to store for them. Some student information systems allow the customer to give a name to a class section. This is in addition to the section identifier. The sections API endpoint does not have a place to store the section name and so we are unable to store this element for the districts and schools that we support.
Marcos