Calyx RIM 7.0 Publishing

Tables of Contents

Tables of Contents (TOCs) enable you to find contextual information in a published assembly. The creation of TOCs is dependent on document structure, as each submission document can contain several levels of document structure elements in a familiar hierarchy. For CTD TOCs, the hierarchical structure roughly follows the eCTD hierarchy, but for other publications such as study reports, the structure may differ.

You can treat TOCs as additional assigned documents in the repository that are not part of the lifecycle or content, but are needed during electronic and paper publishing. These TOC documents can be generated into .doc format for use and modification in Microsoft Word or other word processing applications. Normal rendering processes can create final TOC documents in the publishing output file format.

When you insert a TOC into an assembly the default TOC type is used automatically, or you can choose an alternate TOC type. You specify the default TOC settings in the Publishing Settings Library Templates, and a default TOC is required. In the publishing settings, you may create an association between different TOC types and assembly elements or locations. This association is called mapping.

When publishing tables of contents that include a range to which all content has not yet been assigned, TOC entries that cannot be targeted. For example, when no content yet exists under the leaf, TOC entries are stamped with the Destination Not Found Text from the Publishing Settings. Once the content is assigned to the leaf, the TOC entry stamp correctly resolves to the destination.

If you are defining (mapping) a TOC for volumes, when you insert a TOC on a volume the TOC type associated (mapped) with a volume may be inserted automatically. As long as the TOC types are defined correctly for the appropriate elements before bulk insertion, little editing of the assembly is necessary to generate valid TOCs.

When you generate a TOC, a Word document is created from the information about the TOC in Calyx RIM. The TOC is combined with the style and format specified in the TOC template. The TOC is then rendered to a PDF and the right-column text and hyperlink is resolved during final publishing. There are various ways to create a TOC, for example:
  • Generate the TOC from the default range directly to a PDF during final publish; this is best suited for volume TOCs.
  • Edit the TOC in the TOC editor, then generate the TOC from the TOC editor directly to a PDF during the final publishing.
  • Generate the TOC from the default range to the Word document preview, edit the preview, then publish the Word document to a PDF during final publishing; this is best suited to submission TOCs.
  • Edit the TOC in the TOC editor, generate the TOC from the TOC editor to a Word document preview, edit the preview, and then publish the Word document to a PDF during final publishing; this is best suited to a submission TOC.

Generated TOCs are saved to the preview location specified in the TOC publishing settings.

When you preview a generated TOC, the system makes a copy of the TOC in a temporary location (regardless of the defined preview location) and displays that copy for preview. Any changes you make to the previewed TOC are made on the temporary copy only, and are not made on the actual TOC that will be published.

Note: In some desktop configurations you may have to save the TOC to a local file and open the local file to view the TOC.