Expand description
Our grade in the study registry’s terms. A scale or grade the registry does not know is rejected
at request level, taking the whole batch of twenty-five with it, so every pair that reaches a
batch has been through map_grade or is_known_grade.
Structs§
- Grade
Source - What the completion says and what the module and the chosen enrolment say the scale should be.
- Mapped
Grade
Enums§
- Grade
Comparison - How a grade stands against one the registry already holds.
- Grade
Scale Family
Constants§
- FAIL_
GRADE_ ID - MAX_
NUMERIC_ GRADE - NUMERIC_
GRADE_ SCALE_ ID - PASS_
FAIL_ GRADE_ SCALE_ ID - TODO: Suotar has not confirmed the spelling. Both are accepted on the way in; this is the one we send.
- PASS_
FAIL_ GRADE_ SCALE_ ID_ ALT - The other accepted spelling of the same scale, which our own legacy pull path sends.
- PASS_
GRADE_ ID
Functions§
- compare_
grades - Whether
candidateis worth pushing overregistered, which is the frozen pair of an attempt the registry accepted. - grade_
rank 🔒 - Where a grade sits within its own scale. Comparable only against another rank of the same scale.
- grade_
scale_ family - is_
known_ grade - Whether a frozen pair is one the registry will accept. Checked again before batching: an unknown pair is a request-level rejection, so one bad row would fail twenty-four good ones.
- map_
grade - Maps a completion into the scale the registry expects, preferring what it told us to a guess.
- same_
grade_ scale - Whether two scale ids name the same scale. The pass/fail id has two spellings in circulation, so comparing the strings would call an attainment we ourselves registered a different scale.