Data Quality

My Rules

App Rules

Duplicates

PII Shield

Data Quality Overview

To get to Data Quality click the menu button > and choose Data Quality.

The main purpose of Data Quality is to provide users with the ability to monitor the quality of data that is received from the SIS and provided to the vendor.

There are 4 tabs in Data Quality:

• My Rules - Displays errors related to the data received from the SIS;
• App Rules - Displays errors related to the data provided to the vendor;
• Duplicates - Contains tools that help to avoid duplication of data and get a complete set of data from different data sources.
• PII Shield - Contains tools that enable a Data Provider admin to set up sensitive data protection within their data.

My Rules

My Rules displays errors related to the data received from the SIS.

If the data is synchronized without errors, there will be a corresponding entry "No data errors" on the My Rules tab.

If during the sync process errors occurred, it will be displayed on the My Rules tab. Users are able to see which entities contain errors. Clicking on the corresponding entity allows you to see the full list of errors that occurred during the sync process via the Details screen.

On the Details screen you can check:

• which data attributes have problems - Attribute;
• what is wrong with the data - Issue;
• the number of errors - Errors;
• whether this data was skipped during synchronization - Skipped;
• the name of the application from which no relevant data was imported - Applications.

App Rules

App Rules displays errors related to the data exported to the vendors.

If the data is synchronized without errors, there will be a corresponding entry "No data errors" on the App Rules tab.

If during the sync process errors occurred, they will be displayed on the App Rules tab. Users are able to see which entities contain errors. Clicking on the corresponding entity allows you to see the full list of errors that occurred during the sync process via the Details screen.

On the Details screen one can check:

• which data attributes have problems - Attribute;
• what is wrong with the data - Issue;
• the number of errors - Errors;
• whether this data was skipped during synchronization - Skipped;
• the name of the application to which no relevant data was exported - Applications.

Duplicates

Duplicates provide users with the ability to detect the duplication of data. Duplicates contain tools that allow users to import and export only unique data. Two buttons are responsible for these functions: Master Fields and Domains of Uniqueness.

Master Fields

Data to a district account can come from multiple data sources. One data source may not have a complete list of required data, or this data might be inaccurate. In order to avoid duplication of data from different data sources, the user can configure which attributes from which data source will be the main ones. This configuration occurs in Master Fields.

Domains of Uniqueness

Domains of Uniqueness define parameters that require being unique. The main goal of Domains of Uniqueness is to avoid duplicates in the data system. One can set DoU for seven entities existing in the system: Student, Contact, Teacher, Course, Class, Calendar, Admin.

Аttributes (Domains) of Uniqueness such as First Name, Last Name, and Email are set by default, but you can also set other attributes that need to be unique: birth date, gender, grade, phone number, etc.

Some attributes are already set up by default:

• First / Last name
• Middle name
• Username
• Email
• Password
• Phone numbers
• City/state/country of birth

The list of attributes to be defined as sensitive data can be edited by activating (deactivating) the respective attribute checkboxes.

Once set, the sensitive attributes list will be available on data sharing requests with the Vendor Apps where the data sensitive attributes will be badged as ‘sensitive’.

A District Admin may choose to apply the data masking (hiding the data attribute) to a Vendor within their data feed by checking the checkboxes on the left for each particular attribute (as of now, only First and Last name data masking is supported):

First and Last name data masking can be activated for all users by checking the checkbox below the attributes list: