Grading scheme mappings

So the new gradebook stuff using CM is starting to reveal itself to my passive intellect....

Each enrollment has an grading scheme code, we knew this, that is why Brian wired it up in the external mviews....

Banner (actually our mview banner_gradingscheme) has these codes and their descriptions:

Now imagine yourself mapping grading scales to some scale indicated by each code in this table....

1. Instructor chooses and Grading Scale for the course

• this is the old 2.1.x notion of a grading scale: Letter Grade, Letter Grade With Plus/Minus, etc.

2. When final grades a calculated, the number which 'is' the grade for the student in mapped to the grading scale (in #1)

3. Each student's grading scheme is looked up in CM, and her mapped value from #2 is converted to an acceptable final grade for that scheme

• an 'acceptable final grade' is one that will not cause the Final Grading Tool to barf for that student, and, presumably, accurately reflect the course work completed.

That means that for each grading scale we use, there are 12 mapping vectors required. We used 3 grading scales last go 'round, that would be 36 mappings ... is it feasible to think that each grading scheme warrants a grading scale as well? In that case, it would be 144 mappings.

Parting ponder-able: The final 'mapping' in #3 can be pretty arbitrarily defined... Berkeley's example uses spring injected lists to map 'A-' to 'P' for instance. But, we can calculate the proportion of dark matter in the Universe to determine our mapping, we don't have to use a static scale.

Questions:

1. What are the scales assoc.'d with each of the above codes?
2. what are the standard mappings from standard grading scales to the scales in #1?