Glossary of MSM for Assets terms

  • Source: The original assets or folders. Primary copy from which live copies are derived.

  • Live copy: The copy of the source assets/folders that is in synchronization with its source. Live copies can be a source of further live copies. See how to create LCs.

  • Inheritance: A link/reference between a live copy asset/folder and its source that the system uses to remember where to send the updates. Inheritance exists at a granular level for metadata fields. Inheritance can be removed for selective metadata fields while preserving the live relationship between source and its live copy.

  • Rollout: An action that pushes the modifications made to the source downstream to its live copies. It is possible to update one or more live copies in one go using rollout action. See rollout.

  • Rollout config: Rules that determine which properties are synchronized, how and when. These configurations are applied when creating live copies; can be edited later; and a child can inherit rollout configuration from its parent asset. For MSM for Assets, use only the Standard rollout config. The other rollout configurations are not available for MSM for Assets.

  • Synchronize: Another action, in addition to rollout, that brings parity between source and its live copy by sending the updates from source to live copies. A sync is initiated for a particular live copy and the action pulls the changes from the source. Using this action, is possible to only update one of the live copies. See synchronize action.

  • Suspend: Temporarily remove the live relationship between a live copy and its source asset/folder. You can resume the relationship. See suspend action.

  • Resume: Resume the live relationship so that a live copy again starts receiving the updates from source. See resume action.

  • Reset: Reset action makes the live copy again a replica of the source by overwriting any local changes. It also removes inheritance cancellations and resets inheritance on all metadata fields. To make local modifications in the future, you must again cancel the inheritance of specific fields. See local modifications to LC.

  • Detach: Irrevocably remove the live relationship of a live copy asset/folder. After detach action, the live copies can never receive updates from source and it stops being a live copy anymore. See remove relationship.

Create live copy of an asset

To create live copy from one or more source assets or folders, follow either of the following:

  • Method 1: Select the source assets and click Create > Live Copy from toolbar at the top.
  • Method 2: In Experience Manager user interface, click Create > Live Copy from upper-right corner of the interface.

You can create live copies of an asset or a folder one at a time. You can create live copies that are derived from an asset or a folder that is a live copy itself.

Content Fragments (CFs) are not supported for the use case. When attempting to create their live copies, CFs are copied over as is without any relationship. The copied CFs are a snapshot in time and does not update when original CFs are updated.

To create live copies using the first method, follow these steps:

  1. Select source assets or folders. From the toolbar, click Create > Live Copy.
    Create live copy from Experience Manager interface
  2. Select source asset or folder. Click Next.
  3. Provide title and name. Assets do not have children. When creating live copy of folders, you can choose to include or exclude children.
  4. Select a rollout configuration. Click Create.

To create live copies using the second method, follow these steps:

  1. In Experience Manager interface, from upper-right corner, click Create > Live Copy.
    Create live copy from Experience Manager interface
  2. Select source asset or folder. Click Next.
  3. Select destination folder. Click Next.
  4. Provide title and name. Assets do not have children. When creating live copy of folders, you can choose to include or exclude children.
  5. Select a rollout configuration. Click Create.
NOTE
When a source or a live copy is moved, the relationships are retained. When a live copy is deleted, the relationships are removed.