NCBI testing release 29 Sept
Hi @lathrops1
All issues are linked at test-20210929
Feature 1: PDF source submissions
Manually uploading source files for Users Sys Admin, Org Amin and Editor to submit for conversion in the PDF workflow -- this relates to following User Stories:
In Files management (&21):
-
As a submitter, I need to be able to upload files to the BCMS UI under the following contexts: -
Upload bulk new and updated chapter files for a book when updating a database-type resource weekly or monthly -
Upload new, corrected, or missing associated files directly to a book or chapter component files page at demand - CANNOT SUBMIT - See #777 (closed) -
Bulk upload source or converted files to a (whole) book when doing large scripted data cleanup or data migration -
Upload converted files to load to PMC when there is no source files available because of legacy conditions or there is no supported conversion workflow via the BCMS -
Have processing support or review files uploaded automatically or manually depending on necessity for troubleshooting, communicating with non-submitting users, and later reuse - see issues with support files in Delete issue here - #118 (closed)
-
Note: the actions per status are tracked in the BCMS Status/Actions sheet -- the "tagging" status has been added in this release. - see issue with "tagging" status not in filters - #779 (closed)
In User management (&22):
"Data suppliers and/or editors need to be able to submit accepted content on behalf of publishers for display in Bookshelf and searchability in Bookshelf and PubMed"
[COMPLETE TESTING PENDING PDF WORKFLOW SUPPORT]
-
May submit by FTP ormanual upload - PARTIAL COMPLETE, CAN ONLY TEST PDF2XML DATA SUPPLIERS POSTING TO FTP BECAUSE CANNOT ADD AS USERS YET -
May submit one or more new or updated chapters or books PARTIAL COMPLETE, CAN ONLY TEST PDF2XML DATA SUPPLIERS POSTING TO FTP BECAUSE CANNOT ADD AS USERS YET
Feature 2: PDF (book and chapter) conversion integration
As specified in #404 (closed), summarised here with key details required for Apex
Files submitted to Apex:
- are packaged in this folder structure: bcms-to-apex-sample-20210929.zip
- the
metadata
folder is not included in this release
Files submitted by Apex:
- should be packaged in this folder structure: apex-to-bcms-sample-20210929.zip
- the
metadata
folder is not included in this release - since we don't include metadata in the expected structure yet, Apex should read the
bcmsid
in the vendor-meta.xml file for renaming display pdfs and for wholebook-processed pmcids. - the folder
bookshelf-display-pdf
had been renamed todisplay-pdfs
- In chapter-processed
chapter
submissions there must only be one xml file in theconverted
folder.- The converted xml filename must match the source pdf filename.
- an empty
<book-meta></book-meta>
node must be included in the converted xml
- Vendor must look at
book-submit submission-type
in thevendor-meta.xml
currently to know to tag as book or chapter processed - Vendor can currently ignore the JSON files posted to the FTP new subdirectory
- Packages should continue to include the domain / BCMSID, should not contain spaces and must end in
.zip
Bug fixes and design improvements
Please check following bugs and improvements:
Design improvement 1: Make the folder names in BCMS downloads consistent with the folder names used in packages sent to and received from Apex in the PDF conversion workflow: #715 (closed) (originally raised in #347 (closed))
This relates to the following user story in &22: Publisher teams (users affiliated with publishers) need to be able to download files for their books and chapters to [LOW]
[COMPLETE TESTING PENDING PDF WORKFLOW SUPPORT]
-
Fix errors in their source and associated files (see Errors user stories) -
Reuse the converted XML for their own purposes -
Make substantive updates to the content at a later time
Bug
- Preview tab lacks notice to check errors after Load to PMC #539 (closed) CONFIRMED FIXED
- Preview for previous published version should not display for new published version #683 (closed) CONFIRMED FIXED
All use cases are now complete except the new status "tagging" -- please provide the test you would to display on the Preview tab. @DioneMentis I DON'T KNOW WHAT IS BEING ASKED HERE - PLEASE CREATE SEPARATE ISSUE WITH DETAILS NEEDED
This relates to the following user story in &13: "Investigators (or their Bookshelf proxies) must review preview "proofs" of their funded content to approve visual display."
- Component metadata is not updated from converted file upload #647 (closed) -- this relates to the files management user stories above.