Enterprise docs

Metadata catalog

The dataset information in a metadata catalog contains information about the dataset, table, and column data. The pages for these resources are extremely flexible in terms of the information they can contain and how it's organized. As with all metadata catalog pages, the information at the top is useful to the greatest number of people with the information lower on the page geared to the smallest audience. The following screen shots are from a sample catalog page for a table in our demo organization.

In the center at the top of the page is the metadata that is of value to the most people in the organization. The contents of this area are completely configurable based on your needs. In this example are Personal Identification Information (PII), usage requirements and access, and recommendations. The sidebar on the top right contains information about the people involved in managing the data and the dates and times it was changed:

Overview of table page.png

As we progress down the page, the metadata displayed becomes more technical and is of interest to an increasingly small number of people in the organization. The next section in our example shows the metadata for the columns in the table from the data source:

Columns from table page.png

The number of sections on a page is also dependent on the needs of the organization. In the next section, the lineage of the table from the datasource is displayed:

Table lineage.png

The metadata in catalog pages can also show the linkages between different data resources. The next two sections indicate which terms from the business glossary (another feature of the metadata catalog) and which Business Intelligence (BI) dashboards (from the Analysis Hub) are referenced in the table:


Finally the metadata catalog page for the table in our example ends with specific technical details about the data source and data syncing--the most technical metadata with the smallest audience:

Table page Technical details.png

With data.world your organization can define custom metadata fields on resources like datasets, projects, glossary terms, dashboards, and metadata tables. Custom metadata field types include free text fields, drop-down fields, and multi-select hierarchical fields. Once your fields are defined, administrators can edit them from within the data.world platform.

In this example we will look at the Business Term Average Contract Value (ACV)I in our demo organization DEMO Corp. If you have permissions to edit the metadata in your catalog, you will see similar options to edit your Business Term metadata. As with other metadata objects, the edits you can make to business terms are extensive and completely configurable.

To the left of the About this Business term section on the Overview tab is a link to edit the Business Term:


When you select Edit for the business term you see several tabs where you can set values for different information about the business term:


Some basic fields that exist for most implementations are Title, Description, Summary, and Collections. Selecting Collections enables you to add the current business term to as many of your organization's collections as you would like:


By default, all fields defined for your organization are shown on the tab unless they are flagged as secondary fields. If a field is defined as a secondary field in your initial metadata catalog configuration, it will be listed under an + Add new field dropdown:


In addition to the Overview tab, there are several other tabs on the edit screen, all of which have their own configurable files options. In our example, the additional tabs include Consented Puposes:






Subject Matter Experts (SME's):


Sensitive Data Types:


If your organization has more tabs than will comfortably fit on a screen, there is also a dropdown menu with More listings:


In our example the extras include Quality:




and Technical details: