Calendar Generation
Calendar generation Generation is the process of generating all necessary sessions Sessions that will be associated with each of the cohorts 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 , according to the timetable and calendar schedule that has been defined.
Calendar Generation for a Single Cohort
...
Bulk Generation
...
There are different structures that are used depending on whether a cohort Cohort has its timetable managed externally or not.
...
Timetable
...
Managed Externally equals
...
True
In the case where timetable is managed externally for a cohort, then a process such as the LISS Publish daily data and publish daily delta will Daily Data and Publish Daily Deltas will generally be executed from a platform such as EdVal Daily. This exchange of data instructs Posi Ed PosiEd to create individual session records for each class period.
The data relationship looks like this:
...
For each cohort Cohort we create a session Session and cohort session Cohort Session record for each class period that is being created. You may note Note that the relationship between cohort Cohort and session Session is a many-to-many architecture through the cohort session relationship through the Cohort Session object. This is because each cohort Cohort will likely have multiple sessions but Sessions and each session Session might (if it is a joint Joint session) also have an interaction association with multiple cohorts in the case of vertical or composite classesCohorts.
Timetable
...
Managed Externally equals
...
False
In the case where the timetable is managed by Posi EdPosiEd; either because the school is using a timetable product such as Edval and its publish timetable Publish Timetable feature via LISS; or because the cohort schedules Cohort Schedules have been set up manually, the following architecture is applied instead.
...
In this case, the relationship between cohort Cohort and cohort session Cohort Session can be ignored because it is not used. Instead cohort Cohort has one or more cohort schedule Cohort Schedule records and it is the schedule these Cohort Schedule records that have the relationships relationship to the cohort sessions and sessionsCohort Session and Session objects. The various generate calendar process processes will generate these cohort session Cohort Session and session Session records as per the process we'll get into in a minute.
Note that once again cohort session Cohort Session is the centrepiece centerpiece of a many-to-many relationship in order to accommodate joint classes. The calendar generation process as it pertains to Posi Ed PosiEd generating the calendar is only used when timetable managed externally is false. works when Timetable Managed Externally is False.
This process can be either a process run specifically for a single cohort by pressing the generate calendar Generate Calendar button on the cohort window or it Cohort window.
...
It can be executed for a group of cohorts in a process called bulk generate calendar Bulk Generate Calendar execution. This is done through the cohort Cohort tab of the timetable structure objectTimetable Structure page. By opening this page you can select one or more or all cohorts and then before clicking on the generate calendar Generate Calendar button.
...
This performs the same process, but it executes it across all selected cohorts.
...
Both joint and vertical class architectures require each session to be associated with two or more cohorts or cohort schedule records. Examples of the record creation are described below:
- Insert screenshots from my ERD's from vertical and composite classes from the PosiEd 1 programme (Mike to review which diagrams are best: refer Lucidchart)
Base Calendar
The Base Calendar object requires an entry for each day of the year for each grade level.
...