...

Feature Set 6 Operational Data Model Notes

No Changes

Feature Set 7 - Transcripted Course

Feature Set 7 External Data Model

Feature Set 7 External Data Model Schema

Feature Set 7 External Data Model Dictionary

Feature Set 7 External Data Model Notes

No new external tables.

The basic requirement is to indicate to the end user whenever viewing a plan or adding/editing a course to/in a plan when that course already appears in the user's transcript. Per Jason, "The business requirement is to check the planned courses to see if the student took them....Speed and accuracy are the keys." Because of that (esp the "accuracy" part), we're not going to copy a "transcripted" flag/status onto the operational model. Determining whether or not a planned course is already transcripted will always be a transient join/lookup.

There are two types of checks for an already transcripted course:

 Backward-looking:

select 1 from v_external_student_transcript_course
where school_id = :plan_student_id 
and formatted_course = :planned_formatted_course

Forward-looking: 

select 1 from v_external_student_transcript_course
where school_id = :plan_student_id 
and formatted_course = :planned_formatted_course
and term_code in (select term_code from external_course_term where course_code = :planned_formatted_course)

Our transcript table/s do not know about course code. We accept the potential ambiguity despite the stated priority of "accuracy". That value is likely just not available in transcript feeds.

Feature Set 7 Operational Data Model

Feature Set 7 Operational Data Model Schema

Feature Set 7 Operational Data Model Dictionary

Feature Set 7 Operational Data Model Notes