Top of CAL | Index | Table of Contents | Feedback |
CALF0320 - Rollover Calendar Instance
Purpose |
To provide a quick method for the creation of new Calendars based on an existing Calendar Instance, its related Subordinate Calendar Instances and associated Date alias Instances |
|
Subsystem | Calendar | |
Normally Run By | Administration Specialist | |
Anticipated Frequency | At the start of a year/term/period required | |
Structure | Blocks | Calendar Instance |
Calendar Instance Relationship | ||
Button | Rollover Calendar |
Calendar Instance A Calendar Instance defines a particular occurrence of a Calendar Type and is defined by assigning a start and End Date to the Calendar Type. A Calendar Instance may have many Date Alias instances (Calendar events) associated with it. It may also have a number of Subordinate Calendars related to it. This form is displayed as part of the process (described below) which enables a Calendar Instance, its related Subordinate Calendar Instances and associated Date Alias Instances to form the basis for the creation of a new, similar, Calendar Instance. In creating a Calendar Instance in this way, related information is also created without the need to laboriously re-enter data. This block displays the Calendar Instance (carried forward from the Maintain Calendar Types form) to be rolled over and the Start and End Dates of the new Calendar. For example, a Calendar Instance SEMESTER1, 01/01/02-30/06/02 can be used to create the new Calendar Instance SEMESTER1, 01/01/03 - 30/06/03 via the rollover process. The process also carries forward to the new Calendar any related dates (such as 'Start of Lectures') and any subordinate Calendars (such as Exam or Fee Calendars) which were attached to the source Calendar. Calendar Instance Relationship New Calendar Instances may be created and linked to Superior Calendars which have either already been rolled forward or have been newly created. As part of the Rollover process, if a new Calendar Instance is linked to a Superior Calendar and then rolled forward, the System will create a link to a suitable Superior Calendar if one exists. When a new Calendar does not have the desired relationship specified, this block enables you to specify a Superior Calendar to which the Calendar being rolled over will be linked. For example, the Academic Calendar Instance for 2002 may have been rolled over into 2003 along with all its Subordinate Calendars.
This form is accessed through CALF0220, via the Rollover Calendar button (bottom right). |
The Calendar Instance block contains:
The Calendar Instance Relationship block contains:
|
|
Calendar Instance block To create a new Calendar Instance (its Date Alias Instances and its associated Subordinate Calendar Instances) from an existing Calendar Instance using the Calendar Rollover process:
|
Rules/Notes: The rollover process cannot be undone. It is necessary to manually delete all new details in order to reverse the process. All new Calendars resulting from this process have System Status PLANNED. Inactive Calendar Instances and Calendar Instances with closed Calendar Type cannot be rolled. A user cannot roll Calendars for which he/she has a Calendar Category restriction. The Rollover Start Date must be after the Start Date of the existing Calendar Instance. A Calendar cannot be rolled to an instance which already exists. When rolling an ACADEMIC Calendar, the new instance will default to the next year. The process rolls alternate codes of existing Calendars to the alternate codes of the new Calendars, except in the case of ACADEMIC Calendars where the alternate code = the year to which the Calendar refers. Where the System cannot determine the Offset of a Date Alias Instance (due to non-existence of its Offset Date Alias Instance or the offset Date Alias' Calendar Instance) it will be created but with no absolute value or alias value. Rollover End Date for the new Calendar is calculated by the System by adding the difference in days between the Start Dates of the new and existing Calendars to the End Date of the existing Calendar. If the start day and month of the two Calendars are identical, the System will recognise this and make the end day and month identical, regardless of leap years. When
rolling a Calendar which has a Superior, the
System will determine if a link should be created from the new Calendar
to a suitable existing Superior Calendar. (This applies particularly where
a set of Calendars has been rolled, a new Subordinate Calendar is associated
with a pre-existing Superior and rolled forward separately. The System
will attach the rolled subordinate to the previously rolled Superior.) |
Calendar Instance Relationship block To link a rolled over Calendar Instance to a Superior Calendar as part of the rollover process:
|
|
Last Modified on 1 March, 2004