Intended Audience and Contact Information
Contact | Chief Data Officer, Office of the CIO |
---|---|
UDM Domain | Person |
Intended Audience | Internal UBC |
Data Standard ID | DG0036 |
Change Log
Standard Version Date | Change Log |
---|---|
2023-11-20 | Standard revised to correct misrepresentation of ISO countries that do not qualify as Citizenship values. |
2022-12-12 | Mapping of Invalid values From Systems(s) of Record (SoR) to Common Services sub-section of Compliance section added |
2022-03-09 | Reference Data Compliance for Data Integration sub-section of Compliance section added |
Purpose
This standard aims to achieve consistency around the data collected for Citizenship and the format in which it is collected and stored.
Citizenship is the legally acquired status and established legal relationship between individual and State that confers political, civil, and social rights. A person may have more than one Citizenship. A person may be stateless, that is, they may have no Citizenship. Citizenship can be by birth or naturalization.
Citizens have certain rights, duties, and responsibilities that are denied or only partially extended to aliens and other noncitizens residing in a country. In general, full political rights, including the right to vote and to hold public office, are predicated upon Citizenship.
A person's Citizenship may be different from their nationality, country of origin, country of birth or country in which they reside.
At UBC, the Citizenship for a worker or student who is not a Canadian Citizen or Canadian Permanent Resident may be verified using the official document in which their respective work or study permit is issued by Immigration, Refugees and Citizenship Canada (IRCC).
This standard is based on the Statistics Canada Classification of Country of Citizenship and applies to all UBC applications collecting Citizenship. Exceptions are listed in the Dispensation section. Standard
Standard
The list of Citizenship available as part of the Statistics Canada Classification of Country of Citizenship standard has been adopted1 by UBC to refer to for Citizenship.
Citizenship information of a person must only be collected "when it relates directly to and is necessary for a program or activity of UBC, and only from the individual, rather than from a third party".
Refer to the approved values list associated with Citizenship.
1Some exceptions apply.
This is the status of an individual who has Citizenship in more than one country or state.
A person may have more than one Citizenship; therefore, applications must allow the ability to select more than one value for Citizenship.
This is the accepted value for an Individual who is not considered a citizen under the operation of the laws of any country or state.
These individuals will be accommodated in the standard using the following accepted value:
Accepted Data Value | UBC adopted user-assigned ISO 3166-1 alpha-2 | UBC adopted user-assigned ISO 3166-1 alpha-3 |
---|---|---|
Stateless |
XS |
XSS |
Information captured for any of the accepted Citizenship data values above need to have an 'Effective Start Date' and an 'Effective End Date'. When the Citizenship status of a person changes, effective start and end dates must be captured.
Accepted Data Value |
Definition |
---|---|
Effective Start Date |
A particular day represented within a calendar year on which a person is legally recognized, either native or naturalized, to be a citizen. |
Effective End Date |
A particular day represented within a calendar year on which a person ceases to be a citizen. |
Compliance
Compliance to this standard is required at every stage of the data lifecycle with the exception of dispensations listed on the Dispensation section.
- Applications where Citizenship information is collected, must collect this information 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.
Refer to the table below for a list of countries and the mapping to the correct Citizenship value.
ISO Country Name | Accepted Value for Citizenship | Alpha-3 |
---|---|---|
Norfolk Island | Australia | AUS |
Christmas Island | Australia | AUS |
Cocos (Keeling) Islands | Australia | AUS |
Faroe Islands | Denmark | DNK |
Greenland | Denmark | DNK |
Åland Islands | Finland | FIN |
French Polynesia | France | FRA |
Mayotte | France | FRA |
Guadeloupe | France | FRA |
New Caledonia | France | FRA |
Reunion | France | FRA |
Saint Martin | France | FRA |
French Guiana | France | FRA |
Martinique | France | FRA |
Saint Pierre and Miquelon | France | FRA |
Saint Barthelemy | France | FRA |
Wallis and Futuna | France | FRA |
Bonaire, Sint Eustatius, and Saba | Netherlands | NLD |
Curaçao | Netherlands | NLD |
Sint Maarten | Netherlands | NLD |
Aruba | Netherlands | NLD |
Niue | New Zealand | NZL |
Cook Islands | New Zealand | NZL |
Tokelau | New Zealand | NZL |
Svalbard and Jan Mayen | Norway | NOR |
Jersey | United Kingdom - British citizen | GBR |
Guernsey | United Kingdom - British citizen | GBR |
Isle of Man | United Kingdom - British citizen | GBR |
United Kingdom | United Kingdom - British citizen | GBR |
England | United Kingdom - British citizen | GBR |
Wales | United Kingdom - British citizen | GBR |
Northern Ireland | United Kingdom - British citizen | GBR |
Scotland | United Kingdom - British citizen | GBR |
Sark | United Kingdom - British citizen | GBR |
Channel Islands | United Kingdom - British citizen | GBR |
Falkland Islands | United Kingdom - Overseas Territories Citizen | XGB |
Gibraltar | United Kingdom - Overseas Territories Citizen | XGB |
Montserrat | United Kingdom - Overseas Territories Citizen | XGB |
British Indian Ocean Territory | United Kingdom - Overseas Territories Citizen | XGB |
British Virgin Islands | United Kingdom - Overseas Territories Citizen | XGB |
Bermuda | United Kingdom - Overseas Territories Citizen | XGB |
Saint Helena, Ascension and Tristan da Cunha | United Kingdom - Overseas Territories Citizen | XGB |
Pitcairn | United Kingdom - Overseas Territories Citizen | XGB |
Turks and Caicos Islands | United Kingdom - Overseas Territories Citizen | XGB |
Anguilla | United Kingdom - Overseas Territories Citizen | XGB |
Cayman Islands | United Kingdom - Overseas Territories Citizen | XGB |
Puerto Rico | United States of America | USA |
Northern Mariana Islands | United States of America | USA |
Guam | United States of America | USA |
United States Minor Outlying Islands | United States of America | USA |
U. S. Virgin Islands | United States of America | USA |
American Samoa | United States of America | USA |
Western Sahara | Stateless | XSS |
Dispensation
Legacy systems are exempt from this data standard. Examples of legacy systems are:
- Student Information System (SIS)
As systems are replaced, adoption of this standard is required.
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.