Top of GRD | Index | Table of Contents | Feedback |
GRDF2100 - Maintain Graduation Ceremony
Purpose |
To enter and maintain details of Graduation Ceremony rounds and associated Ceremonies |
|
SubSystem |
Graduation |
|
Normally Run By | Administration Specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Ceremony Round |
Ceremony Round Period | ||
Graduation Ceremony | ||
Buttons | Notes (GRDF2510) | |
Graduands (GRDF3200) | ||
Award Ceremony (GRDF2110) | ||
Copy From Ceremony (Overlay) |
The term Ceremony Round describes a period of time during which a set of Graduation Ceremonies is conducted. The term can also imply the preparatory events and processes leading up to the Ceremony Period itself. Each Ceremony Round is linked to one or more prior completion periods (the Ceremony Round Periods) used to identify potential Graduands. Institutions typically have more than one Ceremony Round during an academic year. Ceremony rounds might run concurrently, for example where an institution runs Graduation Ceremonies both in the 'home' country and overseas. Alternatively, this situation could be handled by creating different Ceremony locations within the one Ceremony Round. Related Forms and JobsCeremony Rounds and their associated Ceremonies are defined in this form. It is the first of four forms creating a complete data structure for Ceremonies. A button in this form leads to GRDF2110 (Maintain Award Ceremony) which in turn leads to GRDF2120 (Maintain Unit Set Ceremony), and GRDF2130 (Maintain Award Ceremony Group)/. The Ceremony Structure is used primarily by the job GRDJ5100, which allocates Graduands with course awards to Ceremonies, and GRDJ5200, which sets up presentation orders within each Ceremony. Graduands may also be allocated to Ceremonies individually, using the form GRDF4210. Prerequisite Calendar StructuresAs a precursor to creating a Ceremony Round and Ceremonies, a Graduation Calendar Instance and associated Date Alias Instances must be recorded in the Calendar Subsystem. A Graduation Calendar Instance broadly defines a Ceremony Round. Only those Date Alias Instances already associated with the selected Ceremony Round are available for use in this form. For more information refer to Ceremony Rounds and Dates in Understanding Graduation, or Calendars and Date Aliases in Specialist Functions.
Graduation Ceremony Rollover Award Ceremony structures can be rolled over per Ceremony (not per Ceremony Round) using the 'Copy From Ceremony' button. Only the composition of the Ceremony (i.e. the Award Ceremony structure) can be rolled over. A Ceremony must still be created prior to running this process. Any warnings that are encountered during the process are displayed. Ceremony compositions can be rolled over from a previous Ceremony. This includes the ability to roll a Ceremony from inside a Ceremony round to another Ceremony. For example, GRD-ROUND 1 Ceremony 1, rolled into GRD-ROUND 1 Ceremony 2. This form is accessed from the main menu. |
The Ceremony Round block contains:
The Ceremony Round Period block contains:
The Graduation Ceremony block contains:
|
Rule/Notes: |
Ceremony Round block Use this form to create, maintain and inquire on Ceremony Rounds and the Ceremony or Ceremonies held during each round. Select the Calendar Type denoting the required Ceremony Round from the list of ACTIVE and PLANNED graduation calendars available. Necessary details for a Ceremony Round are:
Button
|
Notes: Introductory information on Ceremony Rounds, Start Date Alias, End Date Alias and Completion Periods is given in Understanding Graduation. Example
of using Start and End Date Aliases: When Callista automatically identifies and creates Graduand records (GRDJ3100), it compares the Ceremony Round Periods with the student's Completion Year/Period. This is advised by students as the time of their expected Course Completion, and is shown in ADMF3240 and ENRF3000. When the Progression Subsystem becomes available, the System will normally be able to derive a student's Completion Year and Period. |
Graduation Ceremony block One or more Ceremonies can be recorded for each round. Required data for a Ceremony are:
Optionally, a Ceremony Fee and the maximum number of Guests per Graduand can be recorded. Currently these are for information only. Totals fields cannot be accessed. Their values are automatically calculated each time the form is queried, from information in the records of individual Graduands. (See Totals Note in column opposite.) Notes can be recorded for each Ceremony. Instructions for doing this are found under Notes Facility in the General System Functions and Facilities section. Buttons
|
Notes: Venue Codes for this and other Subsystems are recorded in the form ASSF4200. The use of Ceremony Date Aliases and Closing Date Aliases is outlined in Understanding Graduation. The Ceremony and related details can be logically deleted but the Ceremony Number cannot be reused in the same Ceremony Round. The Ceremony Date Alias Instance and Closing Date Alias Instance cannot be changed once Graduands are allocated to the Ceremony. It is not possible to update information relating to a Ceremony after the Ceremony Date has passed. Individual allocation of Graduands to Ceremonies is still possible after the Closing Date, using the form GRDF4210. Totals. Combinations of the Graduand Status, Graduand Approval Status and the Graduand Type are used in determining totals, as follows:
The Notes facility can be used to record a description of the Ceremony. |
Last
Modified on 19 May, 2005