Timetable Structures and Calendar Generation
...
The primary purpose of prime of timetable term records is to provide start and end dates for each term. Terms are hierarchical in nature, for example a term of type academic year will likely have two terms of type semester. Underneath it, each of these are likely to have two terms of type term underneath them.
- create a diagram showing this hierarchy
In the timetable structure context, the most important thing to remember is that all cohorts Cohorts related to a timetable structure Timetable Structure will have a timetable term they are linked to and this will provide the default start Start and end End date range for that cohortCohort. For example, if a cohort Cohort is a full year class, then it should be linked to the academic year term. If it is a cohort that only runs for a single semester then it should be linked to that semester’s term record.
...
Bell Time Records provide a range of options when you are defining a timetable structure. For example example Monday period one 1 in week Week A might start at 8:45 but on Week B start at 9:00 AM. Or Friday timetables might start 30 minutes after other timetables and maybe they have one less period. As long as the data is set up consistently you will be able to extract a great degree of flexibility with regards to bell time structures.
- We need to add additional information on this field using the LISS documentation – refer to data dictionary for reference.
Note that if you are using timetabling software such as Edval or Edval Daily, the Bell Times structure is generally populated for you via the publish Bell Times process.
...
The timetable period table looks something like this:
...
And here Here is an example of a single timetable period record
...