Staff Client eg grid not sorting alphabetically
Bug #1912840 reported by
Llewellyn Marshall
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned | ||
3.10 |
New
|
Undecided
|
Unassigned | ||
3.11 |
New
|
Undecided
|
Unassigned | ||
3.9 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Version: Evergreen 3.5.1
Browser: tested in Firefox & Chrome
When sorting by text columns in the AngularJS staff client, we found that records in all caps were sorted above lowercase records. This was confusing to catalogers trying to look at holds on a very popular record. They'd assumed that records in all caps would be treated the same as lower case strings and intermixed within them. I found that the comparator for the data in the grid service was using the same comparison function regardless of type.
I've created a code patch that addresses this issue by utilizing different comparator functions based on the type of the data. For strings, the data is compared while lower case.
tags: | added: sorting |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | none → 3.9.1 |
Changed in evergreen: | |
milestone: | 3.9.1 → 3.9.2 |
Changed in evergreen: | |
milestone: | 3.9.2 → 3.10.1 |
Changed in evergreen: | |
milestone: | 3.10.1 → 3.10.2 |
Changed in evergreen: | |
milestone: | 3.10.2 → none |
To post a comment you must log in.
Pushing this code patch to production solved the issue we were experiencing when attempting to sort large numbers of holds on catalog records - sorting alphabetically by patron name to determine as closely as possible specific patron's position in the queue