Top of GRD | Index | Table of Contents | Feedback |
Graduation Specialist Functions
In this section:
This section is written for specialist Graduation staff who have responsibility for setting up and maintaining the Subsystem. The following is assumed:
Setting Up the Graduation Subsystem
Reference Data
In order for the Graduation Subsystem to function effectively, the following reference data must be created and maintained:
Reference Data |
Purpose |
Mandatory ? |
Maintenance Form |
Pre-requisite Setup |
Graduand Statuses |
Indicate the Graduand's academic eligibility to Graduate and the current state of the Graduand Record |
Yes |
None |
|
Graduand Approval Statuses |
Are used to determine whether the Graduand is formally approved to Graduate |
Yes |
None |
|
Honours Levels |
Are institution defined equivalents to Government Honours Levels. Other (non-Government) levels of achievement are also recorded in the form. |
Required if institution records honours as part of Graduation process |
Government Honours Levels must be recorded in STAF112F |
|
Graduation Note Types |
Used to classify notes about Ceremonies according to purpose |
Required if Notes are used in GRDF2100 |
None |
|
Testamur Types |
Indicate particular content and layout requirements of Testamurs |
Yes |
Correspondence Types recorded in CORF2110. |
|
Testamur Delivery Method | Allows users to maintain user defined Testamur Delivery Methods that can be mapped to System Delivery Methods | No | GRDF1700 | None |
Measurements - Gown & Hat |
A full list of Academic Dress Gown and Hat Sizes available to Graduands |
Yes, if sizes are to be recorded in GRDF4210 |
None |
|
Awards |
Used to represent Awards conferred by the institution, normally after completing the requirements of a course, but also for conferral of honorary Awards, prizes and medals |
Yes |
|
None |
Course Awards |
To record the links between Awards and Courses; necessary to confer Awards and organise Graduation Ceremonies. This data is normally set up when establishing course structure details |
Yes |
Calendars and Date Aliases
A general introduction to the periods and events underpinning Graduation processes in Callista is found under Ceremony Rounds and Dates in Understanding Graduation. This section deals with setting up the Calendar and Date Alias Instances representing these periods and events.
A suggested method for initial setup of Graduation Calendars is to follow these steps:
The number of rounds required in an Academic Year depends on many variables. For example, the Organisation of Graduation may be decentralised, or some Ceremonies may be held offshore, and the decision may be taken to create separate rounds to cater for such circumstances. See suggested setups for different scenarios in Special Topics.
These Calendar and Date Alias Instances are used when setting up Rounds and Ceremonies in GRDF2100. Each Ceremony Round is associated with one or more Ceremony Round Period comprising a Completion Period (the period of the year in which a student is expected to complete a Course Attempt) and year. Note that completion periods are not represented by Callista Calendars, but are System defined.
In order to accommodate Graduands wishing to defer Graduation until a future round, it is recommended that Graduation Calendars are set up for all rounds for the following Academic Year. At present, any rollover would be at individual Graduation Calendar level, and would include Date Alias Instances but not Ceremony details.
Graduation Locations and Venues
The job to allocate Graduands to Ceremonies, GRDJ5100, is designed to place each Graduand at a Ceremony whose venue is associated with the main campus at which they have been studying. In order to achieve this, a structure of linked venues, Graduation Locations and campus locations must be in place.
Each Graduation Ceremony is held at a specified venue. Each venue is associated with a single nominal 'Graduation Location'. A campus location can be associated with one or more Graduation Locations, but one Graduation Location must be nominated as the default for the campus. The example in the diagram below illustrates a possible structure.
grd03
If required, more than one venue can be linked to a Graduation Location.
Often, a campus will be associated with only one Graduation Location (marked as the default). The reason to associate it also with one or more non-default Graduation Locations is to allow flexibility between rounds. Using the diagram to illustrate:
Extrapolating from this example, all students in Round 2 could be chanelled to the Regional location if no Ceremonies were recorded with venues associated with the metropolitan Graduation Location.
Setting up Venues and Locations
Graduation Location structures are similar to structures required in other Subsystems (notably Assessments). The Graduation Subsystem therefore shares with them a set of common 'Location' forms.
To set up Locations and Venues for Graduation:
Via the buttons in form ORGF0131, for each Graduation Location:
(You may choose to enter ORGF0133 with a campus location as context. In this case, Graduation Locations are recorded as sub locations of campuses.)
Record and maintain a venue or venues where Ceremonies will be held, in the form ASSF4200 (Maintain Venues). The Supervisor Limit and Priority Code fields are not relevant to Graduation Locations.
For each venue, at least one Venue Address should be recorded in ASSF4201 (Maintain Venue Address), accessed via a button in ASSF4200. This address will be used in correspondence to students giving details of the Ceremony to which they have been allocated. Postal or contact addresses may also be recorded here.
Ceremony Rounds, Awards and Unit Set Groups
Ceremony Rounds and Ceremonies are set up using form GRDF2100.
The Awards to be presented at each Ceremony must be listed in GRDF2110. Apart from Honorary Awards, all Awards are associated with a Course. These Course Awards can be further subdivided into Unit Set Groups in form GRDF2120 to give maximum flexibility in grouping Graduands for presentation. A common use of this facility is to group Graduands according to their major study sequence within a course.
Special Awards such as prizes, gifts or medals are set up in Special Awards (GRDF3600).
Whether at Award level or Unit Set Group Level, order numbers control the presentation sequence. At either level two or more records may be amalgamated for grouping purposes by assigning them the same order number, although at course level this is only possible if they share a common Award Code. When assigning numbers it is recommended that gaps are left in the numbering sequences to allow for later additions to the list of Awards or Unit Set Groups.
The table below illustrates some different grouping combinations. Graduands are grouped:
It is possible to use any or all of these variations when setting up an order sequence for a single Ceremony.
Course Awards (established in GRDF2110) |
Unit Set Components (established in GRDF2120) |
||||
Course Version |
Award |
Order in Ceremony |
Unit Set Group |
Unit Sets |
Order in Award |
M614/1 |
1520 |
1 |
. |
. |
. |
S300/2 |
1188 |
5 |
Electronics Major & Robotics Major |
ECMJ |
1 |
. |
. |
. |
Manufacturing Major |
MFMJ |
5 |
M300/1 |
1002 |
10 |
Accounting Major & Banking and Finance Major |
ACMJ001 |
1 |
. |
. |
. |
Economics Major |
ECMJ001 |
5 |
M300D/1 |
1002 |
10 |
Accounting Major & Banking and Finance Major |
ACMJ001 |
1 |
E355/1 |
1015 |
25 |
. |
. |
. |
E355/2 |
1015 |
25 |
. |
. |
. |
. |
PHD-HON |
30 |
. |
. |
. |
Jobs and Reports
The jobs and reports listed in the Subsystem Table of Contents need to be set up in the Job Control and Scheduling Subsystem.
A student is able to use functions within Graduations while online using Connect. See Connect functions for further details.
The Graduation functions are:
Last Modified on 05 September, 2006