Create a member
To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through user group policies.
You can add as many members to an entity definition as you want.
To create a member:
-
On the menu bar, click Manage
. -
On the Manage page, click Schema.
-
On the Schema page, click the entity definition you want to edit.
-
In the desired member group, click New member.
-
In the New member dialog, next to the member type you want to add, click Select, and then fill in the fields available for property, relation, or taxonomy members.
-
Click Save.
Property member fields
Before filling in the property member fields, you must select one of the following data types from the list, and then click Next:
|
Data type |
Description |
|---|---|
|
String |
Alphanumeric value. For example, a set of letters and symbols. |
|
Boolean |
Data type allowing a value of true or false. |
|
Integer |
Number with no fractional part. |
|
Long |
Number with a larger range than an integer. |
|
Decimal |
Number including one or more decimal places. |
|
Datetime |
Time stamp including both date and time. |
|
Datetime offset |
Datetime value combined with an offset indicating the difference between the datetime and coordinated universal time (UTC). |
|
Option list |
Array of string values for users to choose from. |
|
JSON |
Object defined by JavaScript Object Notation. |
After you select a data type, you must fill in various other fields related to that type. These fields are divided into several sections.
Relation member fields
A relation member contains the following fields:
Conditional
To add a condition, select a property from the list and click Add. Then, click 
. For example, setting AssetTypeToAsset to Poster means this field will be visible only if the asset type is a poster.
Adding conditions means the member is only displayed when those conditions are met. When two conditions are added, an OR operator is used, meaning that the member is displayed if condition A or condition B is met. The AND operator is not supported. Conditional members appear in details pages, but they do not appear in inline preview, grid, or table views.
Conditional mandatory fields show as required only when the condition is met, making it clear which fields are actually required. Required fields always have a red asterisk, while conditional required fields have a red asterisk only if the condition is met. If a triggering field changes, the asterisk is recalculated immediately to reflect the new required status. If a triggering field makes another field required and that field is in a different member group without a value, the member group will automatically enter edit mode, allowing you to fill in the required field and save the entity.
To find empty required fields, use the Validation component.
Required
You can specify that either the parent or the child is required for the relation. If you do this, you can also add validation conditions that determine whether the requirement is enforced:
-
If you add conditional validation, the parent or child becomes mandatory when all the conditions are met.
-
If you don't add conditional validation, the parent or child becomes fully mandatory.
To add a condition, click . Select either Property or Relation for Filter type, select a field name (for example, AssetTypeToAsset), an operator (any, all, or none) and then click Add. For example, setting AssetTypeToAsset to Product Asset means this field will be mandatory if the asset type is a product asset.
Taxonomy member fields
A taxonomy member contains the following fields.
Conditional
To add a condition, select a property from the list and click Add. Then, click . For example, setting AssetTypeToAsset to Poster means this field will be visible only if the asset type is a poster.
Adding conditions means the member is only displayed when those conditions are met. When two conditions are added, an OR operator is used, meaning that the member is displayed if condition A or condition B is met. The AND operator is not supported. Conditional members appear in details pages, but they do not appear in inline preview, grid, or table views.
Conditional mandatory fields show as required only when the condition is met, making it clear which fields are actually required. Required fields always have a red asterisk, while conditional required fields have a red asterisk only if the condition is met. If a triggering field changes, the asterisk is recalculated immediately to reflect the new required status. If a triggering field makes another field required and that field is in a different member group without a value, the member group will automatically enter edit mode, allowing you to fill in the required field and save the entity.
To find empty required fields, use the Validation component.
Required
You can specify that the parent is required for the relation. If you do this, you can also add validation conditions that determine whether the requirement is enforced:
-
If you add conditional validation, the parent becomes mandatory when all the conditions are met.
-
If you don't add conditional validation, the parent becomes fully mandatory.
To add a condition, click . On the Required tab, select either Property or Relation for Filter type, select a field name (for example, AssetTypeToAsset), an operator (any, all, or none), and then click Add. For example, setting AssetTypeToAsset to Product Asset means this field will be mandatory if the asset type is a product asset.