Use "itemFullCallNumbers" when navigation from call number browse to search

Description

Overview:
During testing of Call number browse refactor on https://folio-etesting-sprint-fs09000000.ci.folio.org/ we found that using “itemNormalizedCallNumbers” as search field return more Instances (Titles) than expected to the search result list during switching from call number browse to search.

Steps to reproduce

  1. Authorize as admin on https://folio-etesting-sprint-fs09000000.ci.folio.org/

  2. Go to “Inventory” >> “Browse”

  3. Select “Call numbers (all)" browse option

  4. Browse for “TF1 1” call number

  5. Click on the exact match result which has “1” in “Number of titles” column

     

Expected result: Same number of Instances as specified in “Number of titles” column are found.
Actual result: More Instances are found than specified in “Number of titles” column.

Instances with following call numbers are found:
- TF113.A3W38 2002
- TF1 195
- TF1 122

 

Another example: QR1.C66

 

Additional information:
When I’ve used "itemFullCallNumbers" instead of “itemNormalizedCallNumbers” this issues is not reproduced. So, I suggest use it.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

Activity

Show:

Valery_Pilko February 19, 2025 at 3:23 PM

Verified on Eureka Sprint testing - works as expected.
See attached screenshot:

Pavlo Smahin February 14, 2025 at 8:56 AM

Hey , you are right itemFullCallNumbers usage has more sense.
itemNormalizedCallNumbers use right truncation during search while itemFullCallNumbersdo exact match.

Valery_Pilko February 13, 2025 at 4:30 PM

Hey
Could you please review this?
Are there any cons of using “itemFullCallNumbers” instead of “itemNormalizedCallNumbers”?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Sunflower (R1 2025)

RCA Group

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

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 13, 2025 at 4:27 PM
Updated March 14, 2025 at 3:02 PM
Resolved February 19, 2025 at 8:48 PM
TestRail: Cases
TestRail: Runs