Linking data concepts to tables

This example shows you how to create a derived relation type (DRT), "Data Concept is implemented in / implements Table", using the relation type builder. It guides you through defining linear (straight) relation paths, testing the paths, expanding the paths, assigning the derived relation type to an asset type, and viewing the derived relation on an asset page.

Objective

Show all tables that contain the data implementing a data concept on the data concept's asset page.

Overview of phases

This example includes the following phases:

  1. Create a derived relation type with one straight relation path.
  2. Test the derived relation type.
  3. Add a second relation path to the derived relation type and test it.
  4. Assign the derived relation type to an asset type.
  5. View the derived relation on an asset page.

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.
  • The following table lists the out-of-the-box operating model elements used in this example. If these elements were renamed in your environment, use the public IDs to identify them.
Type Name Resource ID Public ID
Asset type Column 00000000-0000-0000-0000-000000031008 Column
Data Attribute 00000000-0000-0000-0000-000000031005 DataAttribute
Data Concept 00000000-0000-0000-0000-000000031113 DataConcept
Data Entity 00000000-0000-0000-0000-000000031004 DataEntity
Relation type Business Dimension classifies / is classified by Asset 00000000-0000-0000-0000-000000007007 BusinessDimensionClassifiesAsset
Column is part of / contains Table 00000000-0000-0000-0000-000000007042 ColumnIsPartOfTable
Data Attribute represents / represented by Column 00000000-0000-0000-0000-000000007094 DataAttributeRepresentsColumn
Data Entity contains / is part of Data Attribute 00000000-0000-0000-0000-000000007047 DataEntityContainsDataAttribute

1 Create a DRT with one straight relation path

The following image shows the relation path used in the first phase of the example, which is based on the Guided Stewardship operating model.

Image of relation path from Data Concept to Table

To connect a data concept to a table, you can define your derived relation type as "Data Concept is implemented in / implements Table", where:

  • Head: Data Concept
  • Role: is implemented in
  • Co-role: implements
  • Tail: Table
  1. On the main toolbar, click Products icon → Cogwheel icon Settings.
    The Settings page opens.
  2. In the Operating model section, click Relation types.
  3. On the Relation types page, click Add derived relation type.
    The derived relation type editor opens.
  4. On the Details tab, enter the following information:
    • Role: is implemented in
    • Co-role: implements
  5. On the Relation type builder tab, in the Head field, select Data Concept.
    This automatically starts the first relation path, and the Select relation field appears.
  6. Define the first relation path from the head to the tail by adding the following relation types in the listed order:
    1. "Business Dimension classifies Asset"
    2. "Data Attribute represents Column"
    3. "Column is part of Table"
    Tip Clicking Add icon next to the Select relation field allows you to add another relation type. Each new Select relation field appears below the preceding one and is slightly indented to indicate that it succeeds the one above. All relation types that belong to the same relation path are shown within a rounded box.
    The Table asset type is automatically suggested as the tail asset type in the Tail field. The Graph tab in the right sidebar shows a graphical representation of your derived relation type definition.

    Image of DRT editor with the Graph tab

  7. Click Save relation type.
    Your derived relation type is created. You will test its relation path in the next phase.

2 Test the DRT

Before testing your derived relation type, ensure that your environment contains data that is compatible with the derived relation type. If your environment already contains assets based on the Guided Stewardship operating model, you can test the relation path using your own data. The example assumes that your environment contains the following test data.

Community Domains Assets Relations
DRT test community

DRT test conceptual model of type Business Dimensions

 DRT test - Email asset of type Data Concept
  • "classifies Asset" → DRT test - Customer email
  • "classifies Asset" → DRT test - Employee email
DRT test data of type Physical Data Dictionary DRT test - Customer Email Column of type Column "is part of Table" → DRT test - Customer Table

DRT test - Customer Table of type Table

 N/A
DRT test - Employee Table of type Table N/A
DRT test logical model of type Logical Data Dictionary DRT test - Customer email of type Data Attribute "represents Column" → DRT test - Customer Email Column
DRT test - Employee email of type Data Attribute "is part of Data Entity" → DRT test - Employee
DRT test - Employee of type Data Entity "represents Table" → DRT test - Employee Table

Image of diagram representing test data

  1. If you closed the derived relation type editor, open it again:
    1. On the main toolbar, click Products icon → Cogwheel icon Settings.
      The Settings page opens.
    2. In the Operating model section, click Relation types.
    3. On the Relation types page, find the derived relation type "Data Concept is implemented in / implements Table".
    4. In the Actions column of the derived relation type, click More icon → Edit.
  2. On the Relation test tab in the right sidebar, in the Test asset field, select DRT test - Email and click Run test.
    DRT test - Customer Table is returned in the results.
    Image of Relation test tab with result
  3. To test the relation path in the opposite direction, select the Start from tail checkbox.
  4. In the Test asset field, select DRT test - Customer Table and click Run test.
    DRT test - Email is returned in the results.
    Image of Relation test tab with result

3 Add a second relation path to the DRT and test it

A closer look at the Guided Stewardship operating model shows that there is another way to connect a data concept to a table with the same meaning—by traversing through a data entity.

Image of relation path from Data Concept to Table

To include this additional relation path, you need to flatten the paths by repeating the relation type between the data concept and the data attribute in the new path ("Business Dimension classifies Asset"). This is because the relation type builder accepts only straight relation paths from the head to the tail. If you want to avoid this repetition and build more complex branching paths, use the JSON editor.

  1. To add a second relation path, on the Relation type builder tab, click Add path.
    This automatically starts the second relation path. The Select relation field appears within a new rounded box below the preceding one, indicating a second relation path from the head to the tail. The two straight relation paths are separated by an OR sign, indicating that the assets will be connected if they follow either of the paths.
    Image of Relation type builder tab
  2.  Define the second relation path from the head to the tail by adding the following relation types in the listed order:
    1. "Business Dimension classifies Asset"
    2. "Data Attribute is part of Data Entity"
      Tip At this point, the Graph tab in the right sidebar rightfully indicates that you have an invalid relation type. This is because the end of your relation path isn't compatible with the defined tail asset type. This will be resolved when you add the next relation type.
    3. "Data Entity represents Table"
    The Table asset type is automatically suggested as the tail asset type in the Tail field.
  3. Click Save relation type.
  4. On the Relation test tab in the right sidebar, clear the Start from tail checkbox.
  5. In the Test asset field, select DRT test - Email and click Run test.
    DRT test - Customer Table and DRT test - Employee Table are returned in the results.
  6. To test the relation path in the opposite direction, select the Start from tail checkbox.
  7. In the Test asset field, select DRT test - Employee Table and click Run test.
    DRT test - Email is returned in the results.

Thus, adding the second relation path to your derived relation type has led to the calculation and selection of more related tables.

4 Assign the DRT to an asset type

Now that your derived relation type is created and tested, you need to add it to an asset type assignment to show the dynamically calculated derived relation on the Data Concept asset pages. This allows users to see which tables implement a specific data concept on the Data Concept asset page. The procedure for assigning a derived relation type to an asset type is identical to assigning an explicit relation type to an asset type. The example assumes that the Data Concept asset type uses a custom layout.

  1. On the main toolbar, click Products icon → Cogwheel icon Settings.
    The Settings page opens.
  2. In the Operating model section, click Asset types.
  3. On the Asset types page, click the name of the Data Concept asset type.
  4. On the Data Concept asset type page, in the left pane, expand the global assignment and click Characteristics.
  5. On the Characteristics page, click Edit layout.
  6. On the Edit layout page, in the left pane, click Add a Characteristic.
  7. In the Add a Characteristic dialog box, find and select your new derived relation type, Data Concept is implemented in Table.
  8. In the is implemented in Table dialog box, select the Add directly to layout checkbox and click Add.
    The derived relation is implemented in Table is added to the layout.
    Tip You can change the position of the derived relation using .
  9. Click Publish and close the asset type page.

The derived relation is now available on the Data Concept asset pages. You can verify this in the next phase.

5 View the derived relation on an asset page

It is now time to verify that the derived relation appears on the Data Concept asset page.

  1. Open the DRT test - Email asset page.
  2. On the Summary tab, verify that the asset page shows the derived relation is implemented in Table with the assets DRT test - Customer Table and DRT test - Employee Table.
    Tip You can identify a derived relation on an asset page by the diagram icon Diagram icon. Clicking Diagram icon shows the relation paths on which the derived relation is based, and clicking an asset name opens the corresponding asset page.