[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: PNG File Skærmbillede 2019-05-17 kl. 15.49.10.png    
Issue links:
Blocks
blocks UISE-68 Codex search treats Swedish diacritic... Closed
blocks UISE-70 Codex search results are taking Nonfi... Closed
blocks UISE-80 Search results are not sorted by title Closed
Relates
relates to UXPROD-2667 Inventory. Result list Refined displa... Open
relates to UXPROD-1634 Inventory. Result list Refined displa... Closed
relates to UIIN-525 Basic search: Titles with thousand se... Draft
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 UISE-80 Closed pertaining to a mismatch between the sort-orders used by the two Codex-source modules. This is fatal, as the Codex multiplexer (mod-codex-mux) needs the lists it merges to be sorted in the same order so that it can zip them together. There is no other way it can work. (The multiplexer could re-sort the aggregation of all the records it gets from the sources, but if they're not already sorted in the same order, then when the next batches get fetched, they won't all correctly sort after the first batch, so you still won't get a consistently sorted list in the UI.)

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 ...

CC: Julian Ladisch Niels Erik Nielsen Mike Taylor

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.

Generated at Thu Feb 08 23:12:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.