A relation is a characteristic that shows how assets are related to one another. The relation type defines which asset types can be related and which connections can exist between the asset types.
When you associate a relation type with an asset type through an assignment, you can add relations of that relation type to the assets of that asset type. This helps you build a rich, interconnected graph of your data assets, making it easier to understand dependencies, impact, and the overall lineage of information across your organization.
Collibra includes a number of out-of-the-box relation types that provide the foundational vocabulary and structure for building a cohesive and understandable network of data assets. They ensure consistency, accelerate implementation, and facilitate the effective use of the platform.
Certain
Choose an option below to explore the documentation for the latest user interface (UI) or the classic UI.
Viewing relation types and their usage
The Relation types table in the Operating Model settings contains both out-of-the-box and custom relation types. You can find the asset types in which a specific relation type is used by selecting the row containing the relation type and then clicking Used In.
Upcoming: Kinds of relation type
Derived relation type (DRT) is an upcoming feature in the latest UI. It is currently in private preview. A derived relation is a kind of relation that shows how one asset is related to another asset that is multiple relations away.
When the DRT feature is activated, Collibra will have two kinds of relation type:
- Explicit relation type: Connects two asset types directly together. This is what is currently referred to as a relation type.
- Derived relation type: Connects multiple asset types together.
Elements in a relation type
A relation type has four elements, which are described in the following table.
| Element | Description |
|---|---|
| Head |
Asset type of the assets that can be the head of the relation. |
| Tail |
Asset type of the assets that can be the tail of the relation. |
| Role |
Description of the relation type originating from the head asset and directed toward the tail asset. A role represents the direction in a relationship between two assets. It describes how the head asset interacts with or is related to the tail asset. For example, in the relation type "Column is part of / contains Table", the role is is part of, which indicates the relationship from the perspective of the head asset (Column) toward the tail asset (Table). |
| Co-role | Description of the relation type originating from the tail asset and directed toward the head asset. A co-role represents the inverse direction in a relationship between two assets. It describes how the tail asset interacts with or is related to the head asset. For example, in the relation type "Column is part of / contains Table", the co-role is contains, which indicates the relationship from the perspective of the tail asset (Table) toward the head asset (Column). |
Note Relations are bidirectional. For example, in the relation type "Column is part of / contains Table", the Column asset is part of the Table asset, and the Table asset contains the Column asset.