Reasons to change mappings
If, for example, a user renamed an item after transfer or you want to move an item to another location, you would need to change the implicit mappings that Content Porter creates during a transfer.
- Scenario 1: A user renamed an item after transfer
-
After Content Porter has transferred a piece of content, Content Manager users on the source system or on the destination system are free to change its name.
For example, say you transfer a Component called OldName from your source system to your destination system, after which a user changes the name to NewName on the destination system. If you now transfer OldName again, Content Porter will not see an item with that name on the destination system, and create it. This results in two items, OldName and NewName, on the destination system.
To prevent this from happening, open the mappings file and explicitly map the OldName item to NewName. You now make Content Porter aware of the fact that the item was renamed, and during transfer, Content Porter renames OldName to NewName and, as a result, updates the NewName item on the destination system.
Use the same approach if after a transfer, someone renames the item on the source system. In this scenario, the source system has an item NewName which you must map to the unchanged OldName on the destination system.
- Scenario 2: You want to move an item to another location
-
Sometimes, the organization of your source system is different from the organization of your destination system.
For example, say you have created an instance of Content Manager that you want to use as an archive of your Web site. Every month, you transfer your Web site to this instance. On the destination instance, you create a new Folder and Structure Group for each month:
Now depending on the month, you would want a Component located in Building Blocks\Folder1 on the source system to be moved to Building Blocks\September 2011\Folder1 on the destination system. You can accomplish this by explicitly mapping to that destination location in your mappings file. Note that the destination location must already be present on the destination system.