Reclassifying Tables in Redshift

To outline the standardized steps followed when a request involving data domains or Redshift object access is received by the Data Engineering (DE) or Data Governance (DG) team. This ensures proper impact analysis, stakeholder communication, and secure implementation of changes.

1. Request Intake
   1. When the Data Engineering (DE) team receives a request, it will be forwarded to the Data Governance (DG) team via the Data Governance group email (DataGovernance@osu.edu) for evaluation.

2. Impact Analysis
   • The DG team will lead an impact analysis with assistance from DE team to assess:
     • How many existing users will lose access to the table
     • How many new users will gain access
   • Results from the impact analysis will be shared with data stewards to inform the access decision.
3. Stakeholder Communication
   • If the impact analysis indicates that existing users will lose access, the DG team will:
     • Coordinate with data stewards
     • Communicate with affected users, if necessary, to ensure awareness and resolution of any concerns
4. Approval and Classification
   • Upon receiving data steward approval and once the appropriate data classification is confirmed, the DG team will submit a ServiceNow request to the DE team (by assigning a ticket or emailing Enterprise-Analytics@osu.edu) to move the Redshift objects into the appropriate data domains.
5. Implementation
   • The DE team will:
     • Move the objects to the approved domains
     • Update the RAE-Arbiter security file to reflect the new domain assignments
   • These updates will automatically apply the appropriate permissions in Redshift.

Key Roles and Responsibilities