Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended audience: | Internal UBC |
| UDM Domain | Location |
Change Log
| Standard Version Date | Change Log |
|---|---|
| 2022-04-20 |
Addition of Accepted Values for Address Usage, and their association with Address Types. |
| 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 Address Type and Address Usage, and the format in which it is collected and stored in across the University.
This standard applies to all UBC applications collecting Address Type and Address Usage. Exceptions are listed in the Dispensation section.
Standard
An Address attached to a person or organization may be categorized based on following attributes:
| Attribute | Requirement | Definition |
|---|---|---|
|
Address Type |
Required |
Classification of address based on its purpose. |
|
Address Usage |
Optional |
Classification of address based on its usage. |
|
Primary Address |
Optional |
Indicator of default address for communication. |
Accepted Data Values for Address Type
Following values are accepted at UBC for Address Type:
| Address Type | Definition |
|---|---|
| Home | The address where person lives either temporarily or permanently |
| Business | The address where a person performs day-to-day activities related to their job or where an organization conducts commercial activity |
| Work | The address where a person performs day-to-day activities related to their job. |
Data Rules for Address Type
| Accepted Data Value | Data Rule |
|---|---|
| Home | Only a person may have this type of address. |
| Business | A person or organization may have this type of address. |
| Work | Only a person may have this type of address. |
A person or organization may have multiple addresses of each Address Type.
A unique address may have more than one value for Address Type.
Addresses of all types and usage must have effective start date and may have effective end date.
Accepted Data Values for Address Usage
Following are the accepted data values for Address Usage:
| Accepted Data Value | Definition | Allowed for Address Type | ||
|---|---|---|---|---|
| Home | Business | Work | ||
| Billing | Usage indicator for billing information in case of a financial payment. | Yes | Yes | Yes |
| Shipping | Usage indicator for sending or receiving shipments. | Yes | Yes | Yes |
| Mailing | Usage indicator for sending or receiving mail. | Yes | Yes | Yes |
| Seasonal | Usage indicator for when an address is used only during particular times of year. | Yes | No | Yes |
| Remit To | Usage indicator as an unique destination address to receive payment for a bill or invoice. | No | Yes | No |
| Other - Home | Usage indicator for an additional (secondary) home address | Yes | No | No |
| Other - Work | Usage indicator for an additional (secondary) work address | No | No | Yes |
| Other - Business | Usage indicator for an additional (secondary) business address | No | Yes | No |
| Work From Home | Usage indicator for an address used as home office. | Yes | No | No |
| Permanent | Usage indicator for a permanent home address | Yes | No | No |
| Street Address | Address assigned to a building with a street entrance | Yes | Yes | Yes |
| Tax Purposes | Usage address indicator for an address used on Tax forms | Yes | No | Yes |
| Student Campus Address | Usage indicator for UBC students living on Campus. | Yes | No | No |
| Do not mail | Indicator to never use the address. | Yes | Yes | Yes |
A unique address may have more than one value for Address Usage.
Following are the accepted data values for Primary Address Indicator:
| Accepted Data Value | Data Rule |
|---|---|
| Yes or No |
Only one address attached to a person or organization may have an indicator for default communication address per Address Type. An address with usage value of “Do not mail” must not be designated Primary Address. |
Following are the accepted data values for Public Address Indicator:
| Accepted Data Value | Data Rule |
|---|---|
| Yes or No |
For student contact information, only the student can elect to allow their address to be displayed in a UBC public directory. |
Compliance
This standard about Address Type and Address Usage must be complied with through every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect Address Type and Address Usage 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.
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.