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

Waitlist Method Type is the way a waitlist for a course section is processed by the application when a seat becomes available

This standard is derived by UBC and applies to all applications collecting. Exceptions are listed in the Dispensation section.

Standard

The following are the accepted values for waitlist method type.

Waitlist Method Type

Accepted Value	Description
Enrolment Auto-promotion	A waitlist process whereby, when a seat becomes available, the first student on the waitlist is automatically enroll into the course section provided eligibility rules are met.
Enrolment Expiration	A waitlist process whereby, when a seat becomes available, a notification is sent to the first student on the waitlist to add the course section within a pre-set period of time, after which the notification goes to the next student if they fail to add the course section within the allotted time.

Compliance

This standard about postal address must be complied with through every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):

All applications must collect the 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)