Top of ADM | Index | Table of Contents | Feedback |
Purpose | Use this form to map System Admission Date Aliases to institution-defined Date Aliases. | |
Subsystem | Admissions | |
Normally Run By | Enrolment/Administration Specialist | |
Anticipated Frequency | Normally before commencement of course year, but can be run as required. | |
Structure |
Block |
Admission Calendar Configuration |
For the Admissions subsystem to operate there are critical dates that must be specified. System flexibility enables institutions to choose the names for these dates. The chosen names are recorded in this form to enable the system to recognise them. The actual values (Date Alias Instances) of these dates, for an Admission Calendar, are recorded in the Calendar subsystem. Configuring Admission Calendars describes this process fully. For example, the system requires a Due Date Alias. This is the date when Admission applications for a particular Admission Period should have been received by the institution. The institution may choose to give this date the code APPL-DUE. For the system to be able to recognise APPL-DUE as the date when applications are due, it must be recorded in this form as the Due Date Alias. Date Aliases to be recorded are: Date Aliases Relating to Admission Periods: Each of these Date Aliases must have a System Calendar Category of ADMISSION and 'instances' created in each Admission Period.
Date Aliases Relating to Academic Periods Each of these Date Aliases must have a System Calendar Category of ACADEMIC and have 'instances' created in each Academic Period. They are used to determine whether the student will complete their course mid-year, at the end of the year, or at the end of a Summer Teaching Period. The calculation of an anticipated completion date results in a date that, in turn, is related to one of the following dates (whichever is the closest date on or before the calculated date) to determine nominated completion year and period. These dates are not related to Admission Periods. Refer to the Derivation of Completion Period/Year topic for a full description of the system derivation.
Use this form to advise the system of the institution-defined Date Aliases, previously created in the Calendar subsystem, that represent critical Admission dates. Refer to the Calendar Subsystem for explanation of the concept of Date Aliases. This form is accessed from the Main Menu. |
The Admission Calendar Configuration block contains:
|
Rules/Notes: Date Aliases must not be closed. The following Date Aliases must have a System Calendar Category of ADMISSION:
The following Date Aliases must have a System Calendar Category of ACADEMIC:
A default buffer period can be defined at the beginning of a course commencement at an institution that applies to all courses. This is to accommodate international students arriving in Australia earlier than the expected course commencement date. The buffer period is used to automatically adjust the start date of the health care cover by the days captured in the buffer.
This adds to the total duration for health care cover calculations. A second buffer period can be recorded that applies between courses. This makes sure there are no unacceptable gaps between courses, where multiple courses are attempted by a student. This is the maximum number of days allowed between the end of one course and the beginning of the next course for the purposes of calculating overseas health care cover. If the gap between courses is larger than the buffer amount then a warning is displayed (AMDF3910) advising that the health care cover period will not extend to the second course. |
Last Modified on 15 February, 2018 2:00 PM
History Information
Release Version | Project | Change to Document |
13.1 | 1708 - Compliance | New fields added |
13.1 | 1323 - Document Maintenance | Fixed spelling mistake |