How XUNO handles team teaching, composite classes, yard-duties and attendance
In this article
Thinking of switching the timetable package you import from? ...
Each timetabling package (even if you import from First Class > CASES > XUNO) exports its class codes differently. Some packages support suffixes, some don't. If you were to switch half way through a term or a semester you will end up with duplicate classes. That is because we will not able to match the class codes anymore. We recommend you switch or make major changes to your timetable package at the end of a semester and then import a new timetable.
During the timetable import process, XUNO will combine classes with the same class code and different teachers into one class because it will automatically recognise this class as a team-taught class.
ENGY07A taught by AM and ENGY07A taught by JA, will be combined into one team-taught class ENGY07A-AMJA. Note how the initials of each teacher are appended to the end of the class code.
If you do not want combined classes and would like each class to remain separate, then you must either use a unique class code for each class, or add a unique suffix to each class in your timetabling software.
CASES timetabling does not support the unique suffix option.
When importing a timetable, XUNO will create a composite class when multiple classes share the same class code or when two or more classes are taught by the same teacher on the same day and same period on your timetable. The latter instance will occur even if the class has a different class code.
If you do not want composite classes and would like each class to remain separate, then you must either use a unique class code for each class, or add a unique suffix to each class in your timetabling software. CASES timetabling does not support the unique suffix option.
Day 1, Period 3: ENGY07A taught by AM
Day 1, Period 3: ENGY08C taught by AM
Day 1, Period 3: ENGY07A taught by AM
Day 4, Period 5: ENGY07A taught by MB
These will be combined into one composite class.
When importing a new timetable for the first time, XUNO will automatically flag the 'subject' of a class as a yard-duty if there are no students in the class. This only occurs the first time a class is imported to a timetable in XUNO. On later imports, the yard-duty flag will not change, even if the class now has students enrolled in it.
All classes whose subjects have been flagged as 'Yard duty' will not show on student timetables. You can change the behaviour of each subject and its classes (whether they should be considered as yard-duty or not) after the class has been imported by following these steps.
- Click on the Administration menu, then click on Subjects under the Timetabling section.
- Find the subjects related to the classes and then select or deselect the Yard Duty check box as required.
What Happens to Attendance Data after a Timetable is Imported
Any attendance data that is still valid after a timetable import will remain untouched. Attendance data is considered 'valid' when a class still exists on the same date and period of the previous timetable.
Any attendance data that is invalid after the import, is automatically removed. Attendance data is considered 'invalid' when a class does not exist on the same date and period of the previous timetable.
What Happens to Scheduled Attendance after a Timetable is Imported
All scheduled attendance that falls into the date range selected during the timetable import, is reapplied after the import. If you re-import a timetable and the scheduled attendance is still relevant to the updated student timetable, the changes will still be applicable. Otherwise, the scheduled attendance will no longer apply.
When importing a timetable, XUNO will automatically create a new period if it can not find an existing period with the same name or linked "timetable period". XUNO keeps its own internal records of periods - allowing you to change period names, delete them and even link them to different timetable periods.
To prevent a previously imported timetable period from displaying on your XUNO timetables, you must "hide" the period. Do not delete or unlink the XUNO period from your imported timetabled period. Doing so will cause the period to be automatically created again during the next timetable import.