Intended Audience and Contact Information
Contact | Chief Data Officer, Office of the CIO |
---|---|
Intended audience: | Internal UBC |
UDM Domain | Academic |
Purpose
This standard aims to achieve consistency around the data collected for Academic Level, and the format in which it is collected and stored.
This standard is derived by UBC and applies to all applications collecting Academic Level. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for Academic Level.
Accepted Data Value | Description |
---|---|
Undergraduate | Level for an undergraduate study learning opportunity. |
Graduate | Level for a graduate study learning opportunity. |
Academic Level Not Applicable | Level for a learning opportunity that is not undergraduate or graduate. |
Compliance
This standard must be complied with through every stage of the data lifecycle with the exception of any dispensations (see Dispensation section below):
- 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)
- Human Resource Management System (HRMS)
- Finance Management System (FMS)
Related documents
None