Exporting a DDN
DDN Export lets you export modules or graphics, recursively or not, locked or not.
Before you begin
To export a DDN, you must have created a Dispatcher and added content (DMs, PMs, SCPMs, and graphics) to it. See Collecting Content to Export to a DDN.
About this task
The result of exporting a DDN is a .zip file that contains the selected content and an XML file that contains the information you entered in the UI and a list of the codes of the selected content. If you are including referenced objects, a second .zip file that contains a text log file reporting the status of each referenced object will also be provided.
You can only export graphics of one of the supported file types, per the SDL Contenta S1000D Cross-Product Graphics and Multimedia Support Reference section of this documentation.
If you export objects that refer to other objects (for example, DMs that refer to graphics), the referenced objects are not included in the DDN unless either or both of the Modules or Graphics check boxes are checked in the Include Referenced Objects section of the UI.
A log file will be written to the <Contenta_home>/web/cw_common/custom/S1000D_DDN_Export/DDNexports directory. This file will be zipped, and named Dispatcher-object-name-log.zip, which you can download after DDN Export finishes running. A link labeled "Click here to download the log.zip file" will appear below the link used to download the DDN .zip file. The log file contains the name of the Dispatcher object, a date stamp, the user's login name, the types of each referenced module (DMs, PMs, SCPMs, or graphics), whether modules were exported recursively, and the status of each referenced object.
Note the following regarding the log file:
- Any modules or graphics that you do not have access to (because they are in a configuration that is not on your desktop) will be reported as inaccessible.
- Any modules or graphics that cannot be found in the CSDB will be reported as missing.
- If you set Lock Referenced Objects on Export to Yes, and DDN Export finds a referenced module or graphic that is already locked, a message indicating that this object was exported but not locked will be added to the log file.
Sample output of an Include Referenced Objects log file.
DDN Export referenced objects report
DDN: Dispatch123
Date: 2016/03/24
User: sysadmin
Type: Referenced modules only, exported non-recursively.
Exported referenced DM: DMC-SAMPLEBIKE-CCC-D00-00-00-00AA-041A-A.xml
Warning: Cannot export missing referenced DM: DMC-SAMPLEBIKE-CCC-D00-00-00-00AA-043A-A.xml
Exported referenced DM: DMC-SAMPLEBIKE-CCC-D00-00-00-00AA-00WA-D.xml
Exported referenced DM: DMC-SAMPLEBIKE-CCC-DA0-10-20-00AA-400A-A.xml
Exported referenced DM: DMC-SAMPLEBIKE-CCC-D00-00-00-01AA-941A-D.xml
Exported referenced DM: DMC-SAMPLEBIKE-CCC-DA2-10-00-00AA-520A-A.xml
Exported referenced PM: PMC-SAMPLEBIKE-XYENT-00030-01.xml
Exported referenced DM: DMC-S1000D-E-04-10-0301-00A-022A-D.xml
Two Referenced Objects Use Cases
- Reuse DMs into your Dispatcher, and also include the graphics referenced by those DMs:
- Reuse DMs (which may reference graphics) into the Dispatcher.
- Check the Graphics check box.
- Leave Recurse set to No.
- Reuse a PM into your Dispatcher, and export the entire publication by including referenced, nested PMs, DMs, and graphics recursively:
- Reuse a PM into the Dispatcher.
- Check both the Modules and Graphics check boxes.
- Set Recursion to Yes.