Specs for User Permissions to Modify All Metadata and Process Book Metadata
USER STORY / CONTEXT
In Phase 1 at this point, to work and maintain data integrity in the Bookshelf archive, minimum requirements are needed, which are reductions to the scope of the original Phase 1 metadata user stories and consequent changes to original plans for implementation of those stories.
MINIMAL REQUIREMENTS
- All non-NCBI Book Metadata fields (e.g., source type) in the whole book scenario that must come from a combination of source files and conversion / tagging agreements must be locked to any user edits. -- see UI in #819 (closed)
- Notify the system admin assigned to the Organization whenever collection or chapter-processed book metadata is saved -- NCBI to provide notification text.
- For chapter-processed books, there needs to be a new button that permits bulk selection of chapter components and to a) reload them to PMC (without having to make modifications to chapter files). The current "publish" button should allow republishing (without having to manipulate files). The ability to reload and republish in this phase will follow existing specifications for status properties and permitted actions. It would be the responsibility of Bookshelf Staff System Admin in this phase to note content with these statuses and coordinate they updates in a reasonable time frame based on where they are in the workflow. -- See updated design below:
- For XML conversion, agreed collection values and source type values will be sent to NCBI as JSON files. Any other metadata can be edited / added via source files. Publisher name and location can be hardcoded as is in existing converters, but will need to be supported as Phase 2 priority.
- For PDF workflow, any metadata not created and written by the BCMS will be provided by Bookshelf Staff Admin to the PDF2XML taggers via uploaded files in the Support Folder for the PDF2XML taggers to add to the converted XML they deliver. Any necessary changes to that wholebook metadata will be made by Bookshelf Staff System Admin to the converted XML and reloaded.
ACCEPTANCE CRITERIA
Refer to linked ticket #776 (closed)