Review model for MeetingTime

Summary of outcomes for Data Standard 3.0

• Problem Addressed: Prior to v3.0, the MeetingTime common type included properties that were later determined to pertain to (some of) the entities that referenced MeetingTime and not the Meeting Time itself. Additionally, BellSchedule contained a direct reference to MeetingTime and MeetingTime included a reference to ClassPeriod. This does not correctly reflect the real-life relationship between these entities.
• High-level Reasoning: By relocating the properties that are not specific to a MeetingTime to be referenced by the appropriate entities, MeetingTime now only contains properties that are relevant to each referencing entity. Additionally, by replacing the MeetingTime reference on BellSchedule with a collection of ClassPeriods and by reversing the cardinality between MeetingTime and ClassPeriod (such that ClassPeriods have MeetingTimes), the model now correctly depicts a BellSchedule as a collection of ClassPeriods, each having a collection of MeetingTimes.
• Changes Made:

• Move OfficialAttendancePeriod reference from MeetingTime to ClassPeriod.
• Move AlternateDayName reference from MeetingTime to BellSchedule.
• Remove ClassPeriod reference from MeetingTime and add a reference to MeetingTime on ClassPeriod (as an optional collection).
• Replace the MeetingTime reference on BellSchedule with a reference to ClassPeriod as a required collection.

Original ticket description follows:
Creating an issue to review the model for Meeting Time in the data model, and linking to a related issue in the ODS and MetaEd. Also attaching an in-depth discussion related to ODS-333 that suggests model changes to Meeting Time -