Calendar Generation
...
A Session and Cohort Session record combination is then created for each of these dates and these are linked to the Cohort Schedule.
DO WE GENERATE THESE HERE OR IN GENERATE ATTENDANCE???
It will then duplicate any cohort schedule connection records for each session through session connection records. It will also create various event record entries for each cohort schedule connection record for each session. For example if there are two teachers, two classrooms and a resource booking listed in the cohort schedule connections, then it will create two session staff, two session location and a session resource event record for each session record that it creates.
Joint sessions
Whether or not a cohort’s timetable is managed externally or not, we manage Joint classes using the same objects and relationships as described previously but with an extra degree of complexity.
Both Composite and Vertical class architectures require each Session to be associated with two or more Cohort or Cohort schedule records. Examples of the record creation are described below:
WHERE ARE VERTICAL AND JOINT CLASSES DESCRIBED?
https://lucid.app/lucidchart/b298586f-e162-4267-b2b5-13279a805f65/edit?page=6e3V7Z-N18yr#