Relationship types

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2025

Relationship types capture a specific type of relationship between two specific types of asset (the subject and an object) using a predicate. A predicate is a term which explains the nature of the relationship. Relationships are bidirectional, so the inverse of a relationship must also be defined. Look at the examples below.

Table 1. Examples of common relationship types
Subject Predicate Object
Application stores Business Term
Business Term synonym of Business Term
Policy governs Business Term
Table 2. Examples of inverse relationship
Subject Predicate Object
Business Term is stored by Application
Business Term synonym of Business Term
Business Term is governed by Policy

Manage relationships between asset types

You can also manage relationships between asset types within the same asset class, allowing flexibility in moving child assets between different parent assets.

  1. Define your parent asset types, such as Parent 1 and Parent 2, as well as your child asset types, like Child 1 and Child 2.
  2. Use the Hierarchy predicate functional type to create relationship types. Set the Predicate to "is parent of" and the Inverse to "is child of".
  3. Create relationships between the parent and child asset types. For example:
    • Parent 1 - Child 1
    • Parent 1 - Child 2
    • Parent 2 - Child 1
    • Parent 2 - Child 2
  4. For each asset type, create an asset item. Establish relationships between these items. For instance, the Parent 1 Asset Item should "be a parent of" the Child 1 Asset Item.
  5. If you need to move a child asset item to a different parent, first delete the existing parent relationship. For example, remove the relationship between Parent 1 Asset Item and Child 1 Asset Item. Then, create a new relationship with the desired parent, such as Parent 2 Asset Item "being a parent of" Child 1 Asset Item.
Note: Each child asset item can only have one parent at any time. Moving child asset items between parents retains the child’s change history and other non-bulk loadable data.