Calendar Generation
Calendar Generation is the process of generating all necessary Sessions that will be associated with each of the Cohorts for which we are generating the calendar. This means we are creating the individual classes for each of the class periods for each of the class groups, according to the timetable and calendar schedule that has been defined.
...
In the case where timetable is managed externally for a cohort, then a process such as the LISS Publish Daily Data and Publish Daily Deltas will generally be executed from a platform such as EdVal Edval Daily. This exchange of data instructs PosiEd to create individual session records for each class period.
...
Note that once again Cohort Session is the centerpiece of a many-to-many relationship in order to accommodate joint classes. The calendar generation process as it pertains to PosiEd generating the calendar only works when Timetable Managed Externally is False.
This process can be either a process run for a single cohort by pressing the Generate Calendar button on the Cohort window.
...
It can also be executed for a group of cohorts in a process called Bulk Generate Calendar execution. This is done through the Cohort tab of the Timetable Structure page. By opening this page you can select one or more or all cohorts before clicking on the Generate Calendar button.
...
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#in Joint Cohorts & Sessions - PosiEd