Data Class Proposal and Approval Process

Data classification auto-tagging proposal:

• For data-detected data classes, when the confidence level is higher than the MATCHING THRESHOLD specified for that data class the application proposes to classify the harvested object with the data-detected data class (e.g. Country Code (98%)). You can accept or reject the proposal.
• For metadata-detected data classes, when the associated Metadata Query Language (MQL) query produces the harvested object as a match the application proposes to classify the harvested object with the metadata-detected data class (e.g. Maiden Name). You can accept or reject the proposal.
• For compound data classes, when either of the two above conditions applies to any of the contained data classes the application proposes to classify the harvested object with the compound data class (e.g. PII). You can accept or reject the proposal.

When you accept the proposal the application creates the “classifies” relationship between the data class and harvested object. The application creates the same relationship when you assign a data class to a harvested object manually.

When you reject the proposal the application remembers it and does not propose the match from then on. If you rejected the match by mistake you can instruct the application to forget about the rejection by classifying the column with the term manually.