Course Enrolment Hold Type Data Standard

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 Hold Type, and the format in which it is collected and stored.

Enrolment Hold Type is the category for temporarily blocking enrolment until the student acts on the reason for the hold.

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 hold type.

Enrolment Hold Type

Accepted Value	Description
Enrolment Add Hold	Condition(s) that inhibit(s) a student from enrolling into course sections. Example: Past Due Fees
Full Enrolment Hold	Condition(s)s that inhibit(s) a student from adding, dropping or swapping course sections.
Silent Full Enrolment Hold	Similar to Full Enrolment Hold but only visible to administrators.

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)