Skip to main content Skip to complementary content

Importing and implementing a glossary

Create a glossary model in the configuration and import glossary objects and relationships from CSV files.

Before you begin

You have been assigned an object role with the Metadata Management capability.

About this task

When importing the glossary, you use two CSV files:
  • gdpr_glossary.csv to define the glossary objects terms and abbreviations.
  • gdpr_glossary_relationships to define the relationships between the glossary objects.


  1. Go to Manage > Configuration.
  2. Click Add > Glossary.
  3. Enter a name such as ACME Glossary and a description, then click OK to save the model.
    The Overview tab of the model opens in the configuration manager.
  4. In the upper right corner, click the Open button to access the object page.
  5. In the More actions menu (three dots), click Import from CSV.
  6. Click to browse and navigate to tdc_gsg_sources_files\use-case-2-using_and_contributing\glossary\gdpr_glossary.csv.
  7. Click Import.
  8. Click the spinning gear icon on the top right of the banner to monitor the operation and open the log if necessary.
  9. Follow the same process as above to import the second file tdc_gsg_sources_files\use-case-2-using_and_contributing\glossary\gdpr_glossary_relationships.csv.
  10. Open the object page of the GDPR term.
  11. Click the Contains tab to check that the objects have been imported. Click Filters and the Grid display mode.
  12. Click the US Address term to open its details page.
  13. Open the Specializes and Member tabs to check that the relationships have been imported.

    Specializes contains terms which have a more general context or are more abstract.

    Member contains terms which are considered to contribute to the complete concept, such as Name Contains First Name.


You are ready to trace dependencies between business and technical assets by linking the glossary terms to the table columns.

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!