Book component preview workflow
Hi @lathrops1, here is my understanding and queries for the workflow of previewing book components to be published.
Purpose
Checking the preview gives the content team the opportunity to confirm that they are satisfied with the rendered content as it will appear on Bookshelf when published.
Current experience
- Currently Authors/Editors (whoever uploaded the files) are sent preview links via email after the file processing is complete.
- Authors/Editors view the content in the link and make a decision:
- reject preview: user goes back to Word doc, makes changes, reuploads, waits for email with preview link, repeats until satisfied.
- approve preview: user forwards the email to others on the content team who needs to approve (Previewers), waits for response, confirms preview is approved via email
- When Previewers reject a preview, they say why and provide information on what needs to change. This may include providing replacement images as attachments in the email.
New/expected experience
Without getting into the details of what the UI looks like, the experience is:
- V1: When Authors/Editors open the book manager page, they will see book components with the status "previewing", meaning that there is a preview link to check.
- The link opens in a new tab (one for each component), Author/Editor checks the content and makes a decision:
- reject preview: user goes back to Word doc, makes changes, reuploads in BCMS browser tab, waits for Preview to generate, repeat until satisfied.
- approve preview: user goes back to BCMS browser tab, assigns one or more Previewers associated with the book to check the preview. The status might change at this point to "Pending approval" or something similar.
- V1: Assigned Previewers open the book manager page, they see book components with the status "Pending approval"
- The link opens in a new tab (one for each component), Previewers checks the content and make a decision:
- reject preview: user goes back to BCMS browser tab, types some comments, possibly attaches an image, and selects "reject".
- approve preview: user goes back to BCMS browser tab, possibly types some comments, and selects "approve".
- Status changes to "approved" and Editor can publish the chapter(s).
Questions
- What are the reasons for rejecting a preview? -- I have listed my assumptions
- missing or incorrect metadata
- broken links in the content
- incorrectly styles chapter features (e.g. an H2 should be an H3)
- cross-references to other chapters or glossary terms not linked
- missing images
- low resolution images
- What kind of files might a Previewer need to attach with their reject decision?
- Is the assumption that all Previewers associated with the book must be send the Preview to check? As opposed to the Editor or Author selecting individual Previewers from the approved list.
- A Preview can be assigned to multiple Previewers -- must all Previewers approve before the chapter can be published?
- The role permissions state the "An Editor moderates Peer Reviewers, Copyeditors and Previewers comments and assigns resulting tasks from them to members in their content team" -- what is involved in moderating Previewers comments?
- If the book component has more than one Author (as a user in the system) -- must all authors approve the preview before publishing?