Managing derived relation types
This topic guides you through the derived relation type editor in the Operating Model settings to create, edit, and delete derived relation types (DRTs).
For comprehensive information about how to create a derived relation type, with practical examples and instructions for using the Relation type builder tab and the JSON tab, go to Building derived relation types.
Common prerequisites
- Your environment uses the latest user interface.
- You have a global role with the Product Rights > System administration global permission.
- The Derived relation support setting in Collibra Console is activated. If activated, the Add derived relation type button is shown on the Relation types page in the Operating Model settings.
Create a DRT
You can create a derived relation type if the out-of-the-box derived relation types don't meet your needs.
-
On the main toolbar, click
→
Settings.
The Settings page opens. - In the Operating model section, click Relation types.
- On the Relation types page, click Add derived relation type.
- In the derived relation type editor, on the Details tab, enter the following information.
Field Description Role The description of the relation type's meaning when originated 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 The description of the relation type's meaning when originated 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). - On the Relation type builder tab, in the Head field, select the asset type of the assets that can be the head of the derived relation type.
- In the Select relation field, define the relation path from head to tail by selecting the required relation type to the path.
The tail asset type is automatically suggested in the Tail field. - To change the suggested tail, in the Tail field, select the asset type of the assets that can be the tail of the derived relation type.
- Click Save relation type.
The derived relation type is created. You can now assign it to an asset type.
Edit a DRT
You can edit a custom derived relation type. For information about what you can edit in an out-of-the-box derived relation type, go to Customizing an OOTB DRT.
-
On the main toolbar, click
→
Settings.
The Settings page opens. - In the Operating model section, click Relation types.
- On the Relation types page, in the Actions column of the derived relation type, click
→ Edit.
Tip You can use the Kind column to filter the table by the relation kind Derived. - In the derived relation type editor, edit the derived relation type.Note Changing the public ID of a derived relation type can affect any existing integrations.
- Click Save relation type.
Your changes are saved.
Delete a DRT
You can delete a custom derived relation type only if it isn't used in another derived relation type. Out-of-the-box and system-managed derived relation types can't be deleted.
-
On the main toolbar, click
→
Settings.
The Settings page opens. - In the Operating model section, click Relation types.
- On the Relation types page, in the Actions column of the derived relation type, click
.
Tip You can use the Kind column to filter the table by the relation kind Derived. - In the Delete this derived relation type dialog box, click Delete.
The derived relation type is deleted.