Intended Audience and Contact Information
Contact | Chief Data Officer, Office of the CIO |
---|---|
Intended Audience | Internal UBC |
UDM Domain | Demographic Data |
Data Standard ID | DG0077 |
Purpose
This standard aims to achieve consistency around the data collected for Language Proficiency, and the format in which it is collected and stored in across the University.
Language proficiency refers to the ability to understand and communicate in a language for academic or technical purposes.
This standard is derived by UBC and applies to all applications collecting information on Language Proficiency. Exceptions are listed in the Dispensation section.
Standard
The following are the accepted values associated with demographic language(s) first learned at home in childhood:
Accepted Data Value |
---|
Arabic |
Cantonese |
English |
Persian |
Filipino |
French |
German |
Hindi |
Indigenous language, please specify: [open text] |
Japanese |
Korean |
Mandarin |
Punjabi |
Russian |
Spanish |
Tagalog |
Urdu |
Vietnamese |
If not listed above, please specify: [open text] |
I choose not to disclose |
Accepted Data Value |
---|
Arabic |
Cantonese |
English |
Persian |
Filipino |
French |
German |
Hindi |
Indigenous language, please specify: [open text] |
Japanese |
Korean |
Mandarin |
Punjabi |
Russian |
Spanish |
Tagalog |
Urdu |
Vietnamese |
If not listed above, please specify: [open text] |
I choose not to disclose |
Accepted Data Value | Definitions |
---|---|
Listening/speaking: Advanced Level | A person who can contribute to meetings and seminars within their own area of work or keep up a conversation with a good degree of fluency, while also coping with abstract expressions. |
Listening/speaking: Intermediate Level | A person who can follow or give a talk on a familiar topic or keep up in a conversation in a wide range of topics. |
Listening/speaking: Entry Level | A person who can express their opinions on some abstract or cultural topics in a limited way. A person who can offer advice within a known area and understand instructions or public announcements. |
Reading: Advanced Level | A person who can read quickly enough to cope with an academic course, read the media for information, or understand non-standard correspondence. |
Reading: Intermediate Level | A person who can scan texts for important information and understand detailed instructions or advice. |
Reading: Entry Level | A person who can understand routine information and articles, and the general meaning of non-routine information within a familiar area. |
Writing: Advanced Level | A person who can prepare and draft professional correspondence, take reasonably accurate notes in meetings, or write an essay, which shows an ability to communicate. |
Writing: Intermediate Level | A person who can take notes while someone is talking or write a letter using more complex language. |
Writing: Entry Level | A person who can write letters or make notes on familiar or predictable matters. |
Data Trustee
For Student Data: Registrar
For Employee (Staff and Faculty) Data: Associate VP, Equity and Inclusion Office
Data Steward
Vancouver Student Data: Deputy Registrar, UBCV
Okanagan Student Data: Deputy Registrar, UBCO
Faculty and Staff Data: Associate VP, Equity and Inclusion Office
Purpose for Collection
In alignment with UBC's commitments to inclusive excellence and anti-racism and in support of numerous strategic initiatives aiming to advance equity, diversity, and inclusion at UBC, data will be used to enable the university to better understand a person's experience at UBC, support inclusion and success, and assess progress of equity, diversity, and inclusion.
- Equity: Collected data can support the institution to improve its understanding of a person's accessibility to the resources they need to succeed, to improve their UBC journey and to positively enhance their overall experience. Collected information may also signal systemic barriers and inequities where they exist including observation of patterns or trends with respect to recruitment, retention, participation, engagement, learning, performance, success, and support for individuals.
- Diversity: Collected data will improve understanding of the nuance and complexity of UBC's diverse community including how it compares with other institutions or communities, and how it changes or needs to change over time. Understanding the different diverse groups will enhance UBC's allocation of resources to ensure equitable treatment and opportunities for all individuals regardless of their identity or background.
- Inclusion: Collected data will inform the understanding of the extent to which experiences may differ for people of different identities and backgrounds. This includes the extent to which a person feels welcome, respected, and that they belong.
Process for Collection
This data must be self-declared, and not derived or collected from a third party. An individual can update their response at any time.
Pre-Approved Data Access in the System of Record
- PAIR
- EIO
- Enrolment Services
Data Access Request Process for All Others
If your department is not listed in the Pre-Approved Data Access section above, a Data Access Request (DAR) is needed. Visit ACCESS UBC DATA for more information and to access a Data Access Request form.
Data can only be shared at an aggregated level. If case-level data is needed, approval must come from the Data Access Committee.
Guideline on Phrasing of Questions in a Survey
- What language(s) did you first learn at home in
childhood and still understand? Please select all that apply. - Which languages do you know well enough to conduct an
academic or technical conversation? Please select all that apply. - How would you assess your academic or technical language proficiency according to listening/speaking, reading, and writing?
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.
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.
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.