Hi, the challenge is to recreate a collection of content that exists in one Tridion CMS server environment into another Tridion CMS server environment (beta, gamma, prod).
Using Content Importer, can I import all these dimensions (versions and language layers) of the maps and topics?
Thanks in advance,
Ann
I can offer part of an answer, before RWS responds. If the content and metadata only need one file, then content importer does that.
For example, if you are starting with content exported from the same instance that you are importing to, and you also no longer have objects with the same GUIDS, and a .met file specifies that a topic is version 3, it will be imported as version 3 of the topic. If you look at the version history, it starts with version 3.
I encountered a problem where exported content had an object that was a branch, e.g. version 3.1.1, then content importer failed because there was no version 3.1. I didn't try it, but maybe this could be solved by having the other versions available as files. You could test that.
For example, if the input directory was like:
in\main.ditamap
in\v3\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.dita
in\v3\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.met # specifies version 3
in\v2\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.dita
in\v2\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.met # specifies version 2
maybe that would import 2 version.
The same idea might apply to the language level and the resolution level.
I can offer part of an answer, before RWS responds. If the content and metadata only need one file, then content importer does that.
For example, if you are starting with content exported from the same instance that you are importing to, and you also no longer have objects with the same GUIDS, and a .met file specifies that a topic is version 3, it will be imported as version 3 of the topic. If you look at the version history, it starts with version 3.
I encountered a problem where exported content had an object that was a branch, e.g. version 3.1.1, then content importer failed because there was no version 3.1. I didn't try it, but maybe this could be solved by having the other versions available as files. You could test that.
For example, if the input directory was like:
in\main.ditamap
in\v3\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.dita
in\v3\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.met # specifies version 3
in\v2\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.dita
in\v2\GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.met # specifies version 2
maybe that would import 2 version.
The same idea might apply to the language level and the resolution level.
Translate
