Permit Editors, Org Admin, System Admin to Fail a Job and Send it back to New Upload
Context
GeneReviews and other NIH power users have reported that they are losing lots of wasted time updating their files when they make a mistake and press "Submit" and immediately know there is a problem with the files they processed. But they can't fix the problem for sometimes more than four hours because the status is in an active "Converting" or "Loading Preview" status. They have requested the ability to Abort or Fail a job and have it automatically go back to a "New Upload" status if the source file was in "Converting" or "Loading Preview" with the ability to upload a corrected Source file.
Proposal
- Add a "Fail" button On Chapter / Book Component pages to the Left of the "Reload Preview" status
- "Fail" button is active for Editors, Org Admin, System Admin IF Source files are in "Sending," "Converting," or "Loading Preview" status
- If user presses "Fail" a "Fail" notification is sent back to PMC Task Manager to Fail any active sessions, AND
- When user presses "Fail" button the Component Status and Source File status becomes "New Upload"
- User can upload new source file and press "Submit" again
Design
TBD
Acceptance criteria
-
Editors, Org Admin, and System Admin can press "Fail" button On Chapter / Book Component pages If Source files are in "Sending," "Converting," or "Loading Preview" status -
Editors, Org Admin, and System Admin can Upload and Submit new source file after they press "Fail" and the Component and Source File changes to "New Upload"
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