Taxonomies

 ØA taxonomy is used to classify metadata and is useful when you are organizing assets for use with filters, or you need to add security. For example, you could use taxonomies to organize assets by brand name so that when users search for an asset, they can filter the search by brand name.

ØThe difference between option lists and taxonomies is that a taxonomy can have many hierarchical values (for example, a tree structure) and it controls security. Use a taxonomy instead of an option list when: 

lThe selected value controls the security on the entity (option lists cannot control security).

lThe list of possible values is very long (taxonomies are searchable and paged).

lThe item needs more properties than just a name (for example, it also requires a description and an image).

Create or modify a taxonomy

ØThe Taxonomy page provides an overview of the current taxonomy configuration for your environment.

ØOn the menu bar, click Manage .

ØOn the Manage page, click Taxonomy.

ØOn the Taxonomy page, click New taxonomy.

ØGive Taxonomy name

ØClick Create and I am getting validation error message.

ØSo I changed the name to Demo.Taxonomy

ØClick the Allow manual sorting switch to active if you want the ability to sort taxonomies.

ØOn the Taxonomy Management page, click Add , define taxonomy details, and then click Save.

ØStart to create

ØI filled the required info

ØClick save

ØLet me create a new child item for this, click the highlighted name

ØClick save.

ØGo back to the taxonomy page

ØNow we can see the different icon near to color label.But it was dot at initial stage.

Entities

ØAs a superuser, you can manage all entities within your Sitecore Content Hub™ solution from the Entities page. 

ØEntities are grouped according to their entity definition. It is from this page that you manage the domain model and taxonomies. 

WARNING

ØOnly experienced superusers should modify entities as changes may cause unexpected system behavior or system instability.

How to create a new Entity?

ØOn the menu bar, click Manage  

ØOn the Manage page, click Entities.

ØThis is Entity listing page

Entity definitions

ØEntity definitions allow you to create a data schema, also known as a domain model.

ØThe entity definitions contain properties on their own and sub-definitions in property definitions and relation definitions. Property and relation definitions define potential properties (type, names, and so on) and possible relations between two entities (cardinality, name, and so on).

ØEntity definitions store the property and relation definitions (members) in one or more member groups.

Relation diagram

Tree view 

ØFor a visual overview of how entity definitions are related, from the Manage menu, go to the Entities page, click  and switch to Tree view .

ØView of Demo.Arul  is mapped with M.Asset.

ØView of M.Asset type

Entities list

ØClicking on an entity displays the Entity list.

ØIn the following example, the M.Asset entity list is opened and shows all the asset entities.

Schema

 The Schema page lists all the entity definitions defined in Sitecore Content Hub™. 

ØEach entity definition contains member groups and members, and details the content and structure of the data.

ØEntities are content types (for example, an asset, a product or a project). You create them based on an entity definition (for example, an asset has the M.Asset entity definition).

How to create a schema?

ØGo to settings

ØSearch scheme

ØM.Asset is my entity definition(template).click on show entities, you can find the entity content types which created by using M.Asset(item).

Create a new Entity definition

ØClick on new definition button

ØWe can’t create a definition prefix of M

ØWe couldn’t use the special characters.

ØWhen I try to create a definition using M prefix.

ØIt is redirected to this page

ØThe data schema is defined by the properties and relations that are created through member groups. An entity definition consists of one or many member groups.

DAM Terminology

DAM

ØWhen designing a Digital Asset Management (DAM) solution, a key element of success is designing a content architecture that best represents each client’s marketing world and user needs.

ØSitecore Content Hub™ Professional edition / Fixed Content Modelling provides some flexibility in how content can be modeled to reflect varying client contexts and use cases by enabling the creation of custom metadata properties and taxonomies. 

What is a Domain Model?

ØA domain model defines the kinds of things that are part of a system’s domain and how those things get described, structured, and linked. 

ØIn Sitecore Content Hub the domain model is a representation of the types of entities that make up the marketing world of a customer that will be stored in the DAM and how they are related to and inherit information from each other.

Entity

ØAn entity is a real-world thing or concept represented in the DAM. An entity can be a file uploaded

to the DAM (i.e. a digital asset), along with its metadata, or simply a collection of related data.

Ø“Asset” is a type of entity, but other examples of entities include:

● Product

● Brand

● Recipe

● Article

● Store

● Hotel

● User

● etc.

ØAn entity definition defines how an entity is structured via a set of metadata properties.

ØThe definition (or schema) includes both descriptive metadata properties as well as relations between other entities.

ØThe entity definition can also be thought of as a content type definition or an entityspecific metadata schema.

Relation

ØA relation is a link between two entities that allows for displaying the data on detail pages from the parent-child direct relationship.

ØNote that regular relations cannot inherit and cannot cascade data or security via the hierarchical parent-child "family tree" and must be handled via taxonomy relations instead.

ØNon-taxonomic relations are typically used for simple direct parent-child relations between entities and displaying these via direct relations within detail pages.

ØTaxonomy relations should be used for more advanced metadata and security inheritance, to be able to be used for facet searching on search pages and cascading data inheritance via the family tree.

Taxonomy definition

A taxonomy definition is similar to the entity definition in that it defines how an entity is structured via a set of metadata properties but it also allows for it to be searchable as a filter/ facet or in advanced search query options on the different search pages within one or multiple levels within the “family tree” of parent-child relationships.

Taxonomy relation

ØA taxonomy relation is a link between two entities that allows for data inheritance from the parentchild hierarchy.

ØCreating taxonomy relations between entities makes each of the entities more defined and richer without duplicating data.

ØThis is because relations between entities allow for inheritance of data from the parent entity to the child entity by either making them searchable or displaying them inside detail pages. The child entity definition can inherit one or more metadata