This process extracts information from the database, and can update the database. |
||
Subsystem |
Graduation |
|
Purpose |
To extract data containing relevant information for inclusion on a testamur (award certificate/parchment). |
|
Normally Run By |
A graduations specialist via Job Scheduler |
|
Anticipated Frequency |
In the period immediately preceding a graduation ceremony |
|
Parameter Sample |
||
View Details & Data Source |
||
Related/Dependent Jobs |
This job is run late in the graduation cycle and is typically run following GRDJ5200 (Set Graduand Order in Presentation). This ensures that the testamurs can be printed in the same order as the graduands will be presented during the ceremony. A suitable correspondence type (e.g. TESTAMUR) should exist (see CORF2110) and be linked to the output from this job. The mapping of awards to particular testamur types (in CRSF1190) may be needed. |
Extract Process |
This job uses the generic 'extract table' structure to store extracted data which can be used for the production of testamurs. A program which uses the extracted data (and data from other Callista tables if required) to produce testamurs can be custom built by the institution. The program accesses the extracted data via views specifically created for the testamur extract process. Extract Creation Processes describes this methodology.Technical detail regarding testamur extracts is provided in release Technical Documentation. Details of the data available in Testamur Extract views is available in Testamur Extract - View DetailsRecord Selection Records can be selected for batches of graduands or for a single graduand award. Primary record selection is dependent on which of certain parameters are used. Records are extracted only for graduands with a graduand status of GRADUATED, and:
Other parameters can be used for batch testamur extraction to further refine the set of records extracted. Record Extraction The extract process creates a record in the S_EXTRACT table which identifies the particular extract job run. It creates corresponding records of graduands for whom a testamur extract record has been created in the S_EXTRACT_RECORD table. Records are not normally created where a testamur record has already been extracted once, however, a parameter allows this job to be run to produce a replacement testamur. |
Update Process |
For each student course attempt for which a testamur record is extracted, the process can register an outgoing correspondence item, with a specific testamur correspondence type ( CORF2320). If required a parameter allows testamur extract records to be produced without the recording of correspondence items. |
Run Details |
Method GRDJ6000 runs only in batch mode, through the Job Control & Scheduling subsystem.Place in cycle This job would typically be run after the Set Graduand Order in Presentation job (GRDJ5200) although it could be run prior to this job for graduands receiving their awards in-absentia (System Graduand Status of INABSENTIA). Viewing the extracted data Data is usually processed by the institution's custom built testamur creation and printing job. Data can be viewed in the S_EXTRACT and S_EXTRACT_RECORD tables, or in a more useable form in the views TESTAMUR_EXTRACT_V and TESTAMUR_RECORD_V, using an ad-hoc query tool. |
The parameters for this job are grouped on the parameter form according to whether the job is being run for a batch of testamurs or for a single testamur. Batch testamur parameters are used to refine the set of testamur extract records produced. NOTES: The % symbol indicates that the parameter is not considered for processing. |
||
General |
Batch Testamur Parameters |
|
Ceremony Round |
the ceremony round from which graduands are to be considered. A value must be entered here unless a single testamur is being produced. |
|
Ceremony Number |
optional - a single ceremony for which testamurs are to be produced. Note that a ceremony selected from the list of values must belong to the ceremony round specified against the previous parameter. The default is all ceremonies within a ceremony round. |
|
Organisational Unit |
optional - a single, active, organisational unit can be selected. Limits the production of testamurs to those for student course attempts in course versions with a corresponding responsible organisational unit. The default is all organisational units. |
|
Award Code |
optional - the code of a single 'course' or 'honorary' award can be selected. Limits the production of testamurs to those for student course attempts in (a) course version(s) with which the course is associated. The default is all awards. |
|
Location Code |
optional - the code of a single open location can be selected. Limits the production of testamurs to those for student course attempts with the specified course location. The default is all locations. |
|
Course Type |
optional - the code of a single open course type can be selected. Limits the production of testamurs to those for student course attempts with courses of the specified course type. The default is all course types. |
|
Combined Degrees |
mandatory - indicates whether combined degrees are to be included in the testamur extract. Specifying INCLUDE means that an extract record is created for each student course attempt award making up the combined degree. The default value is INCLUDE. Specifying EXCLUDE means that no extract records are created for any of the components of a combined degreee. Specifying ONLY means that extract records are created only if the student is in a combined degree. |
|
System Graduand Type |
mandatory - must be one of:
The default is BOTH. |
|
System Award Type |
optional - a single award type for which testamurs are to be produced. The default is all award types. |
|
Testamur Type |
optional - a single award type for which testamurs are to be produced. The available testamur types are institution defined and the LOV displays all possible types. The default is all testamur types. |
|
Person ID Group |
optional - permits an ID group to be specified. Testamurs are produced only for students whose ID number is a member of the ID group. The default is no ID groups, meaning that only other specified parameters are considered. |
|
Individual Testamur Parameters |
||
Person ID |
optional - this parameter is used to produce a single testamur. When used, an award code must be specified. Any batch parameters are ignored when person ID is specified. Typical usage would include producing a replacement testamur. The default is no person ID. |
|
Award Code |
this parameter must contain a value when a person ID has been specified, otherwise it must be blank (or %). The combination of person ID and award code must match an existing graduand record. The default is no award code. |
|
Production Detail Parameters |
||
Production Mode |
mandatory - the default value, ORIGINAL, means that only original testamurs are to be produced. If the graduand already has an outgoing correspondence record indicating that a testamur has been produced, no entry is made in the testamur extract and no testamur will be produced. If Production Mode is set to REPLACEMENT, an entry is created in the testamur extract regardless of whether or not an outgoing correspondence record already exists for the testamur and a replacement testamur will be produced. Register Correspondence must be set to Y, for the 'original' check to be performed. |
|
Register Correspondence |
mandatory - one of:
must be selected. the default is Y. To use this feature, a suitable correspondence type (or types) (e.g. TESTAMUR, REPL-TSTMR) should exist (see CORF2110) and be linked to the output from this job. |
Last Modified on 21 September 1999.