Export a Published Submission

You can export a published submission from the repository you specified in the publish request to another repository.

1. Click a link for the assembly you want to export.
2. Right-click the root and choose Export Published Output.
   The Export Published Output dialog box opens.
3. In the Source Location box, specify the output location for the assembly. You can click Browse under the Source Location box to choose the published output from a DMS repository or a file system.
4. In the Destination Location box, specify the the DMS repository or file system to which you will copy the published output. You can click Browse under the Destination Location box to choose a location in a DMS repository or a file system.
   Note: When exporting published output, you can only export to an existing location within the DMS repository or file system. If the path that is entered in the output location attribute does not exist, the export will fail.
   Note: For EAEU submissions, provide the valid values for the Source Location and Destination Location fields. For Source Location, a folder containing the index-r-022.xml file must be specified. See: Calyx RIM Best Practice: EAEU Submissions for details.
5. If you are exporting to a DMS repository, do the following:
   1. In the Output Document Type drop-down list, select the object type to be created for the exported documents.
      Use dm_document for Documentum or if you are unsure, or livelink_object for OpenText Content Server.
   2. For DMS Versioning Scheme, select either Minor to version existing documents as a minor version, for example 1.1, or Major to version existing documents as a major version, for example 2.0.
6. Click OK.
   Note: For EAEU submissions, select Embed PDFs into EAEU XML? and proceed further. See: Calyx RIM Best Practice: EAEU Submissions for details.
   Calyx RIM processes the export as a batch job and the following occur:

   • A new document/file is created for each repository document that is a descendant of the source folder.
   • A new folder is created for each repository folder that is a descendant of the selected folder.
   • Only the CURRENT version of a particular document or folder in the source repository is exported.
   • The document or folder name attribute is set to the repository object name for the document file.
   • The documents are placed as children of the matching folders to mirror the hierarchy in the repository.
   • Virtual documents (with and without content) and objects with no content are ignored.
   • Destination Not Found text will be used to stamp TOC entries or cross-references where the destination is undefined. By default it is set to blank, but in some processes it may be helpful to set it to some text indicating an issue with a TOC entry or cross-reference.