Upload Student Unit Attempt Outcomes - ASSJ5341

Subsystem

Assessments

Purpose

This job validates batch files of student unit attempt outcomes and loads successful records into the System.

Normally Run By

Assessments specialist and/or

Scheduled to run automatically at regular intervals

Anticipated Frequency

Frequently at the end of each assessment period 

Update Process(es)

Validates and loads the student unit attempt outcome batch files 

Reports

Upload Student Unit Attempt Outcomes - Exception Report 

Parameter Sample

Report Sample

 

Related/Dependent Jobs

This job is dependent on batch files having been created by the Validate Electronic Outcome Upload File process (ASSF5340) at a previous time.

The validations for the upload files are configured in the Maintain Results Entry Configuration form (ASSF01K0).

 

Update Process

The electronic upload process:

  • Validates each record against the configurations established in the Maintain Results Entry Configurations form (ASSF01K0).
  • Loads validated records into Callista.
  • Loads those records designated as HOLDING (according to criteria given in ASSF01K0) into the non-enrolled student outcome structure. Details of these actions are listed in the exception report.
  • Records that are not loaded into Callista are listed in the exception report.

Refer to Electronic Upload of Results in Assessments for the Subsystem Specialist for further information on the electronic upload process.

 

Run Details

This job is usually run at the end of each assessment period but can be run at any time.

It is recommended that this job be run in batch mode. However, it can be run online, particularly where the report is run with parameters specifying a small data set, such as a specific validated sequence number (batch number).

 

Job Parameters

The parameters for this job are used to refine the data set produced.

  • The Validated By parameter allows the uploading of batch files validated by a particular user.
  • The Validated Batch parameter allows the uploading of a particular batch file.
  • The Insert as Finalised Outcomes parameter allows the user to upload the student unit attempt outcomes as either 'finalised' or 'recommended' outcomes.

 

Report(s)

The Exceptions Report

 

The report displays all exceptions encountered through the validation of the batch files.

The exceptions reported relate to the validations configured in ASSF01K0. The exceptions are:

  • WARNING - occurs where the validation for Mark/Grade Invalid in ASSF01K0 is set to WARNING. Records are loaded into the System and no action is required.
  • ERROR - occurs where the validations are set to DON'T LOAD or ABORT FILE in ASSF01K0. The records are not loaded into the System and must be resolved by an assessments specialist.
  • DUPLICATE - occurs where a student unit attempt outcome has already been loaded into the System. The duplicate is not loaded into the System and no action is required.
  • HOLDING - occurs where a validation is set to HOLDING within ASSF01K0. For example: Unit Not Enrolled. There are three types of HOLDING exception reported. They are:
    • HOLDING - the record is successfully loaded into the non-enrolled student outcome structure for resolution. Non-enrolled student outcomes can be viewed in the Non-Enrolled Student Outcomes Report (ASSR06J0).
    • HOLDING DUPLICATE - the record already exists in the non-enrolled student outcome structure. The duplicate record is not loaded into the System and requires no action.
    • HOLDING ERROR - this exception will be fairly rare. It occurs where a valid unit version for the record cannot be. For example: a unit version is made invalid part way through a teaching period, student outcomes may exist. However, the unit code is no longer valid within the System. The record is not loaded and must be resolved by an assessments specialist.

Summary statistics are displayed at the end of the report.

The report is presented in landscape mode.