Review workflow for PDF and XML (Phase 1)
There are four actions in the review workflow:
- Request Review:
- action can be taken by Editor or Author.
- sends email notification to all Previewers associated to the book and chapter team
- action is blocked if there are no associated Previewers
- Revise:
- action can be taken by Previewers
- sends email notification to all Authors associated to the chapter team
- action is blocked if there are no associated Previewers
- Approve:
- action can be taken by Previewers
- sends email notification to all Editors associated to the book and chapter team
- Ready to publish:
- action can be taken by Editor or Org Admin
- (currently no email notification on action)
PDF and XML workflow, when content is submitted by FTP, the Previewer's contact details could be provided in the meta.xml file. (see #438 (closed) here). If this user gets an email notification to review a chapter, he'll need to sign up first (and request to join the org?). It's unclear how this flow should work.
For a phase 1 mitigation we could remove all notifications, making the actions simply a way to track status in the BCMS, and Sys admin/Org admin coordinate approval from external Previewers by email.