Paper Publishing

— Volumes are refreshed.

— Files are concatenated as per defined volume ranges.

— Cross-references are converted to margin cross-references. See the chart in the Linking Tools section.

Submit an Electronic Publishing Request

Before submitting an electronic publishing request, you should be aware of the limitations.

— All electronic publish requests must be made from assemblies that have leaf elements. Leaf elements represent output documents to Ennov InSight . Electronic publishes without leaf elements in the assembly will not generate output.

— For single file electronic output, all content and sheets (such as TOCs and cover pages), with the exception of native files, are included in the published output.

To submit an electronic publishing request:

1. On the Assembly Attributes page, do the following:

   Option	Action
   For a sequence assembly:	Choose Publishing above the assembly tree.
   To publish the entire assembly or choose a folder to publish:	Click the assembly root.

2. Click .
3. On the Publish Request page, choose Electronic from the Publishing Output Channel list.
4. To choose the repository location to publish the electronic submission, click Browse.

   When choosing a folder for a published output location, the name of the folder cannot contain both Unicode characters and a space character, as this will cause an invalid path error. If you are using Documentum as the repository location, move to the next step. Else, go to step 6.

5. Under Output Document Type, choose the document type.
6. Check Append Application and Sequence Number to create subfolders in the output location. The subfolder names comprise the application followed by the sequence number.

   — You must check this box to avoid having an invalid relative path in the STF.xml file.

   — Because Ennov InSight automatically appends the application number and sequence code to the folder path during publishing, you should always use legal file system characters in these attributes. The following characters are not legal on a file system: \ / : * ? " < > |

   Warning: For Assembly Plans, the values are taken from the Application Number and Sequence Number values of the Metadata Library (US Module 1 Application metadata type).

7. If you need to generate renditions for assigned documents, special sheets, TOCs, overlays, select Prepare to Publish .
8. Choose one of the following to indicate what should be published:

   Option	Description
   Publish to a Single File:	Publishes to one PDF file all elements in the entire assembly that are flagged for the electronic output channel. All content and sheets (TOCs, cover pages, etc) are included in the published output, except native files. Native files are omitted.
   All Leaf Elements:	Publishes all the leaf elements in the assembly to individual output files.
   Selected Leaf Elements:	publishes only those leaf elements that are included in the selected folder.
   All Leaf Elements and XML:	Publishes all the leaf elements in the assembly to individual output files. The eCTD XML backbone is published according to the appropriate XML definition file.
   Selected Leaf Elements and XML:	Publishes only those leaf elements that are included in the selected folder. The eCTD XML backbone is published according to the appropriate XML definition file.
   XML Only:	Publishes the eCTD backbone XML based on the appropriate XML definition file. None of the leaf elements are published.

   Note: Reference leaf elements publish their xlink:href path as the minimum necessary relative path required to take the reviewer to the correct document. References to other sequences do not contain the application number; references outside the application contain the application number.

9. If Publish to a Single File is selected, in the Single File Output Filename box, enter the output file name for the assembly.
10. In the Include Leafs with Status multi-select box, select the leaf statuses of leafs you want to be published.

    By default, all active Leaf Statuses from Data Administration|Submission Maintenance section are listed in the Selected box. Deselect, if needed. The leafs with selected statuses are included in the electronic publish to generate output leaf files. This option does not affect the XML generation. For XML, all leafs are included, independent from the status assigned.

11. Next to DMS Versioning Scheme, choose one of the following for the published output files:

    Option	Description
    Same:	Indicates the published output files should have the same version number as previous output. (Choose this when you are publishing to a file system.)
    Minor Version:	Indicates the published output files should be increments to a minor version.
    Major Version:	Indicates the published output files should be increments to a major version.

12. Click OK to submit a publish request.
13. Chose Go To > Job Requests to view the status of your publication request.
14. Once the job is complete, navigate to the publish output location and confirm publication.

Submit a Paper Publishing Request

You can submit a paper publishing request and customize its details such as page counts and versions.

To submit a paper publishing request:

1. On the Assembly tree, do the following:

   Action

   For a lifecycled sequence assembly, choose Publishing view above the assembly tree.

   Click the assembly root, a volume, a folder, a leaf, or a document.

2. From the action bar on the right, click . The Publish Request window opens.
3. Under Publishing Output Channel, choose Paper.
4. To choose the repository location to publish the paper publication, click Browse. If you are using Documentum as the repository location, move to the next step. Else, go to step 6.

   Note: If this is a Standalone assembly, do not check Append Application and Sequence Number.

5. Under Output Document Type, choose the document type.
6. Check Prepare to Publish to create PDF renditions if you are using the Ennov InSight rendering and publishing services.
7. Use the Update Volume Page Count option to update the volume page counts from the publish request screen.
8. Next to Publish Paper, select which volumes to publish:

   Option	Description
   All Volumes:	Publishes all volumes in the submission.
   Volumes in Selected Range:	Publishes only those volumes that start in the node you have selected to publish.

9. Next to DMS Versioning Scheme, choose one of the following for the published output files:

   Option	Description
   Same:	Indicates the published output files should have the same version number as previous output. (Choose this when you are publishing to a secure file system.)
   Minor Version:	Indicates the published output files should be increments to a minor version.
   Major Version:	Indicates the published output files should be increments to a major version.

10. Click OK to submit a publish request.
11. Choose Go To > Job Requests to view the status of your publication request.
12. When the job is complete, navigate to the publish output location and confirm publication.

When publishing paper volumes, regardless of where invoked, the Publish All Volumes option will output all publishable volumes in your assembly.

Publish Commands and Volumes

For publishing volumes in the selected range, the output produced is dependent on where the publishing command was invoked.

Publishing Leaf Elements

During publishing, if a leaf has no content, it will be published with a checksum of null (empty checksum attribute) in the XML.

A final run of the Ennov InSight Validator tool will correctly set all checksums and confirm XML validity.

After publishing, when you choose View File for an empty SPL XML leaf element, an error message appears in the assembly. This is expected behavior.

You cannot preview cover pages. You can preview only source document renditions, TOCs, and tabs.