Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Location |
| Intended Audience | Internal UBC |
Change Log
| Standard Version Date | Change Log |
|---|---|
| 2022-12-12 |
Mapping of Invalid values From Systems(s) of Record (SoR) to Common Services sub-section of Compliance section added |
| 2022-03-09 | Reference Data Compliance for Data Integration sub-section of Compliance section added |
Purpose
This standard aims to achieve consistency around the data collected for building Floors across the University (Vancouver and Okanagan campuses), and the format in which it is collected and stored across the University.
This standard applies to all UBC applications collecting Floor information. Exceptions are listed in the Dispensation section.
Standard
Definition: A structural level in a Building or in a Building subdivision as defined in UBC's Building and Records Data Standards.
Note: Each building may have one or more floors, and each floor represents one entire level of that building (e.g.: Level 200, Basement A, Floor 2, etc.).
A floor can be related to a records ID to distinguish the floor area belonging to a wing or addition to a building, for operational purposes.
For example: VBL10409 – Biological Sciences Building will have Floor Levels 1 to 4 measuring 200 square meters on each plane. Biological Sciences Building West Wing will also have floor levels 1 to 4 and will have an area of 50 square meters as it is measured for the specified wing.
| Attribute | Requirement | Definition |
|---|---|---|
| Building UID | Required | Generated ID in ArcGIS, that uniquely identify every building. |
| Record ID | Required | The unique identifier for the Record that the Floor is located in, as documented in the Records dataset. |
| Floor UID | Required | Auto generated ID by Archibus, that uniquely identifies every floor in each building. |
| Floor Code | Required | A number that represents the floor level. Floor numbers can be represented by a decimal number if the level is between two floors (i.e.: mezzanine) Floor Level below grade is represented by a negative number. |
| Floor Name | Required | General or descriptive name of a Floor in a building. |
Compliance
This standard about Floor must be complied with every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect Floor 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. Examples of legacy systems are:
- Student Information System (SIS)
As systems are replaced, adoption of this standard is required.
As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.
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.