Skip to content

Glossary

Data catalog

Quick answer

An inventory of a company's data assets with descriptions, owners and metadata so people can find and understand them.

Catalogs record where data lives, what fields mean and who may use it.

An existing catalog speeds up the inventory step of a licensing review.

Why Data catalog matters when licensing company data to AI

Data catalog is an inventory of a company's data assets with descriptions, owners and metadata, so people can find and understand them. It records where data lives, what fields mean and who may use it. In a licensing review, an existing catalog speeds up the inventory step by showing which systems and fields are candidates for release.

  1. 01Your work records
  2. 02Personal details removed
  3. 03You approve the release
  4. 04Licensed to AI developers
How it works with SourceX: Your work records → Personal details removed → You approve the release → Licensed to AI developers.Illustrative

Related terms

What does a data catalog hold, and what does it leave out?#

A data catalog holds metadata about data, not the data itself. In AWS Glue, for example, the Data Catalog is a persistent metadata store, and its tables contain metadata such as column names and data types rather than records from the underlying data store.

Catalogs are usually filled two ways: automated scanning and manual entry. AWS Glue crawlers infer a data store's schema and create or update catalog tables, and scheduled runs pick up schema changes. Tables can also be created by hand, and people add what a scanner cannot know, such as business meaning and ownership.

The table below shows the kinds of metadata a catalog typically records and what each one answers when a company reviews data for an outside use such as licensing.

What does a data catalog hold, and what does it leave out?
Metadata typeWhat it recordsExampleQuestion it answers in a review
TechnicalTables, columns, data types, partitionsA tickets table with created_at as a timestampWhat fields exist and in what format?
LocationWhere each dataset is storedA bucket path or database nameWhich system would an extract come from?
BusinessPlain-language definitions of fields and termsWhat counts as a resolved ticketWill an outside reader understand the fields?
OwnershipOwner or steward for each datasetSupport operations leadWho can answer questions and approve use?
AccessWho may use the data and how access is requestedAn access request routed to approversWho has to sign off before anything is shared?
LineageWhere data came from and how it was transformedA report table built from raw CRM exportsIs this the original record or a derived copy?

Data catalog vs data marketplace: what is the difference?#

A data catalog is an internal discovery tool; a data marketplace is an external exchange where providers list data products and other organizations find, subscribe to or buy them. One helps your own staff find and understand data, the other moves data or access across company boundaries.

AWS Data Exchange is described as a service that helps customers find, subscribe to and use third-party data in the cloud. Snowflake Marketplace documentation describes free, limited trial and paid listings that providers publish for consumers. A catalog such as Microsoft Purview Unified Catalog, by contrast, lets users request access to data products, and the approval requests go to the involved parties inside the organization.

Data catalog vs data marketplace: what is the difference?
QuestionData catalogData marketplace
Who uses it?Employees inside one organizationProviders and buyers in different organizations
What does it list?Metadata about the company's own data assetsData products offered by providers
What changes hands?Internal access, granted by approversA subscription, license or paid access under listing terms
ExamplesAWS Glue Data Catalog, Microsoft Purview Unified CatalogAWS Data Exchange, Snowflake Marketplace
What it settlesWhere data is and what it meansHow a listed product is found and accessed

Which does a supplier need first, a catalog or a marketplace?#

A supplier needs to know what it holds before it can sell any of it, so an inventory comes first and a sales channel second. A marketplace listing assumes the provider has already decided what to offer, documented it and confirmed it has the right to license it.

Neither tool settles rights. A catalog does not show whether customer contracts, privacy notices or vendor terms allow the data to be licensed. That is a separate review, and counsel looks at the specific facts.

A formal catalog is not a prerequisite for licensing. With SourceX, the first step is a short company assessment, and no data uploads are needed to see if a company qualifies. SourceX then runs rights review, contracting, data preparation, delivery and payment, and the company approves exactly what is released, once per deal.

  • No catalog yet: start with a simple inventory of systems, record types and date ranges.
  • A catalog exists: export its owner, location and definition fields for the datasets in scope.
  • Considering a marketplace listing: confirm licensing rights and de-identification needs before publishing anything.
  • Unsure what is valuable: buyers generally look for years of consistent history, typically 2+ years, in one system.

Sources for this section

  • The AWS Glue Data Catalog is a persistent metadata store whose tables hold metadata, not data, and crawlers populate and update it. Source
  • AWS Data Exchange helps customers find, subscribe to and use third-party data in the cloud. Source
  • Snowflake Marketplace documents free, limited trial and paid listings that providers publish for consumers. Source
  • Microsoft Purview Unified Catalog lets users request access to data products, with approval requests sent to the involved parties. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies