...
Primary Source(s) - BANNER Instructor Assignment table (sirasgn), BANNER Section table (ssbsect)
Secondary Source(s) - Mothra Person Table (ucd_person_t)
EID(s) - http://ucdavis.edu/course/enrollmentset/sirasgn.sirasgn_crn/sirasgn.sirasgn_term_code/instructor/sirasgn.sirasgn.pidm
Description - The OfficialInstructors object is a simple mapping of person eids to enrollmentsets and sections for the purposes of denoting instruction assignment.
Derived Values - In the event of blank description or title date, '(Description Unavailable)' is rendered instead.None
Mapping Issues - In order to reproduce the section eid, the ssbsect table must be joined on the mview query. (The unique columns for the section_eid are not stored in the sirasgn table. This table is eligible for mview fast refresh under the simple join condition. This is effected by capturing the rowids of the two source tables.
This object also needs to capture a person eid, which we have identified as the Mothraid of the person. The Banner source data uses pidm to uniquely identify users in its system. Therefore, a lookup from pidm to mothraid must be performed. This is currently done via a view, but other methods are under investigation.
Data Issues: Ideally, the Banner data would only record one instance of an instructor assigned to one course. However, there are isolated cases in which the same instructor is assigned to a section multiple times. Normally, a distinct clause would be able to eliminate the extra assignments, but in this case that would break the fast-refresh of this table. Since we want up to date instructor assignments, we will need to find another way of weeding out the extra assignments.
...
Primary Source(s) - BANNER Student Registration table (sftstcr)
Secondary Source(s) - Mothra Person Table (ucd_person_t)
EID(s) - http://ucdavis.edu/course/enrollmentset/sfrstcr.sfrstcr_crn/sfrstcr.sfrstcr_term_code/sfrstcr.sfrstcr_rsts_code/mothra_person.mothraid
Description - The Enrollment object records all of the data required to notate an student registration to an enrollmentset / section.
Derived Values - In the event of blank description or title date, '(Description Unavailable)' is rendered insteadThe dropped column is derived by classifying all registration codes other than 'RE' and 'WL' as drops.
Mapping Issues - This object needs to capture a person eid, which we have identified as the Mothraid of the person. The Banner source data uses pidm to uniquely identify users in its system. Therefore, a lookup from pidm to mothraid must be performed. This is currently done via a view, but other methods are under investigation.
Data Issues: Ideally, the Banner data would only record one instance of an student assigned to one course. However, there are cases in which the same student is registered to a section multiple times. As opposed to the Instructor assignment case, it is possible to differentiate the enrollments by adding the registration status into the eid. While a student may be registered multiple times, it is always with a different registration code.
...
Field
...
Datasource
...
Reference
...
eid
...
BANNER
...
enrollmentset_eid
...
BANNER
Meeting (MeetingCmImpl)
Primary Source(s) - BANNER Section Meeting table, (ssrmeet), BANNER Section table (ssbsect)
Secondary Source(s) - Mothra Person Table (ucd_person_t)
EID(s) - http://ucdavis.edu/course/section/
...
...
person_eid
...
BANNER
...
mothra_person.mothraid (sfrstcr.sfrstcr_pidm)
...
EnrollmentStatus
...
BANNER
...
sfrstcr.sfrstcr_rsts_code
...
Dropped
...
BANNER
...
case when sfrstcr.sfrstcr_rsts_code IN ('RE','WL') then 0 else 1 end
...
Credits
...
BANNER
...
sfrstcr.sfrstcr_credit_hr
...
GradingScheme
...
BANNER
...
sfrstcr.sfrstcr_gmod_code
...
createdBy
...
...
'BANNER'
...
createdDate
...
BANNER
...
sfrstcr.sfrstcr_activity_date
...
lastModifiedBy
...
...
'BANNER'
...
lastModifiedDate
...
BANNER
...
sfrstcr.sfrstcr_activity_date
Meeting (MeetingCmImpl)
...
Field
...
Datasource
...
Reference
...
eid
...
BANNER
...
section_eid
...
BANNER
...
StartTime
...
BANNER
...
ssrmeet.ssrmeet_begin_time
...
EndTime
...
BANNER
...
ssrmeet.ssrmeet_end_time
...
Location
...
BANNER
...
ssrmeet.ssrmeet_bldg_code ssrmeet.ssrmeet_room_code
...
Sunday
...
BANNER
...
ssrmeet.ssrmeet_sun_day
...
Monday
...
BANNER
...
ssrmeet.ssrmeet_mon_day
...
Tuesday
...
BANNER
...
ssrmeet.ssrmeet_tue_day
...
Wendesday
...
BANNER
...
ssrmeet.ssrmeet_wed_day
...
Thursday
...
BANNER
...
ssrmeet.ssrmeet_thu_day
...
Friday
...
BANNER
...
ssrmeet.ssrmeet_fir_day
...
Saturday
...
BANNER
...
ssrmeet.ssrmeet_sat_day
...
Notes
...
...
...
createdBy
...
...
'BANNER'
...
createdDate
...
BANNER
...
ssrmeet.ssrmeet_activity_date
...
lastModifiedBy
...
...
'BANNER'
...
lastModifiedDate
...
BANNER
...
SSRMEET_TERM_CODE/SSRMEET_CRN/SSRMEET_BLDG_CODE/SSRMEET_ROOM_CODE/SSRMEET_BEGIN_TIME/SSRMEET_END_TIME/SSRMEET_CATAGORY/SSRMEET_MON_DAY/SSRMEET_TUE_DAY/SSRMEET_WED_DAY/SSRMEET_THU_DAY/SSRMEET_FRI_DAY/SSRMEET_SAT_DAY/SSRMEET_SUN_DAY|
Description - The Enrollment object records all of the data required to notate an student registration to an enrollmentset / section.
Derived Values - The begin and end times are recorded as strings and must be converted to an Oracle timestamp in order for Hibernate to use them.
Mapping Issues - In order to reproduce the section eid, the ssbsect table must be joined on the mview query. (The unique columns for the section_eid are not stored in the ssrmeet table.)
Data Issues: This table is a case study in dirty data, lack of primary keys, and bad enforcement of business rules. In short, almost every column in the table is required in order to resolve a unique eid.
Section Category (BANNER_SECTION_CATEGORY)
...