Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended audience | Internal UBC |
| UDM Domain | Admissions |
| Data Standard ID | DG0089 |
Purpose
This standard aims to achieve consistency around the data collected for Readmission Type, and the format in which it is collected and stored.
Readmission Type is the subcategory used to drive workflow and dictate the specific Admission Evaluation criteria to be used for Admission Applicants with a Basis of Admission of UBC Student. This attribute is optional, and each Admission Application can only have one Readmission Type value assigned to it.
This standard is derived by UBC and applies to all applications collecting Readmission Type. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for Readmission Type:
| Accepted Value | Code | Definition |
|---|---|---|
| Readmission to New Program | REND | The Admission Applicant has completed a Program of Study at UBC, or has discontinued or been suspended or dismissed from their Program of Study at UBC, and is now applying to a new Program of Study. |
| Readmission to Same Program | RESP | The Admission Applicant has previously attended UBC and is reapplying to the same Program of Study. |
| Transfer to New Program | TRNP | The Admission Applicant is currently attending UBC and is applying to a new Program of Study governed by the same Senate. |
| Okanagan to Vancouver Student Campus Transfer | TROV | The Admission Applicant is currently attending a Program of Study administered by the Okanagan Senate and is applying to a Program of Study governed by the Vancouver Senate. |
| Vancouver to Okanagan Student Campus Transfer | TRVO | The Admission Applicant is currently attending a Program of Study administered by the Vancouver Senate and is applying to a Program of Study governed by the Okanagan Senate. |
Compliance
The above standard must be complied with at every stage of the data lifecycle except for 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.