Skip to main content

Module grade_mapping

Module grade_mapping 

Source
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§

GradeSource
What the completion says and what the module and the chosen enrolment say the scale should be.
MappedGrade

Enums§

GradeComparison
How a grade stands against one the registry already holds.
GradeScaleFamily

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 candidate is worth pushing over registered, 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.