create toc for chapter-processed books in XML workflow
@lathrops1, @latternm, @John.kopanas
Use case:
XML content is submitted by FTP one chapter package at a time. This content can be published without Preview approval. An Org user doesn't need to come into the BCMS, unless there are errors to resolve. So the ordering of book components needs to be communicated via an a toc.xml FTP package.
- User submits FTP package (according to specs in #183). The manifest file should include
file type
andfilename
, e.g.
toc toc.xml
- The toc.xml file must show entire structure of book, including any parts
- Each
<toc-entry>
node must includetitle
anddocument-id
which matches the info in submitted meta.xml for the related chapter. E.g.
<toc-entry>
<title>Preface</title>
<nav-pointer><related-object document-id="preface1" document-type="preface">
</related-object></nav-pointer>
</toc-entry>
- Coko uses toc.xml file to order content in Book manager
- The only way to change the order is to submit an updated toc.xml file
- Coko processes toc.xml to add filename and version number (if the book supports multiple published versions).
<toc-entry>
<title>Preface</title>
<nav-pointer><related-object document-id="preface1" document-type="preface">
<?xml_file preface.xml?>
<?version 2?>
</related-object></nav-pointer>
</toc-entry>
@lathrops1 please confirm the above, update the submission specs accordingly, and provide a sample package.