---
title: "Metadata: which are the differences between Business Glossary, Data Catalog and Data Dictionary?"
description: The terms Business Glossary, Data Catalog and Data Dictionary are often used in Data Governance field, but their definitions are not always standardized.
image: https://newsroom.kireygroup.com/hubfs/Blog_data_value_business_glossary_data_dictionary_data_catalog.jpg
---

[kireygroup.com](https://www.kireygroup.com/)

[![](https://newsroom.kireygroup.com/hubfs/item-2020-dicembre/logo-Blog-v2.svg)](https://newsroom.kireygroup.com/en/news)

- [Ita](https://newsroom.kireygroup.com/news/metadati-quali-sono-le-differenze-tra-business-glossary-data-catalog-e-data-dictionary?hsLang=it)
- Eng
- [Esp](https://newsroom.kireygroup.com/es/news/metadatos-cuales-son-las-diferencias-entre-el-glosario-empresarial-el-catalogo-de-datos-y-el-diccionario-de-datos?hsLang=es)

[Kireygroup.com](https://www.kireygroup.com/)

# Get your daily dose of tech!

## We Shape Your Knowledge

# [Welfare: from compliance to competitiveness, digital services and technologies are key to pension funds’ future](https://newsroom.kireygroup.com/en/news/welfare-digital-services-and-technologies-are-key-to-pension-funds-future?hsLang=en)

By Michela Sertorio, Business Line Manager - BU Pension Funds atKirey.

[Read more](https://newsroom.kireygroup.com/en/news/welfare-digital-services-and-technologies-are-key-to-pension-funds-future?hsLang=en)

 9 MIN READ

26 October 2026

### Latest News

- [Welfare: from compliance to competitiveness, digital services and technologies are key to pension funds’ future](https://newsroom.kireygroup.com/en/news/welfare-digital-services-and-technologies-are-key-to-pension-funds-future?hsLang=en)
- [Inference Costs: how to prevent AI agents from driving costs up exponentially](https://newsroom.kireygroup.com/en/news/inference-costs-how-to-prevent-ai-agents-from-driving-costs-up-exponentially?hsLang=en)
- [Kirey Advisory at the ABI Lab workshop on Processes, Operations and Organization](https://newsroom.kireygroup.com/en/news/kirey-advisory-at-the-abi-lab-workshop-on-processes-operations-and-organization?hsLang=en)
- [Kirey Strengthens Its SAP Presence: Mind The Value Achieves Reselling Partner Status](https://newsroom.kireygroup.com/en/news/kirey-strengthens-its-sap-presence-mind-the-value-achieves-reselling-partner-status?hsLang=en)
- [The Dark Side of Multicloud: how to prevent workload placement from generating technical debt](https://newsroom.kireygroup.com/en/news/the-dark-side-of-multicloud-how-to-prevent-workload-placement-from-generating-technical-debt?hsLang=en)
- [Shadow AI: 4 out of 5 employees use tools not governed by the company](https://newsroom.kireygroup.com/en/news/shadow-ai-4-out-of-5-employees-use-tools-not-governed-by-the-company?hsLang=en)

 15 MIN READ

13 April 2021

- Share on:
- <https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fnewsroom.kireygroup.com%2Fen%2Fnews%2Fmetadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>
- <https://www.twitter.com/share?url=https%3A%2F%2Fnewsroom.kireygroup.com%2Fen%2Fnews%2Fmetadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>
- <http://www.linkedin.com/shareArticle?mini=true&url=https://newsroom.kireygroup.com/en/news/metadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>

- [Data Value](https://newsroom.kireygroup.com/en/news/tag/data-value) /

# Metadata: which are the differences between Business Glossary, Data Catalog and Data Dictionary?

#### Kirey

[![](https://newsroom.kireygroup.com/hubfs/it.svg)](https://newsroom.kireygroup.com/news/metadati-quali-sono-le-differenze-tra-business-glossary-data-catalog-e-data-dictionary?hsLang=it)    [![](https://newsroom.kireygroup.com/hubfs/ES.svg)](https://newsroom.kireygroup.com/es/news/metadatos-cuales-son-las-diferencias-entre-el-glosario-empresarial-el-catalogo-de-datos-y-el-diccionario-de-datos?hsLang=es)

 15 MIN READ

13 April 2021

- Share on:
- <https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fnewsroom.kireygroup.com%2Fen%2Fnews%2Fmetadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>
- <https://www.twitter.com/share?url=https%3A%2F%2Fnewsroom.kireygroup.com%2Fen%2Fnews%2Fmetadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>
- <http://www.linkedin.com/shareArticle?mini=true&url=https://newsroom.kireygroup.com/en/news/metadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary>

- [All](https://newsroom.kireygroup.com/news?hsLang=en)
- Categories + 
    - [Corporate](https://newsroom.kireygroup.com/en/news/tag/corporate)
    - [Cybersecurity](https://newsroom.kireygroup.com/en/news/tag/cybersecurity)
    - [Cloud](https://newsroom.kireygroup.com/en/news/tag/cloud)
    - [Data Value](https://newsroom.kireygroup.com/en/news/tag/data-value)
    - [Innovation](https://newsroom.kireygroup.com/en/news/tag/innovation)
    - [Artificial Intelligence](https://newsroom.kireygroup.com/en/news/tag/artificial-intelligence)
    - [Software Development](https://newsroom.kireygroup.com/en/news/tag/software-development)
    - [Corporate Social Responsibility](https://newsroom.kireygroup.com/en/news/tag/corporate-social-responsibility)
    - [Advisory](https://newsroom.kireygroup.com/en/news/tag/advisory)
    - [Welfare & Social Services](https://newsroom.kireygroup.com/en/news/tag/welfare-social-services)
- [Press & PR](https://newsroom.kireygroup.com/en/news/tag/press)

## The terms *Business Glossary*, *Data Catalog* and *Data Dictionary* are often used in Data Governance field, but their definitions are not always standardized.

*By Laura Bacci, Principal Consultant at [Kirey Group](https://www.kireygroup.com/en/)*

The terms *Business Glossary*, *Data Catalog* and *Data Dictionary* are often used in Data Governance field, but their definitions are not always standardized. The lack of clarity and distinct differentiation often causes overlap and conflicts of competencies.

| *Element* | *Content* | *Application Level* | *Responsibility* |
| --- | --- | --- | --- |
| Business Glossary | Business Metadata | Corporate | Business |
| Data Dictionary | Technical Metadata | Corporate/Divisional | Technology |
| Data Catalog | Data Localization | Corporate/Divisional | Technology/Business |

Tab 1 – Three Data Governance elements

As listed in Tab. 1, these tools collect metadata useful to contextualize data, despite having different characteristics: some are business-oriented metadata (*Business Glossary*), others are technical metadata (*Data Catalog* and *Data Dictionary*). Some of the confusion is is easy to understand, considering how Data Governance generally evolves within an organisation. For example, it is fairly typical to start by creating a *Data Catalog* and then to build a governance program from that; or, for a Data Quality program, it is typical to start by defining the *Data Dictionary*.

This type of approach is potentially effective in delivering immediate results, but it should be "adjusted" and corrected to fully capture the additional value that is obtained from common implementation of all three instruments, within a data governance project.

[![Go to the news](https://no-cache.hubspot.com/cta/default/6224655/ff44304a-74c9-4940-91c7-9dbe2916525b.png)](https://cta-redirect.hubspot.com/cta/redirect/6224655/ff44304a-74c9-4940-91c7-9dbe2916525b)

# **What is Business Glossary?**

A *Glossary* should be focused on the business terms used within the organization, it should be easily understandable at all levels and it should define what each term means in terms of business. What is meant by Customer? By Tax Code? By Reserve? By Award? By Current Account?

The Glossary was created to answer these kinds of questions. It is clear that a Glossary is typical of a specific company, even if, in order to facilitate interoperability, it should be constructed to have most of the terms common to companies operating in the same sector.

### Benefits of a Comprehensive Business Glossary

The advantage of having such a *Glossary* is that a common vocabulary of terms can be shared within the organization, with all the positive effects that this has on operational activities, both functional and technical, as well as on the projects that are executed. The range of application for a Glossary should be at all the company levels. The Glossary could be placed at the divisional level when the different company divisions deal with significantly different business. Therefore, they have to adopt a significantly different terminology.

### Responsibility and Ownership

The *Glossary*’s responsibility should not be delegated to the Information Technology, because of its scope and the skills required for its drafting. The *Glossary* is the property of the Company or, better to say, of the functional component of the Company, rather than of its technological component.

### **Data Dictionary**

A *Dictionary* should focus on descriptions and details of the physical structure of data. Every data stream (file or database table) used within the organization should be registered within the *Dictionary*. This should include details of data such as type, permissible length, technical name, transformations (the *lineage*[**\[1\]**](https://newsroom.kireygroup.com/en/news/metadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary#n1) ) and any other relevant technical details. These details are nothing more than the mostly technical metadata we were talking about at the beginning of this article. The details allow data architects and data engineers to understand how to associate and to query the data for the design of information systems and the production of reporting used by the functional component of the company.

### **Data Catalog**

Finally, the *Catalogue* works as a register to identify the data localization.  It should be seen as an asset that is the unique reference source for the location of any data set and for the identification of all possible internal needs, at technical-operational level, at Information Technology level and for Data Science or Business Analytics activities.

Like the glossary, the catalogue is developed at the divisional level rather than at the corporate level if some divisions carry out a business significantly different from the others.

The Catalogue's compilation requires the knowledge of the localization of all the data resources present in the company.  Most of these data are IT managed, so usually the Catalogue's responsibility is entrusted to **Information Technology**. In the Catalogue should also list those data produced and managed by the functional components. Consequently, the compilation should be the result of a joint activity involving both the **technical** and **functional** components of the organization.

### **Some examples**

All three tools described above are necessary to implement Data Governance in the best possible way,  as they are the foundation on which Data Governance is built. How can we think about governing data if we don’t know what they are, where they are and what they mean for my business?

 

| *Element* | *Content* | *Example* |
| --- | --- | --- |
| Business Glossary | Business Metadata | The tax code serves to uniquely identify natural persons and other entities in their dealings with State institutions and governments. |
| Data Dictionary | Technical Metadata | **Storage in string composed of 16 alphanumeric characters** for natural persons and 11 digits for subjects other than natural persons. Features of no nullability and uniqueness. |
| Data Catalog | Data Localization | The **tax code is contextualized to the various processes** in which it is used listing the storage in the various data sources:\<Database1\>\<tabella1\>\<campo1\> \<Database2\>\<tabella3\>\<campo15\> |

Tab 2 – Content examples for the three Data Governance elements

Moreover, the three tools should "talk" to each other: if we have recorded the location of all informative resources in the *Catalog* and we have recorded all the metadata related to the same informative resources in the *Dictionary*, we will have to link the two pieces of information to take full advantage of both. I will also have to link the definitions of the business terms included in the *Glossary*  to the resources recorded in the *Catalog* to completely close the circle and to know exactly which metadata are characteristic of each business term.

### **An effective and efficient approach**

The complete effectiveness and efficiency are achieved by converging all the information within the three tools in a single centralized repository of Data Governance metadata. In this repository, all the metadata related to the entities of Data Quality processes, described below, are added as control rules, outcomes and reports. In this way, the management of metadata becomes the central node for the development of data governance. This, at least, is the theory.

In real practice, the approach is often partial not completely organized or optimized due to factors such as managerial ability or simply due to cost problems. For this reason, it is unrealistic to imagine an approach to Data Governance that provides, a global project that counts the entire company’s information assets starting from scratch.

The best approach is an Agile one (borrowing the term from Project Management[\[2\]](https://newsroom.kireygroup.com/en/news/metadata-which-are-the-differences-between-business-glossary-data-catalog-and-data-dictionary#n2)): local and departmental initiatives are initially developed; at the end, they eventually converge towards a centralized vision. The approach should be incremental, including first those areas of information that are considered as priorities for various reasons (market, impact on multiple business areas, regulatory relevance, etc...), and then gradually add all the others considered relevant for overall governance.

[![New call-to-action](https://no-cache.hubspot.com/cta/default/6224655/b89cd5c0-b115-44e5-982b-1a1ad02cb7d0.png)](https://cta-redirect.hubspot.com/cta/redirect/6224655/b89cd5c0-b115-44e5-982b-1a1ad02cb7d0)

### **Notes**

\[1\] The lineage is the source-target relationship between the data transformations.

\[2\] "Agile" methodologies originated in software development projects and refer to flexible development practices, which include small development teams, iterative and incremental development, adaptive planning, and the direct and continuous involvement of the customer in the development process.

- [Previous post](https://newsroom.kireygroup.com/en/news/sase-the-new-security-challenge?hsLang=en)
- [Read all posts](https://newsroom.kireygroup.com/en/news?hsLang=en)
- [Next post](https://newsroom.kireygroup.com/en/news/kirey-group-announces-collaboration-with-electrifai-to-bring-the-benefits-of-pre-built-ai-and-machine-learning-models-to-italian-companies?hsLang=en)

## Related posts:

#### [Data Virtualization, the pillar of data-driven com...](https://newsroom.kireygroup.com/en/news/data-virtualization-the-pillar-of-data-driven-companies-what-it-is-and-how-it-works?hsLang=en)

Becoming a data-driven company is essential to remain competitive, but the journey is often slowed d...

[Read more](https://newsroom.kireygroup.com/en/news/data-virtualization-the-pillar-of-data-driven-companies-what-it-is-and-how-it-works?hsLang=en)

 10 MIN READ

13 April 2021

#### [DataOps: What It Is and Why It Is Revolutionizing ...](https://newsroom.kireygroup.com/en/news/dataops-what-it-is-and-why-it-is-revolutionizing-enterprise-data-management?hsLang=en)

As organizations strive to become truly data-driven, they are increasingly running into the limitati...

[Read more](https://newsroom.kireygroup.com/en/news/dataops-what-it-is-and-why-it-is-revolutionizing-enterprise-data-management?hsLang=en)

 20 MIN READ

13 April 2021

#### [Data Strategy: a practical guide to aligning data,...](https://newsroom.kireygroup.com/en/news/data-strategy-a-practical-guide-to-aligning-data-business-and-it-architecture?hsLang=en)

Companies have never had so much data available: management systems, applications, sensors, digital ...

[Read more](https://newsroom.kireygroup.com/en/news/data-strategy-a-practical-guide-to-aligning-data-business-and-it-architecture?hsLang=en)

 13 MIN READ

13 April 2021

#### Explore

- [Home](https://www.kireygroup.com/)
- [Competencies](https://www.kireygroup.com/en/competencies)
- [Industries](https://www.kireygroup.com/en/industries)
- [About Us](https://www.kireygroup.com/en/about-us)
- [Tech&Partners](https://www.kireygroup.com/en/tech-partners)
- [Careers](https://www.kireygroup.com/en/careers)
- [Contact](https://www.kireygroup.com/en/contact)
- [Corporate Social Responsibility](https://www.kireygroup.com/en/corporate-social-responsibility)
- [Advisory](https://www.kireyadvisory.com/en)

#### Policy

- [Quality](https://www.kireygroup.com/oven/media/PKG-COMP-AL14-Quality-Policy.pdf)
- [Security](https://www.kireygroup.com/oven/media/PKG-CIS-LG02-Security-Policy.pdf)
- [Gender Equality](https://www.kireygroup.com/oven/media/PKG-COMP-LG03-Politica-per-la-parita-di-Genere-v2.pdf)
- [Service Management](https://www.kireygroup.com/oven/media/PKG-COMP-AL45-Politica-per-la-gestione-dei-servizi.pdf)
- [Environment](https://www.kireygroup.com/oven/media/PKG-COMP-AL44-Politica-Ambientale-Kirey.pdf)
- [Health, Safety & Wellbeing](https://www.kireygroup.com/oven/media/PKG-COMP-LG02-Policy-on-health-safety-and-well-being-in-the-work-environment.pdf)
- [ESG](https://www.kireygroup.com/oven/media/Policy-ESG-ENG-v1.pdf)
- [Info on Data Processing](https://www.kireygroup.com/en/information-on-data-processing)

#### Certifications

- [ISO 9001:2015](https://www.kireygroup.com/oven/media/KIREY-S-R-L-9001.pdf)
- [ISO/IEC 27001:2022](https://www.kireygroup.com/oven/media/KIREY-S-R-L-27001.pdf)
- [PDR 125](https://www.kireygroup.com/oven/media/PDR-125-2022.pdf)  
  <https://www.kireygroup.com/oven/media/PKG-COMP-AL45-Politica-per-la-gestione-dei-servizi.pdf>
- [ISO/IEC 20000-1:2018](https://www.kireygroup.com/oven/media/ISOIEC-20000-12018-ENG.pdf)
- [ISO 14001:2015](https://www.kireygroup.com/oven/media/ISO-14001-2015-ENG.pdf)
- [ISO 45001:2018](https://www.kireygroup.com/oven/media/CERTIFICATO-ISO-45001-KIREY-ENG.pdf)
- [ISO 22301:2019](https://www.kireygroup.com/oven/media/ISO-22301-2019-ENG.pdf)

#### Info

**Kirey Srl**

[info@kireygroup.com](mailto:info@kireygroup.com)  
Viale Francesco Restelli, 5  
20124 Milano

[kirey@pec.it](mailto:kirey@pec.it)  
**PI/CF**: 06729880960  
**REA**: MI 1910802  
**Tel**: +39 02 78625200

Capitale sociale 1.089.620,00 

[![Linkedin](https://newsroom.kireygroup.com/hs-fs/hubfs/Linkedin.png?width=20&name=Linkedin.png)](https://www.linkedin.com/company/kireygroup/)<https://open.spotify.com/show/41V5g7d4zccIrVcmNB3ZWd>   <https://www.instagram.com/kireygroup/?igshid=MzRlODBiNWFlZA%3D%3D>

- [Privacy Policy](https://www.kireygroup.com/oven/media/Kirey-Privacy-ENG-policy-art-13.pdf)
- [Cookie Policy](https://www.kireygroup.com/oven/media/Kirey-Cookie-Policy-ENG-1.pdf)
- [Terms and Conditions](https://www.kireygroup.com/oven/media/Kirey-Website-Terms-and-Conditions-1.pdf)

[![KIREY LOGO](https://newsroom.kireygroup.com/hs-fs/hubfs/KIREY_LOGO_PAYOFF_RGB_POS.png?width=200&height=72&name=KIREY_LOGO_PAYOFF_RGB_POS.png)](https://www.kireygroup.com/)

© Copyright 2026 by Kirey