Skip to main content

Module enrolment_discovery

Module enrolment_discovery 

Source
Expand description

The enrolment-discovery phase: who the study registry says is on the course.

Each iteration fetches the enrolment lists of the course codes that are due, those with people waiting first, in batches as large as the registry takes; every module on a code shares its list. One list wakes the registrations of people we already have a link for and, while account linking is switched on and link-emails is not paused, claims a linking email for everybody else, which the link-emails phase is made due at once to send. When to fetch a code is headless_lms_models::credit_registration_roster_schedules.

Modules§

listing 🔒
Sending one listing request, and recording what its enrolment lists, or its failure, say about each code.
reconcile 🔒
What one code’s roster does to the modules on it: waking linked students’ registrations and claiming linking mails for everybody else.

Structs§

CodeListing 🔒
One code of a listing request, with the modules that share its roster.

Functions§

load_due_roster_codes 🔒
The codes whose enrolment lists are due, those with people waiting first, then by when each fell due.
load_listing_modules 🔒
Each planned request’s codes, with the modules that share each code’s roster.
plan_roster_requests 🔒
Groups due codes into requests in the order given: a code fetched alone in one of its own, the rest in batches of request_size. Keeps the first request_limit.
run 🔒
With account linking off (account_linking_since None), a roster still wakes linked students’ registrations, and only the mails are left out.