These entire rendition related source attributes are repeating, i.e. can contain several values, in order to support multiple renditions for a single document version.
The attributes along with the exported content of the renditions allow you to migrate the renditions of the source objects to the target system.
Let us now see how the Documentum importer supports renditions when importing into a target repository. You can control the renditions of an object through a set of migration-center system attributes that are named like the rendition source attributes presented above, i.e. “dctm_obj_rendition”, “dctm_obj_rendition_format”, “dctm_obj_rendition_modifier”, “dctm_obj_rendition_page” and “dctm_obj_rendition_storage”.
To keep the renditions for an object and migrate them as they are, the system attribute “dctm_obj_rendition” must be set to contain one single transformation function:
This transformation function will simply copy all paths in the source attribute “dctm_obj_rendition” to the target system attribute “dctm_obj_rendition”. The importer will pick up the content from the locations specified in this attribute and add them as renditions to the corresponding object version in the target system.
Of course it is possible to add /remove individual renditions to/from objects by using migration-center’s transformation functions. This can prove useful if renditions generated by third party software need to be appended during migration. These renditions can be saved to files in any location, which is accessible to the migration-center job server that runs the import job. Just add the paths to these files to the target system attribute “dctm_obj_rendition” and the importer will do the rest.
The following table shows all rendition related system attributes of the Documentum importer: