...
Info | ||
---|---|---|
| ||
|
MAP_STATUS_REPORT_COURSE_DETAILS
Column | Type | Notes |
---|---|---|
id | uuid | primary (technical) key, unique identifier |
report_id | uuid | foreign key to MAP_STATUS_REPORT(id) |
term_code | varchar | soft reference to EXTERNAL_TERM(code) |
formatted_course | varchar | soft reference to EXTERNAL_COURSE(formatted_course) |
course_code | uuid | soft reference to EXTERNAL_COURSE(code) Do we really need this? |
anomaly_code | varchar | code that identifies the specific course level violation |
anomaly_note | varchar | detailed information about specific course level violation |
modified_by | uuid | id of person modifying reference |
created_by | uuid | id of person creating reference |
modified_date | date | date modified |
created_date | date | date created |
object_status | enum | standard object status |
MAP_STATUS_REPORT_TERM_DETAILS
Column | Type | Notes |
---|---|---|
id | uuid | primary (technical) key, unique identifier |
report_id | uuid | foreign key to MAP_STATUS_REPORT(id) |
term_code | varchar | soft reference to EXTERNAL_TERM(code) |
anomaly_code | varchar | code that identifies the specific course level violation |
anomaly_note | varchar | detailed information about specific course level violation |
term_status | varchar(enum) | the on/off plan status of the term |
modified_by | uuid | id of person modifying reference |
created_by | uuid | id of person creating reference |
modified_date | date | date modified |
created_date | date | date created |
object_status | enum | standard object status |
...