Skip to main content

Module enrolments

Expand description

The second half of a resolve-enrolments iteration: the enrolment lookup, and freezing the payload the import will send.

request decides whether a row can be asked about, answer what the registry’s answer means, and resolution what that comes to for the row; the orchestration, with its transaction, is here.

Modules§

answer 🔒
What the study registry’s answer to an enrolment lookup means for the row: the enrolment it lists, or the error it gave, and the grade scale our grade would go out on.
request 🔒
Whether a row can be asked about at all, and what to ask the study registry about its enrolment.
resolution 🔒
Given everything known once the lookup answered, what happens to the registration: settled as a duplicate of a credit already held, failed, or its payload frozen for import.

Structs§

LookupBasis 🔒
What a row’s lookup was built from: the submission context, and the criteria the lookup’s enrolment must fit. The answer is applied against what was asked, not against a second read of the database.
ResolveEnrolments 🔒

Functions§

apply_enrolment_answer 🔒
Writes an answered lookup: settles the row as duplicate when a credit it would not beat is already held, fails it when there is nothing to register against, and otherwise freezes the payload and queues the row for import.

Type Aliases§

Resolvable 🔒
A row claimed for its enrolment lookup.