To permit the attachment of calendar events (date alias instances) to particular calendar instances. Note that two forms (this one, and CALF0511) achieve similar results. In this form, a number of events can be attached to one calendar instance. In CALF0511, one event can be attached to several different calendar instances. |
||
Subsystem |
||
Structure |
Three Blocks |
Calendar Instance Date Alias Instance Date Alias Instance Offset |
|
Calendar Instance |
Explanation |
This context block shows the calendar instance for which associated date alias instances are displayed and/or maintained in the block below. When this form is entered via the navigation button in the Maintain Calendar Types form, the context calendar instance is the one selected there. No inquiry on other calendar instances can be done directly in this form. It is necessary to return to the Maintain Calendar Types form and select another calendar instance there. |
An example might be the attachment of the event 'End of mid semester break' (END-BRK) to the calendar instance for 'Semester 1 1996' (SEM-1, 1/1/96, 30/6/96). |
Date Alias Instance |
Explanation |
The term 'date alias instance' is used for an occurrence of a calendar event. Generally, to create a date alias instance you need to:
The exception is for a calendar under development with a system status of PLANNED. In this case, a date of occurrence is not required immediately but must be added before the calendar instance is made 'active'.This block displays existing date alias instances attached to the context calendar instance shown in the block above. These can be modified or deleted here, and new ones added. Two date values can be displayed for each date alias record:
The alias value is the one recognised by the System as the value of the date alias instance. |
|
|
Rules:
|
|
Rules:
|
|
Rules:
|
Date Alias Instance Offset |
Explanation |
The date of an event (the date alias instance) may be specified in terms of its relationship to another event (the 'base event'). The time difference between the two events is called the 'offset'. The 'base event' is termed the 'Offset Date Alias'. It is possible to ensure that no matter what date is assigned to the offset date alias, the subject date alias instance will not fall on specified days. This is achieved by specifying Offset Constraints in CALF0520, accessed via the navigation button in this form.This block is used for the creation, modification and display of offset information pertaining to the selected date alias instance in the block above.An absolute value overrides a calculated offset value where both are set. The alias value will reflect this. |
A date alias instance for the end of semester 1 mid-semester break (END-BRK1) could be defined as occurring 8 days after the date alias instance for the commencement of semester 1 mid-semester break (ST-BRK1). The Offset Date Alias is ST-BRK1, the Offset Duration of 8 days applies to END-BRK1. |
|
Rules:
|
To modify an offset date alias instance using the Maintain Date Alias Instances form: |
|
|
Rules:
|
To delete an offset date alias instance using the Maintain Date Alias Instances form: |
|
|
Rules:
|
Date Alias Instance Pair |
Explanation |
The pairing of date alias instances indicates that the two dates plus every day between the two dates are represented by the relationship. When a date alias instance pair is created using alias instances in calendars of category HOLIDAY, it effectively defines an institution break, one of the System Date Offset Constraint Types.A pair relationship can also be defined at the date alias level in CALF0420. |
Example |
A date alias instance ST-BREAK, 15/05/1999 is created in a calendar of category HOLIDAY, and it is paired with the date alias instance END-BREAK, 30/05/1999, also in a holiday calendar, the System recognises the period 15/05/99 - 30/05/99 inclusive as an institution break. |
To create a date alias instance pair, using the Maintain Date Alias Instances form: |
|
|
Changes within this form will have the following notable effects: |
|