AUCL future releases: high priority

Integrations with SITS

SORA integrations: non-centrally managed assessments.

Currently, Manager needs to manually add SORA adjustments to all departmentally run assessments in AUCL. This feature will enable SORA adjustments to be automatically added to students enrolled on non-centrally managed assessments in AUCL.

Dependencies: recording assessment deadlines (and durations) in SITS.

tbc

EC extensions integration

Currently, Manager needs to manually add EC adjustments to all departmentally run assessments in AUCL. This feature will enable SORA adjustments to be automatically added to students enrolled on non-centrally managed assessments in AUCL.

Dependencies: EC process delivery in SITS/Portico by Student Records.

tbc

Groupwork: integrate groups from Moodle and CMIS

Objective: enable the use of the external groups of students as created in CMIS or Moodle. This will eliminate the need for administrators to duplicate the work in AUCL; e.g. create student groups again. 

tbc

Automated creation of assessments

Assessments in AUCL should be created via an automated process using the existing data in SITS. The process is dependent on data being available in SITS such as submission deadlines; durations; module assessment components; etc.

tbc

Assignment design

(Author)

FlowMulti: X out of Y exam

Ability to create online assignments where students need to answer a select number of questions from the total number of questions available; e.g. answer 4 questions out of 6 available. The marking process for these assignments should be automated; where total mark is calculated based on 4 questions (currently this requires manual adjustment).

tbc

Create assignments by randomising questions/files from a content bank

Reduces student collusion and cheating.

tbc

Edit paper after the release date

Authors want to be able to edit assignment after it has been published; e.g. due to an error in the paper.

tbc

Improve Author Groups & Content Bank

• Improve edit options for multiple authors

• Improve options to link content bank and assignments

tbc

Short answer: word count

In FlowMulti; short answer question currently doesn't show word count to students when they are answering a question. If a student exceeds word limit they are unable to submit. At present students are manually counting words to ensure they are answering within an allocated word limit.

tbc

Short answer: Levenshtein distance

This is a similarity measure between two words that helps identify correct answers if spelling mistakes occur (e.g. 'helo' instead of 'hello' could be accepted as a correct answer).

It is used to enable auto-marking in short answer questions.

tbc

Delivery

(Student & Manager)

FlowMulti: automatically submit paper for a student, at deadline time.

Currently, student has to manually submit their exam paper before the deadline. If a student fails to submit, they will not be able to submit in FlowMulti. The improvement would ensure that submissions are made when a deadline is reached.

tbc

Manager: Late submission flag and report

Ability for Manager to easily identify late submissions; having a late submission flag is the desired solution. This will enable departments to apply late penalties in a more efficient way.

tbc

Manager: identify SORA  students

Ability for Managers to identify students with SORA and to check that these students have received the relevant extensions where applicable.

tbc

Marking journey

(Assessor & Reviewer role)

FlowMulti: improve 2nd marking

a) Improve 2nd marking in section-based process in Flow Multi. Currently it is not possible to assign multiple markers in section-based marking.

b) Introduce a better process for agreeing marks between co-assessors. Marks have to be agreed before the final mark can be submitted for a student.

Mar-23 planned

Section-based marking in pdf submission (FlowAssign)

Ability to run section-based marking in FlowAssign; where different questions can be allocated to different markers for marking. At present this is not available.

tbc

Retain marking history where mark is changed during 2nd marking

If co-assessors allocate different marks, they have to reach an agreement. This involves changing their marks. Currently, the system doesn't keep the history of the original mark, before it has been changed as a result of the 'agreement' process. History is required for audit purposes.

Mar-23 planned