Filtering and searching based on relations in Data Marketplace

Data Marketplace provides a unique search experience that can be based on relations between assets.

  • Data Marketplace can provide filters to refine your search results based on specific relations.
    Next to filters based on asset type, status, tags, creator and modification and creation date, you can also filter based on specific relations. For example, you can filter the results for a specific data domain.
  • Data Marketplace can find search results if they have a specific relation with the search term. A data set, for example, can show up in the results if the data set contains a column with a name that matches the searched term.

To make filtering and searching based on relations possible, Data Marketplace indexes specific relation paths, chains of relations. These relation paths are based on the Guided Stewardship meta model.

Relations in filters

You can refine the search results with filters that can take relations into account. By following a chain of relations, called a relation path, Data Marketplace can find assets that have a direct or indirect relation to a specific asset. For example, the Source system filter restricts the search results to data sets that are stored in a specific system.

The following table shows the relation paths of the out-of-the-box filters that use relations.
If your Collibra environment does not use one or more of these relation types, the out-of-the-box filters based on relations do not work.

Filter Relation paths
Data Domain Relation path for Data Domain - Data Set:
  1. Data Set contains Column
  2. Column is represented by Data Attribute
  3. Data Attribute is part of Data Entity
  4. Data Entity is classified by Data Domain
Relation path for Data Domain - Table:
  1. Table contains Column
  2. Column is represented by Data Attribute
  3. Data Attribute is part of Data Entity
  4. Data Entity is classified by Data Domain
Data Concept Relation path for Data Concept - Data Set:
  1. Data Set contains Column
  2. Column is represented by Data Attribute
  3. Data Attribute is classified by Data Concept
Relation path for Data Concept - Table:
  1. Table contains Column
  2. Column is represented by Data Attribute
  3. Data Attribute is classified by Data Concept
Business Asset Relation path for Business Asset - Data Set:
  • Data Set is related to Business Asset
Relation path for Business Asset - Report:
  • Data Set is related to Business Asset
Relation path for Business Asset - Table:
  • Table is related to Business Asset
Relation path for Business Asset - Table:
  1. Table contains Column
  2. Column is represented by Business Asset
Source System Relation path for Source System - Data Set:
  • Data Set is implemented into Source System
Relation path for Source System - Table:
  1. Table is part of Schema
  2. Schema belongs to Technology Asset
  3. Technology Asset is grouped by Source System
Data Source Relation path for Data Source - Table:
  • Table is part of Schema
    The data source is an attribute of the Schema asset.
Tip 

If you want to add filters based on the relations in your Collibra environment, ask your Customer Success Manager to contact the Product Management team.

  • For each custom filter, you need to provide the filter name and the relation path.
    • Instead of spaces, use underscores (_) in the name of your custom filters. Data Marketplace replaces the underscores by spaces.
    • Use meaningful names for each relation in the relation path.
    • Don't use more than five relations in a relation path.
  • Custom filters and their relation paths are also used in the Search over relation feature.
  • Custom filters are not automatically reindexed, even if Consistency for Custom facets and Search over Relations is enabled. You have to reindex the relations manually on a regular basis.

Relations in the search

The Search over relations feature is a Data Marketplace-specific beta feature that allows Data Marketplace to find assets based on specific relations. Search results include assets that have a direct match with the search term, but also assets that are related to the search term via specific relation types and based on the name of the asset.

Example 

The "Customer Sales data" data set contains a column with the name "CustomerId'.
If Search over relations is enabled and you search for "CustomerId' then the "Customer Sales data"data set appears in the search results because the column name matches the search term and there is a Data set - Column relation between "CustomerId' and "Customer Sales data".

By default, the Search over relations feature uses the following relation paths.
If your Collibra environment does not use one or more of these relation types, the out-of-the-box Search over relations feature does not work.

Relation paths

Same relation paths as defined for the filters (see above).
Relation path for Data Set - Column:
  • Data Set contains Column

For information on how to enable the Search over relations feature, see Enable Data Marketplace.

Tip 
  • If you want to add specific search over relation paths, ask your Customer Success Manager to contact the Product Management team.
    • Complex relations are not supported as custom relation paths.
  • The Search over relation feature uses all indexed relations, meaning the ones linked to filters and the ones that are not linked to filters.
  • Custom relation paths are not automatically reindexed, even if Consistency for Custom facets and Search over Relations is enabled. You have to reindex the relations manually on a regular basis.