Glossary
Current version: 4.1
This glossary defines the key Sitecore Content Hub terms and concepts.
| Term | Definition |
|---|---|
| Action | Components that perform a specific task. Manually triggered by a user from the UI, automatically run by a trigger or by the API. |
| Administrator | A Sitecore employee responsible for the upkeep, configuration, and reliable operation of Content Hub. Can edit or delete any system-owned entity. Customers cannot be administrators. |
| Agent | Component configured to perform a specific type of task. |
| Asset | Entities in Content Hub such as images, videos, or text files. |
| Block | A basic project, a multi-stage project, or a stage. |
| Campaign | Action plan to promote a product. |
| Collection | A set of assets grouped together. For example, a collection can group related assets based on an event or a product. Collections make it easy to share content with collaborators. |
| Content | Element of a campaign such as a blog post, a recipe, or an advertisement. |
| Domain model | Defines the domain parts of a system and how these parts are structured and linked together. In Content Hub, the domain model is a representation of the entity types stored in Sitecore DAM and how they are related to – and inherit information from – each other. |
| Content collection | A content collection brings together content items that have a common property or purpose. It enables you to create, manage, and share channel-specific content for easy reuse. |
| Data model | A structured representation of the Content Hub underlying database. The data model – also known as a schema – includes entity definitions such as assets, products, or projects. |
| Draft | Temporary instance of an item that lets you make modifications without starting a new creation and approval process. For example, you can create a draft of a published recipe that you want to update. The original recipe stays available but is locked while you edit the draft. When your draft is ready, you send it through an approval workflow for the changes to be approved and merged into the published version, at which point the draft is deleted. |
| DRM | Digital Rights Management. Access-control technologies used to restrict usage of copyrighted works. |
| Entity | A set of data that belongs together (such as for a product, campaign, project, story, recipe, or asset). In general, an entity is anything that you can find and display when searching for content. For example, an entity can be a digital asset (file) that has been uploaded along with its metadata, or it can be a collection of related data. An entity from another system linked to Sitecore DAM is called a proxy entity. You use proxy entities in Content Hub like any other entity. However, they are read-only because master-data ownership for this type of entity belongs to the other system. |
| Entity definition | Set of metadata properties that define how an entity is structured. The definition includes both descriptive metadata properties and relations with other entities. You can also think of the entity definition as a content type definition or an entity-specific metadata schema. |
| Entity property | An editable detail about an entity (such as product number, benefit, campaign brief, or file name). Properties can be, for example, text, numbers, option lists, or dates. They can be multilingual and you can define as many properties as you need on an entity. You can also specify properties to a proxy entity that are not available in the source system. |
| Fragment | Similar to an asset, except that the content is a text snippet rather than a media file. A fragment consists of a rich-text snippet and a title. |
| Job | A background process. |
| Job (MRM) | A space in which teams and departments can work together. |
| Members | The properties and relations you assign to an entity definition. |
| Member groups | A collection of members. |
| Message | Data transported between the sender and the receiver application. For example, a message can be a request to the system to process an asset. |
| Page component | A container that holds the actual content of a page. |
| Policy | A user group policy that consists of rules, conditions, and permissions. Policies are assigned to users, determining what they can see and do throughout Content Hub. |
| Portal asset | An asset created specifically for a portal page. |
| Portal page | A page from which you can access and interact with data such as entities, components, relations, and properties. Users must be given access to a portal page to see its content. |
| Product | Entities in Sitecore Product Content Management (PCM), each representing a single product. |
| Project | Marketing plan in Sitecore Marketing Resource Management (MRM). |
| Public link | Free access link to an asset. |
| Queue | List of messages waiting to be processed in sequential order. |
| Relation | Link between two entities that lets you display data from the parent-child relationship on relevant detail pages. By creating relations between entities, you make each entity more detailed without duplicating data. For example, you might have a product that is available in several colors, a recipe that uses several products, or a campaign that contains a story along with associated files. In each case, there is a relation between the parent and the children entities. |
| Rendition | Version of an asset. For example, an image might have an original and a medium-sized rendition. |
| Schema | See Data model. |
| Search (saved search) | The result of a search in Content Hub, saved as an entity object. |
| Security model | The conditions for securing user access to entity definitions. |
| Selection (saved selection) | A selection of assets saved as an entity object. |
| State flow | The logic applied to the content creation process. This consists of a series of states, transitions, and actions that superusers can enable for any type of content. |
| Superuser | A user with special privileges to configure and maintain a Content Hub solution. Can edit or delete any non-system-owned entity. |
| System-owned | Settings, definitions, properties, or components that are default elements in Content Hub. Superusers cannot edit these default elements. |
| Task | Action performed by a user in a project. |
| Taxonomy relation | The relation between entities that allows for advanced metadata and security inheritance through their family tree. |
| Taxonomy definition | Entity definition that is searchable as a facet in advanced searches. |
| Template | Pre-defined structure and default values to help build the domain model. |
| Transformation | Processing operation that allows superusers to manage the configuration of preset asset renditions and apply them to renditions dynamically. |
| Trigger | Conditions that, when met, automatically execute a set of actions. |
| Variant | Stand-alone copy of an original item that has at least one different property. This variant is considered a sibling or a child of the original item. Variants can be used to adapt an item to different locales, for example. |
| Version | Revision of an original content item that remains associated with the original, essentially an instance of a content item that you can make changes to without affecting the original. The main difference between drafts and versions is that drafts always merge into the original and hence they disappear when you are satisfied with the changes you made, whereas versions are different instances of the same content item. The latest version is considered the master version, but you can revert to an earlier version if necessary. |
| Worker | Specialized application that processes messages from queues. |