Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | All |
| Intended Audience | Internal UBC |
| Data Standard ID | DG0092 |
Purpose
This standard aims to achieve consistency around data collected for for Calendar Date Format. Conformance to this guideline will allow for consistency and removal of doubt that can result from the various day–date conventions, cultures, and time zones that impact a global operation. It gives a way of presenting dates that are clearly defined and understandable to both people and machines.
Standard
This standard is based on (ISO) 8601-1:2019(en) Date and time — Representations for information interchange — Part 1: Basic rules.
The order of the elements used to express a Calendar Date in ISO 8601 is as follows: year, month, and day, separated by a hyphen.
YYYY-MM-DD
Where:
YYYY = the numeric value representing the year
MM = the double-digit numeric value representing the month
DD = the double-digit numeric value representing the day
For example, September 7, 2023 is represented as 2023-09-07.
Compliance
The above guidelines 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. Examples of legacy systems are:
- Student Information System (SIS)
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.