FastTrack PDF

Table of Contents inconsistencies between web and fast-track delivery channels

As a language producer, I understand the table of contents for fast-track PDFs is generated from a different part of the XML files than the table of contents appearing in web content on lds.org. The fast-track PDF draws its TofC from the TofC in the XML language file; lds.org process dynamically creates the TofC based on text from the chapter headings.

In our current web first, then PDF second processes, if there are any inconsistencies or errors in the XML language file, those issues don't arise until the fast-track PDF review which is intended to simply be a completeness check as a secondary delivery channel. Instead, text is needing to be altered and corrected during the fast-track process.

Because many documents for Seminaries & Institutes are multi-channel delivery, it would be very helpful if TofC’s are generated the same way for both web and fast-track processes. One solution is to change how TofCs are created for web review. Another solution is to remove the table of contents from the source files. Technically this may not be considered a fast-track issue; however, the effectiveness of fast-track reviews are being compromised and delayed because of this issue.

Fixing this inconsistency will reduce review cycles in secondary delivery channels and allow for faster delivery.

  • Randall Pixton
  • Feb 9 2017
  • Attach files
  • Preston commented
    February 10, 2017 20:15

    I heard from Zak Nyberg that when he talked with Dave Egbert about this HTML5 should fix this. Where right now we pull lesson titles from multiple places it might be simplified in HTML5 so that we pull from one place, which would help with this problem where different channels pull from different parts of the XML.