Sorting in MCL should retrieve sorted results from backend
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
is cloned by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Owen Stephens December 13, 2021 at 9:26 AM
Where necessary specific stories should be written to implement sorting in an MCL
Jag Goraya October 19, 2020 at 10:22 AM
On hold pending discussion with ERM subgroup on 21 Oct.
Jag Goraya October 12, 2020 at 2:48 PM
Hi @Aditya matukumalli let's pick this up on Wednesday's call to discuss the effort involved going forward and the impact of making this change for MCL complexity, as per @Owen Stephens query raised in mid-sprint review ... cheers
Aditya matukumalli October 8, 2020 at 6:43 PM
@Owen Stephens @Jag Goraya After some investigation, the sorting is doable by fetching the resources from the backend. I have the logic up here on this branch https://github.com/folio-org/ui-agreements/tree/packageContents-sort for us to re-visit later.
Won't Do
Details
Details
Assignee
Owen Stephens
Owen StephensReporter
Owen Stephens
Owen StephensLabels
Priority
TBDSprint
None
Development Team
Bienenvolk
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 5, 2020 at 1:06 PM
Updated December 13, 2021 at 9:26 AM
Resolved December 13, 2021 at 9:26 AM
TestRail: Cases
TestRail: Runs
When applying sorting in an MCL, if the MCL is only loading partial results any sort request should go to the back end to get the full sorted results
This applies to:
Agreement preview -> Agreement lines -> Name/Description column
Resource preview -> Agreements for this e-resource -> Name and Status columns
Package preview -> E-resources in package -> Name and Platform columns
The same process should apply whenever we have a situation where the MCL is loading results that maybe paginated