Remove query to display {book-component-version}.{file-version} number on the chapters rows of the book manager
Context
The book manager displays a list of book components. Each component may have multiple versions -- each of which may have been published before. A current requirement of the book manager is: For each book component listed, display the published date and {book-component-version}.{file-version}
number of whichever {book-component-version}.{file-version}
was most recently published.
When books have a high number of book components, the queries to get this data is affecting the performance and therefore usability of the book manager page.
Proposal
Remove the query to get the {book-component-version}.{file-version}
value for "last published". Get "last published" date only. NCBI has agreed to this in a meeting (1 Feb '23) since it does not negatively impact users ability to perform their tasks on the book manager page.
Design
Only design change is the removal of the version number in brackets after the "last published" date. Here is the current design:
Here is the design after this implementation:
Acceptance criteria
-
Each chapter listed on the book manager page lists the "Last published" date if the chapter has been published -
The component.file version number will no longer display after the "Last published date" on the book manager page - see screenshot below of what will be removed (crossed out in blue) in the highlighted information. Note: Existing users may need to hard refresh their browsers to see this change.
Screenshot from: https://ncbi.cloud68.co/organizations/6c4d37c4-b9f2-4962-9080-b3e29a37dfbd/bookmanager/7f099bb1-3379-4beb-bc4b-aeca26884a47
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 by Coko -
Deployed and tested on “ncbidev” of cloud68 (by Coko team) -
Deployed and tested on “ncbi” of cloud68 (by NCBI team) -
Acceptance Criteria Met
Implementation
Alternative approaches (if applicable)
Scheduling
- Milestone:
- Iteration:
- Dependencies: (list issue numbers if relevant)
- Development estimate (hours):