...
Notes I may well get rid of EnrollmentSets in 2.4; I'm not clear on what the impact would be at this point, but we don't pass grades out and up. (otoh they are there and work so what the hey) I may also push the 'Dept' mapping up into a hierarchy which represents our backend, translating current 'Dept' records into 'Subject' and mapping our Organizations directly. ~caseyd Unlicensed user
U. Arizona
UC Berkeley
The major types of institutional data at UC Berkeley are Term, Department, Course, Primary Section, and Secondary Section. Primary Sections play the central registrar role: they're what holds official enrollment data, decides the instructor of record, determines the number of units available, the allowable set of grading schemes, and cross-listings. In SIS's consolidated enterprise database, "Course" is not abstracted as a separate object, but just consists of some fields that multiple Primary Sections share. However, a student is never enrolled in more than one Primary Section of a single Course, and only one final grade is given for a student-course combination. Secondary Sections hold memberships (generally drawn from the pool of students enrolled in all Primary Sections) but do not formally effect grading. TAs and GSIs tend to be assigned informally, outside the registrar systems. In most cases, the registrar drops management of Secondary Section membership after the first few weeks of class; some departments and courses prefer to handle their own section management from the beginning.
...