Data Domains

DG Data Domains

Purpose

Data Domains and Data Sub-Domains create a logical representation of a category or grouping of Organizational Data that is designated, named, and assigned accountability. The Data Governance Committee maintains the official list of Georgia Tech Data Domains and Data Sub-Domains.

 

Go to Procedures
Go to Resources

 

Related Policies

Data Governance and Management Policy

Related Guidelines, Procedures, and Resources

Definitions

Capitalized terms not otherwise defined herein shall have the same meaning as set forth in the Data Governance and Management Policy

Audience

Responsible Data Governance Committee
Accountable Data Owner
Data Trustee
Support Data Governance team
Consulted Technology Governance Committee
Informed Data Domain & Technology Sub-Committees
Associate Data Trustee
Data Steward
Associate Data Steward
System Owner
Technical Manager
Data Administrator
Data User

Procedures

Request a new Data Domain
  1. An individual must submit a request for a new data domain to the Data Governance Committee. The request must include:
    1. Proposed Data Domain name
    2. Scope of the Data Domain, including proposed Data Sub-Domains
    3. Proposed Data Trustee of the Data Domain, and Associate Data Trustees and Data Stewards for the Data Sub-Domains
    4. Identification of any existing overlap this new Data Domain has with existing approved Data Domains or Data Sub-Domains
    5. Reason the addition is requested
  2. The Data Governance Committee will review the request and determine if further discussion is required with the requestor or others involved with the request.
  3. If approved, the Data Governance Committee will notify the requestor and publish the change to the official list of domains on the website. The Data Governance Committee will then follow the procedure for adjusting membership, if applicable, to the Data Governance Committee, Data Management Committee, and Data Domain & Technology Sub-Committees to ensure proper representation. Inventories that rely upon Data Domains (e.g., Systems Inventory) will be updated.
  4. If not approved, the Data Governance Committee will articulate the rejection and send it back to the requestor.
Request a new Data Sub-Domain
  1. An Associate Data Trustee must submit a request for a new Data Sub-Domain to the Data Governance Committee. The request must include:
    1. Proposed Data Sub-Domain name
    2. Scope of Data Sub-Domain
    3. Proposed Data Steward for the Data Sub-Domain
    4. Identification of any existing overlap this new Data Sub-Domain has with existing approved Data Domains or Data Sub-Domains
    5. Reason the addition is requested
  2. The Data Governance Committee will discuss the request with the Associate Data Trustee, who will provide information on the request but will not be a part of the approval process.
  3. If approved, the Data Governance Committee will publish the change to the official list of domains on the website. The Data Governance Committee will then follow the procedure for adjusting membership, if applicable, to the Data Management Committee and Data Domain & Technology Sub-Committees to ensure proper representation. Inventories that rely upon Data Domains (e.g., Systems Inventory) will be updated.
  4. If not approved, the Data Governance Committee will articulate the rejection and send it back to the Associate Data Trustee.
Modification to an existing Data Domain or Data Sub-Domain
  1. An Associate Data Trustee must submit a request for a change to an existing Data Domain or Data Sub-Domain to the Data Governance Committee. The request must include proposed changes to one or more of the following:
    1. Modification to the name of the Data Domain and/or Data Sub-Domain
    2. Modification to the scope of the Data Domain and/or Data Sub-Domain
    3. Modification to the approved Data Trustee for the Data Domain and/or the Associate Data Trustee and Data Steward for the Data Sub-Domain
    4. Identification of any existing overlap this modification might have with existing Data Domains or Data Sub-Domains
    5. Reason the modification is requested
  2. The Data Governance Committee will discuss the request with the Associate Data Trustee, who will provide information on the request but will not be a part of the approval process.
  3. If approved, the Data Governance Committee will publish the change to the official list of domains on the website. The Data Governance Committee will then follow the procedure for adjusting membership, if applicable, to the Data Governance Committee, Data Management Committee, and/or Data Domain & Technology Sub-Committees to ensure proper representation. Inventories that rely upon Data Domains (e.g., Systems Inventory) will be updated.
  4. If not approved, the Data Governance Committee will articulate the rejection and send it back to the Associate Data Trustee.
Deprecation of an existing Data Domain or Data Sub-Domain
  1. An Associate Data Trustee must submit a request to deprecate an existing Data Domain or Data Sub-Domain to the Data Governance Committee. The request must include:
    1. Proposed deprecated Data Domain and/or Data Sub-Domain name
    2. Data Domain and/or Data Sub-Domain that will inherit the existing scope of the deprecated domain
    3. List of impacted Data Trustees, Associate Data Trustees, and/or Data Stewards
    4. Reason the deprecation is requested
  2. The Data Governance Committee will discuss this request with the Associate Data Trustee, who will provide information on the request but will not be a part of the approval process.
  3. If approved, the Data Governance Committee will publish the change to the official list of domains on the website. The Data Governance Committee will then follow procedure for adjusting membership, if applicable, to the Data Governance Committee, Data Management Committee, and/or Data Domain & Technology Sub-Committees to ensure proper representation. Inventories that rely upon Data Domains (e.g., Systems Inventory) will be updated.
  4. If not approved, the Data Governance Committee will articulate the rejection and send it back to the Associate Data Trustee.

Resources

What are Data Domains and Data Sub-Domains?
Domains are a method to identify and group similar types of data and assign accountability. Data Domains provide a logical grouping of Organizational Data at the highest level. Examples of Data Domains may include the Student Data Domain or the Financial Data Domain. Data Sub-Domains continue this logical grouping within a Data Domain for more granularity and further accountability at a lower level. Examples of Data Sub-Domains may include Student-Registration and Financial-Accounts Payable. Further categorizations of domains assist in the management and protection of its data.
What information is required for a Data Domain or a Data Sub-Domain?
Name The name of the Data Domain or Data Sub-Domain
Parent Record For Data Sub-Domains, what is the parent Data Domain
Data Trustee The member of the Executive Leadership Team with delegated authority from the Data Owner (President) over a Data Domain
Associate Data Trustee The appointed executive who has overall responsibility for the data within the Data Domain
Data Steward For Data Sub-Domains, the appointed division or department director who has day to day responsibility for the data within the Data Sub-Domain
Associate Data Steward For Data Sub-Domains, an optionally appointed division or department director or associate director who may assist the Data Steward with data to day responsibilities within the Data Sub-Domain
Data Domains Registry

The Data Domains structure with stewardship roles for Georgia Tech can be found in the Data Domains Registry.  This is a living document that will be periodically updated as new Data Domains and their corresponding roles are identified.

 

 

Revision Date Author Description
2023-02-24 David Mack, Data Governance Link to Data Domain Registry
2021-07-27 Zachary Hayes, Data Governance New