Expand description
Where a registration stands on the admin timeline. Derived from the ledger state and the preconditions rather than stored, so a new ledger state has to be placed on the timeline before it compiles, and every admin surface (lists, counts, the registration page) places it alike.
Structs§
- Step
Match - The
(state, completion_eligible, has_verified_student_number, course_code_allowed, enrolment_resolved)combinations a set of steps covers, each with its step, as parallel arrays for a query toUNNESTand join against, as a filter or viaSelf::all. - Timeline
Position - A row’s step, with its student’s
Engagementwhere the step waits on the student.
Enums§
- Engagement
- What a student waiting on their own step has done on the registration page. Per completion, so every attempt of one completion shares it. Ordered from most to least engaged.
- Timeline
Phase - A column of the admin timeline. Starting registration is not one: it is
Engagementon the steps that wait on the student. Declared, and so ordered, in timeline order. - Timeline
Step - One step of the admin timeline. The Registrations list, the overview counts and the status card all name a row by this. Declared, and so ordered, in timeline order.
- WaitsOn
- Who a registration waits on. The first line of the status card and of a Needs attention row.