The update cycle

Publishing the mainwork establishes a baseline from which subsequent changes to published leaves or pages can be identified. The following cycle is repeated indefinitely as the partition advances through a succession of releases:

  • Create the Next Update.

  • Label the release (for example, July 2013).

  • Apply any corrections and alterations to the source content.

  • Compose the release and proof the output pages.

  • In a full looseleaf publication, you may want to consolidate the set of changed leaves to minimise the number of leaves issued in the release.

  • Publish the release. A full looseleaf release can only be published if it can be composed without warnings and errors.

  • For electronic publications you can now create a PDF for the entire publication and a list of effective pages (live pages list).

  • For printed publications you can create an update pack consisting of:

    • all new or modified leaves;

    • a set of filing instructions detailing which pages should be removed and where the new material should be inserted;

    • an optional list of effective pages.

After each cycle is complete, the system is ready for the creation of the next release.

The cycle continues between update and publish throughout the life of the document. When each new update is created, TopLeaf can automatically remove releases that are no longer required. The number of releases you want to keep is declared on the Exports tab of the Partition Properties dialog.