Sitecore Content Hub Domain Terminologies

Sitecore Content Hub (SCH) is a system that overall streamlines the content creation process and enables content authors to author, review and approve content pages in one single location. As I started using this platform and applying real world scenarios, I began to marvel on the extreme importance of accurately designing the data domain model. As you know each piece of content created in SCH is made up of an entity. Entities are created and further enriched by metadata.These form the building blocks of one or more content pages that are implemented in SCH. The second importance is ensuring that these entities align with your customer’s organisational requirements and domain language.

Therefore, it is crucial to understand the entities that make up your client’s business requirements. You perform a systematic approach by first planning, sketching and fleshing out your basic domain models (entities) and the relationships between them. This includes modelling out attributes/member properties of your entities and how one entity relates to another entity by their cardinality rules.

What is SCH?

Commonly termed as Sitecore ContentHub. Most folks in the Sitecore community tend to coin this as SCH for short. In my post, you may see some of these terms.

This blog post is part of a series on which it attempts to address simple use case scenarios around content creation on the context of a Recipes data model. I have then worked on to identify the following suitable identities for my use case:

Recipes, Recipe Type, Cuisine Type, Ingredients, Ingredient Type.

Firstly it explains the concepts of an entity definition, taxonomy definition, entity relation and taxonomy relation.

These terminologies and concepts were important to grasp and especially for the Administrator exam certification.These of course is not exhaustive list but were key drivers to my understanding.

As I progress through my series, I will be using some of these terminologies and putting this into action in constructing the Recipes data model in Content Hub.

Option List

  • Provides a selected list drop down (single or multivalue) that can be editable/readable on your detail page.
  • Cannot be applied with security and metadata inheritance.Therefore it cannot provide faceting on your custom search page.
  • Suitable to store a short list of data entries (less than 10 items) and does not support search and paging.

Taxonomy Definition

  • Represents the definition of metadata to enrich your main entity for the purpose of search and faceting – that is often called metadata inheritance. This means you can apply faceting on the definition of a custom search page.
  • Able to apply security inheritance when configuring rules on your User Group Policies – when you are creating conditions for your rules based permissions.
  • Suitable to store a long list of data entries (typically more than 10 items) that will support search and paging.

Entity Definition

  • Also known as a non-taxonomy definition.
  • Represents the main entity that typically represent the main content page with all of its fields and relational data. You will think of this as the page that your content authors will approve as one piece of content that encapsulates all of the required information needed with its relational data.
  • Cannot be used as facets as part of custom search pages.
  • Cannot be used for security inheritance and therefore not usable in User Group Policies.

Entity Relation

Represents a relationship with a non taxonomy definition – usually represents the association detail on the member property as a Parent to Child.

Taxonomy Relation

Represents a relationship with a taxonomy definition – usually represents the association detail on the member property as a Child to Parent.

Once your entities are identified, the next step is to classify them accordingly to the necessary requirements based on the aforementioned definitions above.

In my use case, the Recipe page shall serve as the main content page which encapsulates all the fields and relational data which will be the suitable authoring page – which can be managed by a target state flow.

Secondly I will like to utilise a search page which shall leverage facets search using these entities – Ingredients, Ingredient Type and Cuisine Type. This will facilitate tagging of recipe assets and enhance the search experience.

Entity Classification

Entity TypeResultant Entity
Entity Definition (Non Taxonomy Definition)Recipes
Taxonomy DefinitionIngredients, Ingredient Type, Cuisine Type
Option ListRecipe Type

In my next blog post, I will demonstrate setting up an example taxonomy definition entity and how you can repeat the same set of steps for the rest of the other entities. It will also go on next to define a non-taxonomy definition and finish off with examples of creating association / relation member properties between the entities – ultimately implementing the entity domain model which will help me later to create a basic search and create page for my Ingredients and Recipes entity.

2 thoughts on “Sitecore Content Hub Domain Terminologies

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.