Draw workflow diagram: SFM overview
Hi @John.kopanas, @jure, @yannis and @danjela This diagram show an overview of the SFM workflow for content that is manually submitted.
cc @adam
There are a lot of different tasks that can happen in the 'Editing' and 'Reviewing' states depending on the type (Word/PDF) and quality (complete/incomplete/with issues/etc.) of the files submitted. I'll break these down in more diagrams, but the important things to understand now include:
- The 'Editing' state means preparing content for publishing. This work is done by the Organisation team who submits the content.
- The 'Reviewing' state means checking, resolving issues, and approving content for publishing. Both the Organisation and NCBI teams do this work at various stages in the workflow.
- A preview of the content is only available after it has been successfully converted to XML and pushed to NCBI's staging site.
- There are essentially only two states that the content can be in before it is published live: Editing and Reviewing. These states can be made more meaningful for the users with standardised or customised statuses. At a minimum I think we should differentiate between content that is being reviewed by the Org or by the NCBI.
- The Source files being managed are:
- the original source files submitted by the organisation: Word/PDF book documents and supplementary files
- the converted XML files (provided by the data supplier) that will be used for publication.
- Versioning needs to be tracked for both original source and published source at the file and document level.
Here is an example set of files that a Org might submit manually:
And here is the final published book on NCBI's Bookshelf: https://www.ncbi.nlm.nih.gov/books/n/cer141
Let me know if you have questions. I'll ask NCBI to sense-check too.