Wholebook metdata UI and backend
Workflow for wholebook book meta
See flow diagram in #678 (closed) and the related book-meta sheet.
For PDF wholebooks
- if "permissions" values are applied from collection level, these are sent to Apex whenever the users "submit"
- if "permissions" values are not applied from the collection level, NCBI sys admin uploads as a file to support folder, then these are sent to Apex whenever the users "submit".
Wireframe
- This wireframe simplifies the current book metadata UI which was developed for chapter-processed book.
- Based on the information provided in the book-meta-sheet, the simplifications include
- extract fields that are required by BCMS
- extract fields that are not included in the generated Preview which users need to validate quickly (i.e. without downloading the converted xml file)
- all fields being read from the converted xml file are non-editable. plain text fields. Any xml tagging within the fields supported will display as is (no stripping) -- Book title field to be discussed -- see #558 (closed)
- Fields that users cannot edit are filled in grey
QA feedback
These fields do not update n the UI after getting the converted file:
-
publisher
-
publisher location
-
publication date
-
subtitle
-
DOI
-
Volume \ Issue number
-
Edition
-
Alternative title
See example book here