Defining relationships between object types - Cloud

Talend Cloud Data Catalog Administration Guide

Version
Cloud
Language
English (United States)
Product
Talend Cloud
Module
Talend Data Catalog
Content
Administration and Monitoring
Data Governance

After associating attribute types with object types, define custom association or composition relationships between the objects.

When a relationship has been used in an instance, you cannot change its cardinalities.

Naming standards for composition role names

A composition role name should be a noun depicting the name of the child object.

The name should be plural when the cardinality is set to Many and singular when set to One, such as "Parent" has "Child" or "Children".

For example: Order has Customer Address.

Naming standards for association role names

An association role name must be unique for the END1 and END2 objects. It also should be a singular noun optionally preceded with an adjective and short as possible.
  • A role name of a uni-directional relationship is a noun. It is plural when the cardinality is many.
  • A bi-directional relationship has one role name as noun and another one as a verb.

When there are multiple relationships to an object, each role name should depict the name of the END2 object.

For example: A Term has Synonym Terms, A Term has Acronym, A Policy Is Enforced by Rules, A Term Defines Imported Objects or An Imported Object is Defined By Terms.

Association role names:
  • become section headers and tab names in the details page for a custom model.
  • become Object Type in worksheets.