PDF workflow components are getting stuck in "tagging" status when they should be moved in BCMS to "previewing"
Expected behaviour
All book components should move to the next workflow status if and when a tagged package is successfully delivered by the PDF2XML taggers. These files should be also successfully ingested to the BCMS and sent to PMC ingest to create a preview.
Current behaviour
PDF workflow components are getting stuck in "tagging" status even with the PDF2XML deliver tagged packages meeting NCBI specifications, and in some cases when those files are successfully ingested into the BCMS.
Steps to reproduce
This is hard to reproduce because we don't know what is causing the stuck statuses.
Example where this has occurred in Coko test site:
(1) https://ncbi.cloud68.co/organizations/92399e0c-d133-4450-b4d1-29eb6dde6d5b/bookmanager/507f1b86-a2d0-4a5e-ab47-db2f3f9d73f3 - note the files were correctly ingested to BCMS
There are many examples in this organization: https://ncbi.cloud68.co/organizations/92399e0c-d133-4450-b4d1-29eb6dde6d5b
Environment
Possible solution
(1) Identify source of problem: During the sending of the FTP file, the FTP server failed and returned an error, which caused the app to skip the registration of the chapter submission to APEX folder and thus means it didn't get assign an id.
Solution: improve code by assigning the id prior to file upload.
If this doesn't cover all cases of a component getting stuck in tagging then estimate:
(2) Add "tagging" to the statuses Bookshelf staff can clear in /jobs UI so operations are not blocked nor duplicates created causing version of record issues
QA Steps
[To be completed by Coko once dev is done]
Scheduling
-
This issue is blocking current user testing -
This issue is blocking current migration testing -
Fixing this issue is required for Priority 1: Deploy MVP -
This issue should be triaged into later epics in the PM weekly meeting