Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended Audience | Internal UBC |
| UDM Domain | Organization |
| Data Standard ID | DG0097 |
Change Log
| Standard Version Date | Change Log |
|---|---|
| 2024-03-28 | Data standard published |
Definition
A UBC Senate UBC Senate is a governing body that is responsible primarily for academic matters, and also acts as a curriculum approving body for the relevant campus as per the University Act. UBC Senates also act as Curriculum Approving Bodies; for more information on Curriculum Approving Body please see the Curriculum Approving Body Data Standard.
Purpose
This standard aims to document accepted values for UBC Senate.
This standard is derived by UBC and applies to all applications collecting UBC Senate. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for UBC Senate:
| Accepted Value | University Glossary Term | Code | Definition |
|---|---|---|---|
| UBC Okanagan Senate | UBC Okanagan Senate [UBC Senate ] | UBC-O |
The Senate that has responsibilities pertaining to the Faculties of UBC’s Okanagan campus. The Okanagan Senate also acts as a Curriculum Approving Body; see the Curriculum Approving Body Data Standard for more information. |
| UBC Vancouver Senate | UBC Vancouver Senate [UBC Senate] | UBC-V |
The Senate that has responsibilities pertaining to all aspects of the university other than those specified for the Okanagan Senate. The Vancouver Senate also acts as a Curriculum Approving Body; see the Curriculum Approving Body Data Standard for more information. |
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 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.
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)
In Workday Student, for defined learning instances such as program of study or course, the "Allowed Location" field utilizes the values "UBC Vancouver" and "UBC Okanagan" as values representing the Senate Location tied to the approving Senate.
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.