...
Values for requisite_code were discussed on the dev list.
TBD
| Code | Definition |
|---|---|
| PRE | requiring_course_code requires that required_course_code be taken in a previous term |
| PRE_CO | requiring_course_code requires that required_course_code be taken in a previous term or concurrently |
| CO | requiring_course_code requires that required_course_code be taken in concurrently |
Trying to use only two requisite_code values to model a bi-directional "Co" restriction will not work. E.g. BIO+BIO_LAB must be taken as a pair. If you model BIO->BIO_LAB (Pre-Co) and BIO_LAB->BIO (Pre-Co), then you'll catch cases where they're taken independently and *only* independently. But if you have a plan where they're taken as a pair in one term, but then BIO is added again in a later term, the mistake won't be caught.
Feature Set 5 Operational Data Model
...