ASSJ5341 - Upload Student Unit Attempt Outcomes

Purpose

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

Subsystem Assessments
Normally Run By Assessment Specialist and/or scheduled to run automatically at regular periods
Anticipated Frequency Frequently at the end of each assessment period

Structure

Block

Upload Student Unit Attempt Outcomes

Tabs

Parameters

More

 

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).

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).

Staff Connect

This existing report makes it possible to call it from the Staff Connect reporting interface as well as via Callista web forms. Results display appropriately within ASSF53B0 for Students who have had results uploaded.

Can be run in Immediate or Job Scheduler Mode. Can upload single or multiple units. See Staff Connect Information for further details.

 

The Upload Student Unit Attempt Outcomes block contains:

Parameters tab

Nominated Period:

  • Assessment Calendar
  • Teaching Calendar

If an upload report is required for specific criteria, please enter these criteria on the next page of this parameter form.

More tab

Specific Details

  • Location Code
  • Unit Mode
  • Unit Class
  • Unit Code
  • Finalised Outcomes check box
    The Check box allows the user to upload the student Unit Attempt Outcomes. If Staff Connect functionality available, this check box will be automatically selected.
  • Validated By
    This field allows the uploading of batch files validated by a particular user.
  • Validated Batch
    This field allows the uploading of a particular batch file.

 

Rules/Notes:

Note: The % symbol indicates that the parameter is not considered for processing.

See ASSJ3500 for descriptions of these fields.

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.

 

 

Last Modified on 26 February, 2004