Documentation Center

BluePrint mapping

Renaming or moving items can affect the BluePrint hierarchy so you will need to use mappings to handle items whose BluePrint status changed after transfer.

For example, imagine the following scenario:

  1. You transfer shared content from a child Publication in the source Content Manager to a corresponding child Publication in the destination Content Manager.
  2. After the transfer, a user changes the name of a content item in the source instance, localizes the item and translates it.
  3. You now perform another transfer from the source instance to the destination instance, without providing explicit mapping for the content item that was modified.

In the above example, the following happens:

  • The fact that the item on the source instance is localized from a parent item is detected.
  • The corresponding parent content item is checked on the destination to see if that item is shared or localized to the corresponding child Publication.
  • In this example, it is found that on the destination, the child item is shared and not localized.
  • The child item is localized on the destination and a mapping is created from the source instance to it.

The result is that the child item on the source instance is correctly mapped to the corresponding child item on the destination instance.

To enable this behavior, the user executing the import must switch on the shared item resolution with BluePrint mapping.