Skip to main content

Enterprise Dashboard Checklist

A checklist to ensure Enterprise dashboards meet standards.

  1. Create a ServiceNow ticket for each dashboard.
    1. Select Add or Update an Enterprise Dashboard for Request Type.
  2. The Data Visualization team will review:
    1. Filters are in a consistent location. Filters function consistently.
    2. The name.# of a contact is listed if someone would like to request the data in an alternative format. Additionally, an accessible alternative of the data must be provided and meet university guidelines (Excel document training and web content training). The contact’s information must be for the department developing the dashboard – it should not be data-visualization@osu.edu.
    3. Dashboards contain a link to keyboard navigation or keyboard navigation instructions.
    4. Passwords for data sources are embedded.
    5. Metadata such as dashboard description is complete. A template for descriptions is available as well as a short video on how to add descriptions and field definitions.
    6. If the contents are in the data catalog, an up-to-date icon and link to the data catalog. Otherwise, there should not be an icon or a link to the data catalog.
    7. All unused fields in the dashboard’s data source are hidden.
    8. Clear dashboard instructions and purpose are available.
    9. While not mandatory, below are recommendations:
      1. Clearly label axises and provide descriptions.
      2. Ensure viz alt text makes sense. This is editable with Tableau Desktop 2023.3.1
  3. After approval, a member of the Data Visualization team will publish the dashboard to the Enterprise space and set the refresh schedule. 

 

Structure, Organization, and Roles in the Enterprise data process

Data Governance & Data Stewards

Data in the Enterprise structure is organized in data domains, logical groups of related data to clearly define boundaries, inter-dependencies, and stewardship areas of responsibility. Each domain consists of a Primary Domain subdivided into Secondary Domains. 

Data stewards are individuals assigned to one of three formal roles: Operational Data Steward, Secondary Domain Steward or Primary Domain Steward. Data stewards are the primary point of contact for their respective data and how it should be used. Information on the structure and roles is on theData Governance’s website. A listing of stewards and access approvers can be found in the Data Steward Directory. 

The RAE Object Domain Directory lists all primary and secondary domains (Tableau Server access required). 

Data Governance will work with Subject Matter Experts to ensure metadata is complete and accurate. 

Questions about Data Governance, Data Stewards, or access should be directed to DataGovernance@osu.edu.

Subject Matter Experts

The subject matter experts (SME) are responsible for creating Enterprise reports, datasets, and validating the quality of the data. SMEs are often analysts in the business unit. SMEs are responsible for submitting change control requests.

Access Management

The Access Management team works with the Data Stewards to direct access requests for Enterprise data. 

Information on how to request access to Enterprise data is available.

Data Integrations Team

The Data Integrations team works with technical owners of the data, such as Database Administrators (DBA) to establish connection(s) and move data. Data is available in the Reporting & Analytics Environment (RAE). The Data Integrations team partners with SMEs to create medallion architecture that can be used for reporting purposes. Examples of partnering with SMEs include moving data, creating views, or adding/removing columns. 

Questions about the RAE should be directed to Enterprise-Analytics@osu.edu. 

Data Visualization Team

The Data Visualization team is responsible for migrating content to the correct location in the Enterprise structure. They will also review content around accessibility, performance, and setting up refresh schedules.