Skip to main content Skip to complementary content

Data classes in the Glossary

Defining a compound data class like PII composed of different subtypes is very important to support auto tagging and auto hiding. In addition, it can be important to build up an ontology in one or more business glossaries with terminology that reflects (and is linked to) the significant PII data classes. In this way, you will be able to use the semantic usage and definition reporting on terminology and data elements already auto tagged as well as those you manually tag, classify or semantically map.

Define PII Terminology

Here we will create the specific terms in the glossary from which we will build an ontology.

Create a new term in the Finance glossary named GDPR and create a General Data Protection Regulation term:

And create a Personally Identifiable Information (PII) term:

Define PII Ontology

Then create an association of More General to More Specific between GDPR and PII :

Then, you may create terms for all the other concepts associated with PII , such as email Address , Address , US Social Security Number , etc.:

Create the associations of More General to More Specific between them. In the Semantic Mapping tab of the object page for GDPR we then have:

Link PII Terminology to Data classes

Go to MANAGE > Data classes again and click on US Social Security Number . Then, assign the US Social Security Number term to this data class.

Now, return to In the Semantic Mapping tab of the object page for GDPR we then have:

Linking all the other terminology to data classes, we have:

And suddenly a diagram is less useful.

Click the List tab on the left to get a list of the semantic usage elements:

And, one may also see Business Names and Definitions now (based upon the terminology):

And anything that is downstream in terms of pass-through lineage.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!