[FOLIO-1281] define sorting semantics for titles and names Created: 11/Jun/18 Updated: 01/Nov/23 Resolved: 01/Nov/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | search_enhancements, search_result, sprint40, sprint41, sprint42, sprint43 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||
| Description |
|
There are sorting discrepencies between local inventory and the KB. Let's try to define the soriting algorithm for both and see if we can find a common approach. Adam Dickmeiss Carole Godfrey Hongwei Ji |
| Comments |
| Comment by Carole Godfrey [ 11/Jun/18 ] |
|
Jakub Skoczen - mod-codex-ekb is reliant upon RM API for sorted results. I spoke with product owner for RM API regarding these sorting concerns. Per his suggestions, we should provide specifics on any issues we are seeing with the KB sorted results so they can be addressed. Issue https://folio-org.atlassian.net/browse/UISE-80 though seems related to local and Kb results being sorted with one another though. |
| Comment by Mike Taylor [ 11/Jun/18 ] |
|
Carole Godfrey You are dead right about
|
| Comment by Mike Taylor [ 19/Jun/18 ] |
|
What is the status of this? Is anyone in charge of moving it forwards? |
| Comment by Charlotte Whitt [ 17/May/19 ] |
|
In the very recent Bug-fest environment - https://bugfest.folio.ebsco.com (folio/folio) The sorting of titles beginning with numbers is not listed in expected numerical order, but the sort is done character by character so 1001 is coming before 100 ... |
| Comment by Christine Schultz-Richert [ 01/Nov/23 ] |
|
Closing as part of an effort to review prioritization and clean up backlog. We are able to revisit if needed. |