Cannot find call number when its shelf key starts with same 10 first characters as other call numbers (approx. 1500 call numbers)

Description

Cannot find call number when its shelf key starts with same 10 first characters as other call numbers (approx. 1500 call numbers)

Overview: Cannot find call number when its shelf key starts with same 10 first characters as other call numbers (approx. 1500 call numbers).
It's continuing of work done in
Issue could be reproduced only on big data set, for example at: https://bugfest-poppy.int.aws.folio.org/ 

Preconditions:
We need (at least) 26 instances with holdings and call-numbers (f.e. with LC type) on item level where 26th call-number will be our exact match and 25 call number should come before.

Steps to Reproduce:

  1. Log into https://bugfest-poppy.int.aws.folio.org/ environment as admin

  2. Go to "Inventory" app

  3. Select "Library of Congress classification" browse option

  4. Fill in the browse box with the following query: "PR9199.48 .B4".

  5. Click on the "Search" button.

Expected Results:

  • Exact match result is found (should be highlighted in bold), ex.: "PR9199.48 .B4"

  • Other call numbers of created sequence from preconditions also displayed in the browse result list

Actual Results: At the last page of call numbers, non-exact match result is displayed: "PR9199.4 would be here"

See attached screencast:

URL: https://bugfest-poppy.int.aws.folio.org/inventory/browse?qindex=lc&query=PR9199.4 

Interested parties:  **

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Viacheslav Kolesnyk March 25, 2024 at 10:37 AM

MAX_BROWSE_REQUEST_OFFSET should be set >= 4085 if there’re around 5500 records with same first 9 characters in shelving order. We set MAX_BROWSE_REQUEST_OFFSET at 5000 and it worked.

Valery_Pilko March 22, 2024 at 6:32 AM

Hi
I was able to reproduce this issue on Pre-bugfest-Q environment https://folio-testing-pre-bugfest-fs09000000.ci.folio.org/ .
Could you please review it?
Here are 26 instances which have “LC” call numbers from “PR9199.48 .B10” to “PR9199.48 .B4“:
https://folio-testing-pre-bugfest-fs09000000.ci.folio.org/inventory?filters=staffSuppress.false&query=VP%20pagination

Christine Schultz-Richert December 4, 2023 at 3:42 PM

Closing as done. We will further verify for Q in MSEARCH-649

Viacheslav Kolesnyk December 1, 2023 at 2:10 PM

MAX_BROWSE_REQUEST_OFFSET was added. In order to verify we need to release it, deploy it and set MAX_BROWSE_REQUEST_OFFSET=700.

Christine Schultz-Richert November 28, 2023 at 3:36 PM

Hey - I agree with both proposals:

  • Configurable parameter for additional elasticsearch requests - even though it may slow down some other browse cases, but not the whole browse

  • Keeping the default parameter (as you mentioned, no changes on the UI or API level) that we can increase when needed

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Quesnelia (R1 2024)

RCA Group

Data related (ex. Can be detected with large dataset only)

Affected releases

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 20, 2023 at 3:47 PM
Updated May 21, 2024 at 8:25 PM
Resolved December 4, 2023 at 3:42 PM
TestRail: Cases
TestRail: Runs