About derived relations

A derived relation is a kind of relation that shows how one asset is related to another asset that is multiple relations away. While an explicit relation links two assets that are directly related (Column → Table), a derived relation uncovers the indirect link between two assets that are separated by multiple relations.

Image of a diagram showing how a column is related to a database

Unlike an explicit relation, you can't manually create a derived relation. Instead, you create a derived relation type, where you define the relation paths across intermediate assets (Column → Table → Schema → Database) to establish a connection between the head asset and the tail asset (Column → Database). You then deploy the derived relation type by assigning it to the head or tail asset types, or their subtypes. Collibra traverses the relation paths you defined to show you the derived relation between the head and tail assets on the respective asset pages. This helps you visualize the broader context of your data directly on an asset page.

Image of DRT editor

Image of Column asset type layout with DRT added

Image of asset page with the derived relation

Collibra also includes out-of-the-box derived relation types, which are ready to be assigned to asset types.

Problem vs. solution

In a complex knowledge graph, assets are often related indirectly, which can make it hard for you to see the full context of your data from a single asset page. Consider a chain of explicit relations where a table contains a column, and that column is represented by a business term. If you are a Data Steward looking at the Customer Profile table, you can't immediately see its business context. To find which business terms apply to this table, you must manually trace the chain. The process would involve opening the table, clicking through individual columns, and checking the assigned business terms. Such manual work is time-consuming and hides the broader context of your data.

A derived relation type solves this problem by automatically bridging the gaps between assets. When you create a derived relation type that defines a path between the Table and Business Term asset types, Collibra performs the manual tracing for you. With the derived relation type built and deployed, you can open the Customer Profile asset page and immediately see that it is related to the Customer Email Address business term. As a Data Steward, this provides you with the following benefits:

The linking is automated. If a different business term is assigned to a column, the derived relation updates itself. You don't need to manually adjust the link.
A derived relation works in both directions. Anyone opening the Customer Email Address asset page can see that it is related to the Customer Profile table.

Prerequisites

The Derived Relations feature is available only in the latest user interface of Collibra Platform. It isn't available for Collibra Platform for Government or Collibra Platform Self-Hosted.
To use the Derived Relations feature, the Derived relation support setting in Collibra Console must be activated.

Where to find all derived relation types

To find all derived relation types, click → Settings → Relation types.

The Relation types page contains both out-of-the-box and custom derived relation types. Any relation type with the value Derived in the Kind column is a derived relation type. You can find the asset types in which a specific derived relation type is used by selecting the corresponding row and then clicking Used In.

Choosing between explicit and derived relations

When you want to establish a relation between two asset types, follow these guidelines to decide whether to choose an explicit relation or a derived relation.

Use an explicit relation if	Use a derived relation if
There is no relation path linking the two asset types that conveys the desired business meaning. Tip A derived relation is calculated based on other relations, so it can be built only if a path with the desired business meaning already exists. There is a relation path linking the two asset types but it doesn't fully convey the desired business meaning. You need individual control over each asset. That is, you don’t want to have the derived relation established wherever the underlying relation path exists. Tip Adding a derived relation type to an asset type assignment shows the derived relation for all assets within the assignment, which may not be what you intend. If you want to manage relations for each asset individually, choose an explicit relation instead. You encounter performance issues and limitations with a derived relation.	There is a relation path linking the two asset types that conveys the desired business meaning. You want a relation that shows connections for all assets wherever the relation path exists, updates itself if the path changes, and consumes less database space.

Use an explicit relation if

Use a derived relation if

There is no relation path linking the two asset types that conveys the desired business meaning.
Tip A derived relation is calculated based on other relations, so it can be built only if a path with the desired business meaning already exists.
There is a relation path linking the two asset types but it doesn't fully convey the desired business meaning.
You need individual control over each asset. That is, you don’t want to have the derived relation established wherever the underlying relation path exists.
Tip Adding a derived relation type to an asset type assignment shows the derived relation for all assets within the assignment, which may not be what you intend. If you want to manage relations for each asset individually, choose an explicit relation instead.
You encounter performance issues and limitations with a derived relation.

There is a relation path linking the two asset types that conveys the desired business meaning.
You want a relation that shows connections for all assets wherever the relation path exists, updates itself if the path changes, and consumes less database space.

Why derived relations can't be created

You can create a derived relation type, but you can't create a derived relation.

Derived relation type (the logic): A derived relation type defines how to navigate your knowledge graph. It generates queries on explicit relations. It is an operating model element that needs to be created, edited, and maintained to adapt to your evolving needs.
Derived relation (the result): A derived relation is calculated based on other existing relations. It is a read-only artifact of your knowledge graph that is queried live based on the current state of the knowledge graph. It is ultimately resolved by querying explicit relations.

In summary, you define the logic using a derived relation type. Collibra then uses that logic to dynamically show the derived relation based on the current state of your knowledge graph.

Identifying derived relations on asset pages

Both derived and explicit relations are shown on the Summary tab on an asset page, as a relation table, tile, or list. You can identify a derived relation on an asset page by the diagram icon . Clicking shows the relation paths on which the derived relation is based, and clicking an asset name opens the corresponding asset page. Image of asset page with derived and explicit relations