Update Best Practices for School Calendar Domain
Description
relates to
Activity
Mustafa YilmazJune 11, 2024 at 1:24 PMEdited
The best practices documentation for the Enrollment domain in the ticket has been shared with the Ed-Fi Alliance team members for their review and feedback lately. I will reiterate it with the certification team members as suggested in your recommendation #2.
I have also updated the School Calendar Domain Best Practices UDM reference page with the changes in your recommendation #3.
Since the TimeType descriptor related work as requested for Data Standard team consideration is being tracked in another ticket, , I consider the ticket to be completed.
cc:
Edward ComerJune 10, 2024 at 4:19 PMEdited
The soon-to-be-published Best Practice document for Enrollment identifies the StudentSchoolAssociation.Calendar reference as being a MUST use, meaning that the intended use of the entity requires it to be used.
Recommend forwarding the Best Practice document for Enrollment to the certification team to consider incorporation of MUST have attributes into the SIS certification process.
Recommend the following edits to the Calendar Domain Best Practices:
Add to the bottom of the section Sessions, Grading Periods, Calendars, and Calendar Dates:
In order to provide a consistent granular specification of every student’s calendar, during enrollment the StudentSchoolAssociation.Calendar reference MUST be populated, whether the School has single or multiple calendars.Replace the second bullet under section Multiple Calendars:
When using individual (or small group) calendars, it is RECOMMENDED that the StudentSchoolAssociation.Calendar reference for a student be populated with the unique, individualized calendar, and not a school or grade level calendar. Such calendars SHOULD have a Calendar.CalendarType set to an appropriate descriptor value (e.g., "Student Specific" or "IEP") to ensure clarity on the scope and avoid confusion with a school or grade-level calendar.
Mustafa YilmazJune 4, 2024 at 6:33 PM
A new epic, TimeType Descriptor, created to have the comprehensive analysis of the second recommendation listed in the description. Please follow the related updates by that ticket, .
Mustafa YilmazJune 4, 2024 at 5:57 PMEdited
will create a separate ticket to for a comprehensive analysis of the current usage of time type data elements and their usage, then come up with a recommendation with a consideration if the requested change is a breaking change.
CC:
Muriel MarableJune 4, 2024 at 4:56 PMEdited
Calendar is currently an optional and not a required element.
Calendar is currently not part of the StudentSchoolAssociation certification scenario -
https://edfi.atlassian.net/wiki/spaces/EDFICERT/pages/23701002/v5+Student+Enrollment+StudentSchoolAssociation+Scenarios
Recommendation to add to best practices that every every StudentSchoolAssociation MUST have a CalendarReference . We would like to add this requirement to certification and would like the best practices to reflect this.
https://edfi.atlassian.net/wiki/spaces/EFDS5/pages/26707207/School+Calendar+Domain+-+Best+Practices
Recommendations to be considered
every StudentSchoolAssociation MUST have a CalendarReference
Rationale: By requiring that each student has a calendar reference, it forces the SIS to provide consistent granular view to the student – calendar relationships. This guarantees there will always be a consistent map between a student and calendar regardless of SIS implementation
adding timeType descriptor to the next data standard version.
Rationale: This will allow for regional variation in measurement of duration and provide downstream users clearer view of how to use the data correctly