Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended audience: | Internal UBC |
| UDM Domain | Organization |
| Data Standard ID | DS0116 |
Definition
An Academic Unit is an organization type that represents a school, college, campus/senate, or other units within the institution. These units can recruit and admit learners, offer programs of study or courses and may facilitate key administrative functions, or administer student awards. An Academic Unit is also used with academic appointments.
Purpose
This standard aims to achieve consistency around the data created for Academic Unit across the University.
This standard applies to all UBC applications collecting and creating organization names. Exceptions are listed in the Dispensation section.
Standard
Compliance
The above standard for credentials must be complied at every stage of the data lifecycle with the exception of any dispensations (see Dispensation section).
- All applications must collect data 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.
Mapping of Invalid Values from System(s) of Record (SOR) to Common Services
A common service can only accommodate standard reference data enumerations that are available in the SoR as approved by the Data Governance Steering Committee or Data Trustee.
A reference data value that does not match any of the standard reference data value enumerations is considered ‘invalid’. Any records from a SoR containing an invalid reference data value for a given data element or attribute must be mapped as an 'empty' value in common service(s). Where a reference data value may potentially have the same meaning as a standard enumeration but named differently in the system of record can be corrected to match the appropriate standard enumeration. Please consult with the EDG team in such cases.
Additional Reference Data values in a SoR that are not part of the standard reference data enumerations are to be omitted in the common service.
Dispensation
Legacy systems are exempt from this data standard. As systems are replaced, adoption of this standard is required.
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.