Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended audience | Internal UBC |
| UDM Domain | Admissions |
| Data Standard ID | DG0105 |
Definition
An Admission Application Choice Offer is the offer given to an applicant on the authority of the University based on the Admission Evaluation of their Completed Admission Application for entry into a Program of Study that may or may not lead to one or more Credential(s).
An Admission Offer Status is the code that indicates the status of an applicant’s Admission Application Choice Offer.
Purpose
This standard aims to achieve consistency around the data collected for Admission Offer Status, and the format in which it is collected and stored.
This standard is derived by UBC and applies to all applications collecting Admission Offer Status. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for Admission Offer Status:
| Accepted Value | Code | University Glossary Term | Definition |
|---|---|---|---|
| Accepted Offer | ACPT | Accepted Offer [Admission Offer Status] | The Admission Applicant has indicated that they are accepting their offer of admission. |
| Declined Offer | DECL | Declined Offer [Admission Offer Status] | The Admission Applicant has indicated that they are not accepting their offer of admission. |
| No Response | NRSP | No Response [Admission Offer Status] | The default value when an Admission Applicant has received an offer of admission and has not yet responded. This value would also remain on the Admission Application Choice after the offer deadline if the applicant does not respond by the deadline. |
| Late Decline | LDCL | Late Decline [Admission Offer Status] | Used in the case of an Admission Application Choice where the applicant had previously accepted an offer of admission but has now subsequently declined. |
| Cancel Decision | CNCL | Cancel Decision [Admission Offer Status] |
The Admission Applicant has accepted an offer of admission to another Admission Application Choice within the same Admission Application, and has confirmed that they will keep that offer of admission and no longer wish to be considered for admission for this Admission Application Choice or any alternate Admission Application Choices within that application. The CNCL Admission Offer Code is only used for applications that allow the applicant to select more than one Admission Application Choice on the same application. This code is applied to the Admission Application Choices that the applicant no longer wishes to be considered for. |
| Wait for Pending Decision | PEND | Wait for Pending Decision [Admission Offer Status] |
The Admission Applicant has accepted an offer of admission on another Admission Application Choice, but they have indicated that that they are still awaiting a decision for this Admission Application Choice. This Admission Application Choice will remain active until the Admission Evaluation for this choice has been completed. The PEND Admission Offer Code is only used for applications that allow the applicant to select more than one Admission Application Choice on the same application. This code is applied to the Admission Application Choice that has not yet been evaluated. |
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.
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.