Don't see saved Edited Book Metadata changes in the BCMS UI form
Context
This was reported from GeneReviews team in testing feedback in #1486 (closed). Use case: Multiple users can work on the same book at the same time, so there is chance that user who have the permission to edit Book metadata can attempt an edit simultaneously.
In the example for GeneReviews:
- User A enters two edits to the book metadata: changing text in abstract and adding a license, but when user A saves these changes and closes out of the book metadata and reopens it, they do not see those changes recorded in the forms
See clip: metadatadoesnotsave
Proposal
Show edit history information in the Metadata modal so that users are aware of when it was last edited and by whom. This same approach can be taken in other forms in the BCMS.
Design
Acceptance criteria
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)
Users with the same access rights to book metadata and settings forms, the forms cannot be edited concurrently:
- When User A opens the form to edit, the system locks the form for editing by other users.
- If User B tries to open the form while User A is editing, they see a message indicating that User A is currently editing the form. The form fields are disabled or read-only for User B.
- Once User A finishes editing and closes the form, the lock is released, and other users can now edit the form.
- To avoid the possibility of User A blocking User B from editing the form by accidentally leaving the form open in a browser tab, implement a timeout feature that automatically releases the lock after a certain period of inactivity.
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking