Top of CAL | Index | Table of Contents | Feedback | ![]() |
CALF0420 - Maintain Date Alias
Purpose |
To enable the definition of a Date Alias, Date Alias Offset or Date Alias Pair |
|
Subsystem | Calendar | |
Normally Run By | Administration Specialist | |
Anticipated Frequency | At the start of a year/term/period required | |
Structure | Blocks | Date Alias |
Date Alias Offset | ||
Date Alias Pair | ||
Button | Date Alias Instance (CALF0511) | |
Offset Calendar Restrictions (CALF0450) | ||
Offset Contraints (CALF0442) |
Date Alias In the System, Date Alias is the generic name for a Calendar Event, not the actual occurrence of an event. It is defined by its name and the Date Alias Category to which it is assigned. It may also be assigned to a Calendar Category which will limit its use exclusively to Calendar Instances of the same category. For example, CENSUS could be the Date Alias for any day on which census data is collected for the government. There would be any number of census days over time, occurring on different dates each year. Using this form to define a Date Alias is the first step to including the specific date of an event in the relevant calendar. By attaching a date to CENSUS, say 31/3/03, and applying it to a Calendar Instance, say semester 1, 2003 (SEM-1, 3/3/03, 15/6/03) we can define a particular occurrence of the Date Alias CENSUS and hence create a Date Alias Instance. The Building a Calendar diagram illustrates this. Date Alias Offset It is possible to define a relationship between two Date Aliases which specifies that one will occur at a fixed interval before or after the other. This block is used to display and maintain this time relationship between two Date Aliases. It is also possible to ensure that no matter what date is assigned to the offset Date Alias, the subject Date Alias will not fall on specified days. This is achieved by selecting the Offset Constraints button and specifying Offset Constraints details in CALF0442. For example, the last day of an examination period may always be 12 days after the first day of this period. When the two Date Aliases are assigned to a Calendar Instance and the first date is defined, the second date will be automatically calculated as 12 days later. Another example could be, a Date Alias for the submission of statistics to government could be defined as always occurring one month after the census date. When these two Date Aliases are applied to a Calendar Instance, and a date value for the census date defined, a date value for submission of the statistics will be automatically calculated as 1 month later. In this case the census date is called the 'Offset Date Alias' and the amount of time between the two dates is called the 'Offset Duration'. An occurrence date for a Date Alias with an offset will only be automatically generated the first time that the two related Date Aliases are applied to a particular Calendar Instance. Date Alias Pair The pairing of Date Aliases indicates that two dates plus every day between the two dates are represented by the relationship. For example, two Date Aliases ST-BRK and END-BRK may name the start and end dates of a mid-semester break. Pairing them defines the entire period of the break, inclusive of these two dates. When a Date Alias pair is created for Date Aliases with instances in calendars of category HOLIDAY, it effectively defines an institutional break, one of the System Date Offset Constraint Types. |
The Date Alias block contains:
The Date Alias Offset block contains:
The Date Alias Pair block contains:
|
Rules/Notes: |
Date Alias To create a new Date Alias, using the Maintain Date Aliases form:
|
Rules/Notes: Assigning a Calendar Category to a Date Alias will limit its use exclusively to Calendar Instances of the same Calendar Category. |
To modify a Date Alias, using the Maintain Date Aliases form:
|
Rules/Notes: If a Date Alias has been used by a Date Alias Instance and applied to a Calendar Instance its Calendar Category cannot be modified. |
To delete a Date Alias, using the Maintain Date Aliases form:
|
Rules/Notes: A Date Alias cannot be deleted if it has been:
However, it can be closed, preventing any further use, by selecting the Closed check box. |
Date Alias Offset To create a Date Alias offset for the displayed Date Alias, using the Maintain Date Aliases form:
|
Rules/Notes: To effectively use Date Alias offsets, Date Alias Instances for these Date Aliases must be created using the Maintain Date Alias Instances (for particular Calendar Instances) form which is accessed via the Maintain Calendar Types form. Instances of the two Date Aliases must occur in the same Calendar Instance. |
To modify a Date Alias offset: | Rules/Notes: Modification of Date Alias Offsets should be carried out using the Maintain Date Alias Instances (for particular Calendar Instances) form. |
To delete a Date Alias offset, using the Maintain Date Aliases form:
|
Rules/Notes: This function is used for the deletion of a Date Alias Offset. If Date Alias Instances have been created from this offset, they should be reviewed and modified if necessary using the Maintain Date Alias Instances (of a particular Date Alias) form. |
Date Alias Pair To create a Date Alias pair for the displayed Date Alias, using the Maintain Date Aliases form:
|
Rules/Notes: It is not possible to directly modify a paired Date Alias. To specify a pair relationship with a different Date Alias it is necessary to delete the existing paired Date Alias and create a new Date Alias pair. |
To delete a Date Alias pair, using the Maintain Date Aliases form:
|
Rules/Notes: |
Last
Modified on 07 December, 2004