Add "Sending" status to book manager chapter rows
Context
Coko implemented a job queue which resolved a number of package sending and receiving issues. What this means:
- If there are 10 chapters submitted to conversion,
- chapter 1 is sent, then chapter 2, then chapter 3, etc.
The result in the UI is it that can take longer for users to see the status change, for example, from "new upload" to "converting", especially when the queue is long. This has resulted in a number of queries to NCBI Bookshelf staff from submitters thinking the BCMS is broken. It has also resulted in submitters pressing "Submit" multiple times sending multiple jobs to the pipeline causing delays and failures.
Users should see the result of their action in the UI immediately. At the moment they will see a "Submitting" spinner for the time it takes to send the first package, then that chapter's status will update to "converting."
Consequently there can be no visible change on other chapters that we selected and submitted in bulk for a while, which may lead to confusion.
Proposal
- Implement an interim status called "Sending"
- Apply new status to all use cases:
- sending for conversion
- sending for previewing
- sending for publishing
Design
TBD
Acceptance criteria
-
When user presses "Submit" to bulk send more than one component to Converting, user sees "Sending" for all Components until they reach their turn in queue to changing to "Converting" -
When user presses "Reload Preview" to bulk send more than one component to Loading Preview, user sees "Sending" for all Components until they reach their turn in queue to changing to "Loading Preview" -
When user presses "Publish" to bulk send more than one component to Publishing, user sees "Sending" for all Components until they reach their turn in queue to changing to "Publishing" -
User can Filter by the status "Sending" from main Dashboard for Book Components and from Book Manager for Book Part Components -
User can Retrigger any Component stuck in "Sending" from the Jobs UI
Definition of ready
-
BCMS User Story / Context has been well defined -
The priority of the user story is specified and agreed -
Digital assets added (design, database scheme, mockups etc if relevant) -
Coko Technical Proposal approved by NCBI -
Testable Acceptance Criteria approved by NCBI -
Estimate of effort to complete (time or points) -
The issue has been broken down into development tasks (if necessary) -
Requirements Clarified -
The product owner and development team agree that the user story is ready for development -
NCBI adds “Dev_Ready”
Definition of done
-
All coding tasks are finished and implemented -
QA approved -
Deployed and tested on “ncbidev” (by Coko team) -
Deployed and tested on “ncbi” (by NCBI team) -
Acceptance Criteria Met
Implementation
Alternative approaches (if applicable)
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking