Religion and Spirituality Data Standard

Intended Audience and Contact Information

Contact Chief Data Officer, Office of the CIO
Intended audience Internal UBC
UDM Domain Person Domain
Data Standard ID DG0064

Purpose

This standard aims to achieve consistency around the data collected for a Religion and Spirituality, and the format in which it is collected and stored in across the University.

Religion, also known as Religious Affiliation, Faith, Belief System or Religious Denomination, refers to a person's connection or affiliation with any religious denomination, group, body, sect, or other religiously defined community or system of belief. Religion is not limited to formal membership in a religious organization nor a currently practicing member of that group.

Spirituality refers to a person's contemplation of a deep sense of being, which is separate from the material world. Spirituality may or may not be related to a specific religious affiliation or the existence of a greater being.

This standard is derived by UBC and applies to all applications collecting Religion and Spirituality. Exceptions are listed in the Dispensation section.

Standard

The following are the accepted values for a person's high-level affiliation with Religion and Spirituality:

Religion and Spirituality Accepted Values
Accepted Data Value Description
Buddhism An eastern and central Asian religion or philosophical tradition practiced by Buddhists.1,3
Christianity An Abrahamic, monotheistic religion practiced by Christians. Denominations include Catholic, Protestant, and Orthodox branches.2,3
Hinduism An Indian religion or dharma practiced by Hindus.1,2,4
Indigenous Spiritual Tradition or Practices Spiritual beliefs and practices that Indigenous peoples identify as being "traditional" or "customary" among their communities.3
Islam An Abrahamic, monotheistic religion practiced by Muslims.1,2 Denominations include Sunni, Shia, etc.
Judaism An Abrahamic, monotheistic, and ethnic religion practiced by Jews.1,4
Sikhism A religion and philosophy founded in the Punjab region of the Indian subcontinent, practiced by Sikhs.1,4
I am spiritual but do not belong to any specific religious affiliation. Response for a person who is spiritual but does not affiliate with a religion.
I am not religious or spiritual Response for a person who does not identify or affiliate with a religion or spiritual practice, such as non-religious, atheist, or agnostic.
I am not sure Response for a person who does not know if they are spiritual or have an affiliation with a religion.
If not listed above, please specify: _____________ Response for a person that identifies with a religion or spirituality that is not listed.
Choose not to disclose Response for someone who chooses not to disclose.
Unknown* A person did not select any of the above accepted values at the time of data collection. It may or may not get updated at a later point in time.

*This value is only to be used in integrations where the consuming system does not allow a blank value. It should not be made available in the picklist.

1https://www.merriam-webster.com/dictionary
2 https://www.oxfordlearnersdictionaries.com/us/
3 https://www.britannica.com
4 https://dictionary.cambridge.org/dictionary/

Guideline for Data Collection

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

  • Please indicate whether you identify with any of the following high-level religious and/or spiritual beliefs. Select all that apply.

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.

Related Documents