Intended Audience and Contact Information
Contact | Chief Data Officer, Office of the CIO |
---|---|
UDM Domain | Academic |
Intended Audience | Internal UBC |
Purpose
This standard aims to achieve consistency around the data collected for Enrolment Status, and the format in which it is collected and stored. Enrolment Status is the state of a student enrolment in a course section. This standard is derived by UBC and applies to all applications collecting enrolment status. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for enrolment status.
Accepted Value | Description |
---|---|
Enrolled | The state that indicates a course section has been added on a student record. |
Un-Enrolled | The state that indicates a course section is dropped from a student record before the Drop Without Record End Date (refer to University glossary for definition). |
Withdrawn | The state that indicates a course section is dropped from a student record after the Drop Without Record End Date (refer to University glossary for definition). |
Completed | The state that indicates a student has finished a course section |
Waitlisted | The state that indicates a student has been added to a waitlist for a course section. |
Compliance
The above standard must be complied at every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect date as recommended in this standard.
- Enterprise Data Integration must adopt this standard.
Reference Data Compliance for Data Integration
The use of accepted reference data values in this standard for data integration among applications must comply with the enterprise integration pattern of leveraging the reference data common service API (Application Programming Interface) published in UBC MuleSoft Exchange.
Any application that intends to access real-time, case-level reference data should have the application owner or manager complete and submit a Request API Access form.
For any compliance questions or requests for a dispensation temporarily, please contact the Enterprise Data Governance Team.
Dispensation
Legacy systems are exempt from this data standard. As systems are replaced, adoption of this standard is required. Examples of legacy systems are:
- Student Information System (SIS)
Related Documents
None