Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Learner Financial Support |
| Intended Audience | Internal UBC |
| Data Standard ID | DG0072 |
Purpose
This standard aims to achieve consistency around the data collected for Award Adjudication Method, and the format in which it is collected and stored.
Award Adjudication Method is the method for evaluating Award Applicants for a Student Award.
This standard is derived by UBC and applies to all applications collecting Award Adjudication Method. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values for Student Award Adjudication Method:
| Accepted Value | Code | Definition |
|---|---|---|
| Auto-Adjudication | AUAD |
Award Applicants are evaluated by the system based on set adjudication criteria for the Student Award. Examples include: Trek Excellence Scholarships, Deputy Vice-Chancellor Scholarships, International Tuition Award, International Four-Year Doctoral Partial Tuition Award |
| Single-Tier Adjudication Committee | STCO |
Award Applicants are evaluated by an adjudication committee. Examples include: Affiliation Scholarships, Aboriginal Graduate Fellowships |
| Two-Tier Adjudication Committee | TWCO |
Award Applicants go through two successive rounds of evaluation by an adjudication committee and/or set of subcommittees. Examples include: Premier Undergraduate and Wesbrook Scholarships - first round of adjudication is done through a Faculty adjudication committee (e.g., Arts) to narrow the candidate pool, and the selected candidates go through a second round of adjudication by Enrolment Services. |
| Three-Tier Adjudication Committee | THCO |
Award Applicants go through three successive rounds of evaluation by adjudication committees and/or sets of subcommittees. Examples include: Governor General’s Gold Medals - the department (e.g., Chemistry) adjudicates candidates for the first round, the disciplinary Faculty (e.g., Faculty of Science) adjudicates for the second round, and the central awards office (e.g., CoGS or G+PS) adjudicates for the third round. |
| External Adjudication | EXAD | Please contact the Enterprise Data Governance Team for more information. |
| Not Applicable | NOAP | Please contact the Enterprise Data Governance Team 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.
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.