Custom properties, relationships, and asset types (IBM Knowledge Catalog)

You can extend the default set of properties, relationships, and asset types available for governance artifacts and catalog assets by creating custom properties, relationships, and asset types.

Use custom properties, relationships, and asset types when important details about your data can't be captured by using default properties, relationships, and asset types. Custom properties, relationships, and asset types are created by administrators. For users who work with governance artifacts or catalog assets, custom properties, relationships, and assets appear and behave the same as predefined properties, relationships, and assets.

All asset types in catalogs support custom properties and relationships. The following governance artifacts support custom properties and relationships:

Required permissions

You must have the following user permissions:

Manage glossary

To view definitions for artifacts and assets, including custom properties, relationships and asset types, select Administration > Configuration and settings from the navigation menu, and then select Asset and artifact definition.

Use the filter icon on the following tabs to filter for items:

Artifacts: Filter governance artifacts by custom relationships and custom properties that are assigned to them.
Assets: Filter catalog assets by origin (predefined, custom) and custom properties assigned to them.
Custom properties: Filter custom properties by property types (date, number, predefined values, text) and scope.

How users apply custom properties, relationships, and asset types

After you create custom properties, relationships, and asset types, users can apply them in the same ways as predefined properties, relationships, and asset types. Users who have the required permissions can perform these tasks:

Add values for custom properties or add custom relationships to governance artifacts. Subject to artifact workflows. Requires the Editor, Admin, or Owner role in the artifact’s primary category.
Assign custom relationships, add values for custom properties, or add custom asset types in a catalog. Requires the Editor or Admin role in the catalog.
Assign custom relationships between artifacts and assets in a catalog. Subject to artifact workflows. Requires the Editor, Admin, or Owner role in the artifact’s primary category and the Editor or Admin role in the catalog.

Learn more

Parent topic: Managing governance artifacts