Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Person, Organization |
| Intended Audience | Internal UBC |
Purpose
This standard aims to achieve consistency around the data collected for Telephone Number Type and Contact Preference, and the format in which it is collected and stored in across the University.
This standard applies to all UBC applications collecting Telephone Number Type and Contact Preference. Exceptions are listed in the Dispensation section.
Standard
A telephone number attached to a person or organization may be categorized based on the following attributes:
| Attribute | Requirement | Definition |
|---|---|---|
| Telephone Number Type | Required | Classification of telephone number based on its purpose. |
| Device Type | Optional | Type of device used for telephonic communication. |
| Primary Telephone Number | Optional | Indicator of default telephone number for communication. |
| Contact Preference | Optional | Preference for usage of a telephone number. |
Telephone Number Type Standard
Accepted Data Values for Telephone Number Type
Following are the accepted data values for Telephone Number Type:
| Accepted Data Value | Definition |
|---|---|
| Personal | Telephone number for personal purpose. |
| Business | Telephone number used by a person or organization for commercial purpose. |
Data Rules for Telephone Number Type
| Accepted Data Value | Data Rule |
|---|---|
| Personal | Only a person may have this type of telephone number. |
| Business | A person or organization may have this type of telephone number. |
A person or organization may have multiple telephone numbers of each Telephone Number Type.
A unique telephone number may have more than one value for Telephone Number Type.
Device Type Standard
Accepted Data Values for Device Type
Following are the accepted data values for Device Type:
| Accepted Data Value | Data Rule |
|---|---|
| Fixed | Telephone device connected by cable and may not be able to receive text messages. |
| Mobile | Telephone device that is portable, without a physical connection to a communication network. Mobile devices can send and receive text messages. |
| Voice over Internet Protocol | Device that enables transmission of voice content over Internet Protocol networks. Also known as VoIP or IP telephony. |
| Fax | Device that enables telephonic transmission of scanned-in printed material. |
| Pager | Device used for one way communication with request or notification to contact the sender. |
| TTY/TDD | Stands for Text Telephone / Telecommunication Device for Deaf; special telephone device used for hard of hearing, hearing impaired or speech impaired. |
A person or organization may have multiple telephone numbers for each Device Type.
Primary Telephone Number attribute
Following are the accepted data values for Primary Telephone Number attribute:
| Accepted Data Value | Data Rule |
|---|---|
| Yes | Only one telephone number attached to a person or organization may have an indicator for default communication per Telephone Number Type regardless of Device Type and Contact Preference. A phone number with Contact Preference value of “Do not call” must not be designated Primary Telephone Number. |
Contact Preference Standard
Accepted Data Values for Contact Preference
Following are the accepted data values for Contact Preference.
| Accepted Data Value* | Data Rule |
|---|---|
| Day | Indicator for usage of a telephone number during day hours, usually 9 AM to 5 PM local time |
| Evening | Indicator for usage of a telephone number during evening hours, usually 5 PM to 9 PM local time. |
| Weekend | Indicator for usage of a telephone number only on weekend, usually Saturday and Sunday of every week. |
| Seasonal | Indicator for usage of a telephone number only during particular times of year. |
| Do not call | Indicator to never use the phone number. |
*Application implementing the above Contact Preference values will need to configure times based on the time zone to which telephone number belongs.
Data Rules for Contact Preference
| Accepted Data Value* | Data Rule |
|---|---|
| Day | The effective time set for “Day” usage of a telephone number must not overlap with the effective time set for “Evening” usage within the same time zone. |
| Evening | The effective time set for “Evening” usage of a telephone number must not overlap with the effective time set for “Day” usage within the same time zone. |
| Seasonal | The effective dates must not overlap when there are multiple seasonal phone numbers per person or organization. |
| Do not call | A telephone number with Contact Preference value of “Do not call” must not have any other corresponding value for Contact Preference. |
A person or organization may have multiple telephone numbers for each Contact Preference.
A unique telephone number may have more than one value for Contact Preference.
Compliance
This standard about Telephone Number Type and Contact Preference must be complied with through every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect Telephone Number Type and Contact Preference 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)
- Human Resource Management System (HRMS)
- Finance Management System (FMS)
As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.