COMAND Dimensions

Dimensions are used to store multiple versions of content for:

Localization - Translations of the same content into multiple languages.
Segmentation - Create personalized versions of content to be presented to different user segments.
A/B Testing - Create different versions of content to be presented to different test groups of users to compare engagement and outcomes.
Formats - Store multiple versions of content for fast retrieval based on the desired format. For example, certain sizes, croppings and image formats of image data. Images can also be processed on the fly, but this is useful for storing manual or pre-processed versions as well.

Dimensions can have a significant impact on performance in certain scenarios, so this should be considered before enabling. Complex queries may require optimization.

The following steps will enable dimensions for a content type:

Make sure dimensions are enabled for the repository. See Dimensions Configuration.
Define a content type that extends the Dimension Content Type. For example, a Language content type that extends Dimension.
Add a new field to the desired content type and set the Field Type to the new content type that extends Dimension, and the Location to one of the Reference options.

A content type can be associated with multiple dimensions by creating multiple fields that each reference a different dimension.

Localization

The most common use of dimensions is content localization. The io_comand_localization package makes it easy to add localization with the following steps.

Import the io_comand_language package.
Update each content type that contains content you would like to localize (or a common content type they extend).
Update any existing queries to request the desired language.
Update any existing publication content types you wish to localize.