Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended Audience | Internal UBC |
| UDM Domain | Academic |
| Data Standard ID | DG0085 |
Purpose
This standard aims to achieve consistency around the data collected for Course Standing, and the format in which it is collected and stored.
A Course Standing is an academic decision and its effect on the student's progress in a course.
This standard is derived by UBC and applies to all applications collecting Course Standing. Exceptions are listed in the Dispensation section below.
Standard-Under Review
The following are the accepted values for Course Standing:
Course Standing Attributes
| Accepted Value | Code | Proposed Definition (under review and not final) |
|---|---|---|
| Adjudicated Pass | J |
A standing granted to a student where credit is granted and the course need not be repeated, although it may not normally qualify as a prerequisite for further work. (The grade assigned by the instructor is used in the calculation of averages.) |
| Aegrotat | AEG |
A permanent standing granted to a student that gives credit for a course even though the course requirements have not been completed due to an academic concession (see Academic Concession). This standing is awarded only in rare cases if the course instructor and the dean agree that the student has demonstrated the capacity to deal with the course material satisfactorily. When AEG standing is awarded, a letter grade is assigned. This will be converted to the minimum percentage for that category for the calculation of averages. |
| Audit | AUD |
A standing granted to a student who has Audit Status and has officially completed all course requirements except the final exam. The student may be given Fail (F) standing if their performance is not satisfactory. |
| Challenge | CH |
A standing granted to a student that gives credit for a course when the student meets the minimum required percentage grade on the challenge exam. The percentage grade for the challenge exam is entered as the grade for the course as long as the student meets the minimum grade required to earn challenge credit. No standing or percentage grade is recorded if the student does not meet the minimum grade required on the exam to earn challenge credit. |
| Deferred Standing | SD |
A temporary standing granted to a student when they have a valid reason for not completing course requirements as scheduled (see Academic Concession). Students granted Deferred standing in Winter Session courses must complete all outstanding course requirements by August 23 following. Students granted Deferred standing in Summer Session courses must complete all outstanding work by December 25 following. Students granted Deferred standing are responsible for making satisfactory arrangements with their instructors for completion of outstanding course requirements. If a student fails to complete deferred requirements by the dates specified, the Deferred standing will be replaced with a grade or standing that reflects requirements completed in the course. Students unable to meet the specified deadlines because of further medical, emotional or other difficulties must make an additional application for Academic Concession no later than August 31 for Winter Session courses or December 31 for Summer Session courses following the original deferral. See Deferred and Supplemental Examinations. |
| Exempt | Ex |
A standing granted to a student who has registered for a required course from which they are exempt. |
| Prior Learning Assessment | PLA |
A standing granted to a student that is assigned based on demonstrated competency through prior learning in a subject area. This standing can be used for a student in a course with a Graded or Pass/Fail Grading Basis. |
| Withdrawal | W |
A standing granted to a student that denotes official withdrawal. See Change of Registration for the Okanagan Academic Calendar withdrawal policy, and Withdrawal for the Vancouver Academic Calendar withdrawal policy. |
| Course in Progress | CIP |
Please contact the Enterprise Data Governance team for more information. |
| Externally Graded | EXG |
Please contact the Enterprise Data Governance team for more information. |
| Internal Articulation | IA |
Please contact the Enterprise Data Governance team for more information. |
| Missing Grade | MG |
Please contact the Enterprise Data Governance team for more information. |
| Supplemental | S |
Please contact the Enterprise Data Governance team for more information. |
| Thesis | T |
Please contact the Enterprise Data Governance team for more information. |
| Transfer Credit | TR |
Please contact the Enterprise Data Governance team for more information. |
Compliance
This standard must be complied with every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect date 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.
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)
As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.