Skip to content

Latest commit

 

History

History
280 lines (172 loc) · 11.7 KB

module04.md

File metadata and controls

280 lines (172 loc) · 11.7 KB

Module 04 - Glossary

< Previous Module - Home - Next Module >

📢 Introduction

A Glossary, sometimes called Data Glossary or Business Glossary, is a list of business terms with their definitions. A Glossary is an important tool for maintaining and organizing information about your data. It is used for capturing domain knowledge of information that is commonly used, communicated, and shared in organizations as they are conducting business.

There aren’t any rules for the size and representation of glossaries. They can stay abstract or high-level, but also are allowed to be detailed, describing carefully attributes, dependencies, relationships and definitions. A glossary isn't limited to only a single database, in fact it can cover many applications or multiple databases. Multiple applications can work together to accomplish a specific business need. This means that the relation between a glossary and data attributes is a one-to-many relationship. The glossary can also include and capture more concepts than the concepts representing the application or database itself. It can include concepts, which are used to make the context clearer, but don’t play a direct role (yet) in the application or database design. It can also include concepts, that represents future requirements, but didn’t find their way yet into the actual design of the application or database yet.

When implementing your Glossary it is important to think about how you to structure your business terms and definitions. For example, you could use hierarchies and align these with business domains such as: Finance, Marketing, Sales, HR, etc. You could think of naming standards or introduce term templates for capturing additional information about your business metadata. You could also use relationships for linking business terms, such as Acronyms, Related terms and Synonyms. These relationships could help to avoid creating terms with duplicated names and lower the overhead of management.

In this lab you learn how to create terms using a system and custom term template. You'll also learn how to import and export terms. Lastly, you learn about linking terms to data assets, which helps to relate technical metadata to business metadata.

🤔 Prerequisites

🎯 Objectives

  • Create a Term in the Glossary using the System Default Term Template.
  • Create a Term in the Glossary using a Custom Term Template.
  • Bulk Import Terms into the Glossary via a CSV file.
  • Bulk Export Terms from the Glossary into a CSV file.
  • Assign a Term to an Asset in the Data Catalog.
  • Update an existing Term with Related Terms and Contacts.

Table of Contents

  1. Create a Term (System Default Term Template)
  2. Create a Term (Custom Term Template)
  3. Bulk Import Terms
  4. Bulk Export Terms
  5. Assign a Term to an Asset
  6. Update an Existing Term

1. Create a Term (System Default Term Template)

  1. Open Purview Studio and from the Data catalog, click Manage glossary.

  2. Click New term.

    New Glossary Term

  3. Select the System default term template and click Continue.

    💡 Did you know?

    A Term Template determines the attributes for a term. The System default term template has basic fields only (e.g. Name, Definition, Status, etc). Custom term templates on the other hand, can be used to capture additional custom attributes. For more information, check out How to manage term templates for business glossary.

    System default term template

  4. Change the Status of the term to Approved and then copy and paste the values below into the appropriate field, then click Create.

    New Term

    Status

    Approved
    

    Name

    Contoso Parent
    

    Definition

    This will be the parent term.
    

    Acronym

    CP
    

    Resource Name

    Azure Purview
    

    Resource Link

    https://aka.ms/Azure-Purview
    

2. Create a Term (Custom Term Template)

  1. Open Purview Studio and from the Data catalog, click Manage glossary.

  2. Click New term.

    New Term

  3. Click New term template.

    New term template

  4. Provide the Term Template a Name (e.g. Contoso Template) and click New attribute.

    Term template

  5. Populate the attribute fields as per the examples below and click Apply.

    Field Example Value
    Attribute name Business Unit
    Field type Single choice
    Choices Sales, Marketing, Finance, Human Resources, IT,

    Attribute

  6. Click Create.

    Create term template

  7. Select Contoso Template and click Continue.

    Custom Term Template

  8. Change the Status of the term to Approved and then copy and paste the values below into the appropriate field, then click Create.

    Name

    Contoso Child
    

    Definition

    This will be the long description for the child glossary term.
    

    Parent

    Contoso Parent
    

    Business Unit

    Marketing
    
  9. From the Glossary screen, change the view to Hierarchical view to see the hierarchical glossary.

3. Bulk Import Terms

  1. Download a copy of import-terms-sample.csv to your local machine by opening the link in a new tab, right-click within the body of the content, click Save as .

    Import terms

  2. From the Glossary screen, click Import terms.

    Import terms

  3. Select the System default term template and click Continue.

    Term Template

  4. Click Browse and open the local copy of import-terms-sample.csv.

    Browse

  5. Click OK.

    Upload CSV file

  6. Once complete, you should see 50 additional terms beneath the parent (Workplace Analytics). Tip: You can quickly find specific types of terms using the filters at the top (e.g. Status = Approved).

    Filter Terms

4. Bulk Export Terms

  1. From the Glossary screen, we want to select ALL terms (top check box) and then de-select terms that do not belong to Workplace Analytics (i.e. Contoso Parent, Contoso Child). All Workplace Analytics terms should be selected. Click Export terms. Note: You can not export terms from different term templates.

    💡 Did you know?

    When using Purview Studio to Export terms, all terms selected for the export must use the same Term template. Selecting terms from different term templates will result in the Export terms button being greyed out.

    Export Terms

  2. If the export was successful, you should find a CSV file has been copied to your local machine (e.g. Downloads).

    Downloads

5. Assign a Term to an Asset

  1. Perform a wildcard search by typing asterisk (*) into the search bar and hitting the Enter key to submit the query. Click on an asset title (e.g. QueriesByState) to view the details.

    Wildcard Search

  2. Click Edit.

    Edit Asset

  3. Open the Glossary terms drop-down menu and select a glossary term (e.g. Contoso Child). Click Save.

    Assign Term

  4. Click on the hyperlinked term name to view the glossary term details.

    Assigned Terms

  5. Click Refresh to view the Catalog assets the term is assigned to.

    Catalog assets

6. Update an Existing Term

  1. From the Glossary screen, open an existing term (e.g. Aggregation).

    Term Details

  2. Navigate to the Related tab and click Edit.

    Related

  3. Use the drop-down menu to assign two glossary terms as Synonyms.

    💡 Did you know?

    Synonyms are other terms with the same or similar definitions. Where as Related terms are other terms that are related but have different definitions.

    Synonyms

  4. Use the drop-down menu to assign two glossary terms as Related terms.

    Related Terms

  5. Navigate to the Contacts tab and assign an Expert and a Steward. Click Save.

    💡 Did you know?

    Glossary terms can be related to two different types of contacts. Experts are typically business process or subject matter experts. Where as Stewards define the standards for a data object or business term. They drive quality standards, nomenclature, rules.

    Term Contacts

🎓 Knowledge Check

http://aka.ms/purviewlab/q04

  1. Glossary terms with the same name but different descriptions can exist under the same parent term?

    A ) True
    B ) False

  2. Glossary terms can be related to other terms in the glossary. Which of the following is not a valid glossary term relationship type?

    A ) Synonyms
    B ) Antonyms
    C ) Related terms

  3. Glossary terms created using different term templates can be exported together using the Purview Studio (UI) glossary "Export terms" functionality?

    A ) True
    B ) False

🎉 Summary

This module provided an overview of how to create, export, and import terms into the Azure Purview glossary.

Continue >