Relationship from Section to School Seems To Be Redundant

Summary of outcomes for Data Standard 2.1

• Problem Addressed: Section contains a required reference to School but CourseOffering (part of the identity) already contains a School reference.
• High-level Reasoning: The required direct reference to the domain entity School on the Section domain entity represents the school where the section is taught. However, the School reference in CourseOffering, which is part of the identity of Section, already provides this information. While it is a useful data quality check to confirm that the Section.CourseOffering.School matches the Section.School, requiring both is redundant.
• Changes Made: Changed the School domain entity reference in the Section domain entity from required to optional

Original ticket description follows:

See associated ticket ODS-615 that spawned this discussion.

There has been discussion around the relationship from Section to School being redundant. The relationship represents "The school where the Section is taught.", which seems to be already covered by the Location relationship and others. This is currently implemented in the ODS Sql using key unification which is what uncovered this scenario originally, as the FK from Section to School was a subset of the other relationship FKs.