Taxonomy members
To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through user group policies.
The Sitecore Content Hub data model (that is, the schema) is made up of entity definitions (for example, M.Asset, M.PCM.Product, M.Project.Task, and so on). Each entity definition is made up of members that contain various properties and relations. When you create a taxonomy member, you are adding a new relation between an entity definition and a taxonomy definition.
After you select a data type, you must fill in various other fields related to that type. These fields are divided into several sections.
General information
| Field | Description |
|---|---|
| Name | Name of the member. This is a mandatory field. |
| Role | The role of the relationship between this definition and the related definition. This is a read-only field. |
| Label | User interface label of the member. |
| Help text | Visual hint displayed under the field in edit mode. |
| Associated label | User interface label of the related entity. |
| Associated definition | Name of the definition this entity is based on. This is a mandatory field. |
| Cardinality | The degree of relationship between two entities, expressed in the form Term1ToTerm2, where Term1 is the number of occurrences of the first entity, and Term2 is the number of occurrences of the second entity. Options are:
This is a mandatory field. |
Conditional
A member that has one or more conditions will only be displayed if at least one of those conditions is true. Conditional members appear in details pages, but they do not appear in inline preview, grid, or table views.
Required fields always have a red asterisk. 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 add a condition, on the Conditional tab, select a property from the list and click Add. Then, click Add and select the related property. For example, setting AssetTypeToAsset to Poster means this field will be visible only if the asset type is a poster.
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 validation condition, click Add filter . In the Parent conditional validation section, 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.
Advanced
You can specify advanced settings for taxonomies, including navigation and security settings.
| Field | Description |
|---|---|
| Path relation | Creates a related path on the child side of the relation. This allows for path expansion of hierarchical entities on a related entity. |
| Is path hierarchy relation | Connects path-enabled definitions and hierarchical definitions which creates a path hierarchy. This is usually set on self-relations. |
| Path hierarchy score | Score given to the relation which is marked as IsPathHierarchyRelation. If an entity has multiple parent hierarchy relations, the paths of the entity are sorted according to this score in ascending way. The first path, if not marked otherwise, is used as a sole entity path when only one path is required. |
| Taxonomy relation | Whether the relation is taken into account when faceting. |
| Is taxonomy hierarchy relation | The taxonomy hierarchy for entities of this definition. This is usually set on self-relations and is taken into account when faceting. Due to the nature of self-relations, you can have only one taxonomy hierarchy relation per entity definition. |
| Is rendition relation | Sets the relation as source of rendition. The main rendition of the entity is always determined by this relation. An entity cannot have more than one relation with this option on. |
| Content copied | Whether the full-text content is inherited through the relation (inheritance only goes from parent to child), letting users search for the child entity based on the full-text content of the parent entity. |
| Completion copied | Whether the auto-completion content is inherited through the relation (inheritance only goes from parent to child). As a result, the auto-completion available when searching for the child entity is based on the auto-completion content of the parent entity. |
| Allow navigation | Whether navigation over this relation is allowed using the REST API. This is usually set to false on the parent side of relations, which can contain a large number of children entities. |
| Inherits security | Whether security is inherited or broken at entity level. This is usually used for pages. |
| Secured | Whether the relation is visible to all users or only to those with sufficient access rights. |
| Allow updates | Whether the value of this property can be updated using the REST API. This is usually set to false for technical properties. |
| Nested | Whether this relation is nested. This means that the ID and properties of the related entities are directly included in the requested entity resource. |
| Include permissions | Includes the related entity permissions in the entity resource. |
| Include properties | Includes the related entity selected properties in the entity resource. |
If a taxonomy relation has no values, all users get the Write permission, regardless of their user groups. To prevent this, you must make the relation mandatory in your user group policies.