ECS | "totalRecords" returns 0 for most call numbers in result list when location from another tenant is selected

Description

Overview: “Non-exact match” placeholders display instead of call numbers when user selects location from another member tenant in “Effective location (item)” facet during call number browsing from member tenant.

"totalRecords" returns 0 for most call numbers in response of GET “/browse/call-numbers/all/instances”

Steps to reproduce:

  1. Authorize as admin user on Eureka ECS sprint testing environment https://folio-etesting-sprint-cs00000int.ci.folio.org/

  2. Switch active affiliation to “Colleague” tenant

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

  4. Select “Call numbers (all)” browse option

  5. Browse for any call number value

  6. Expand “Effective location (item)” facet

  7. Select “location” from another member tenant, ex.: “Migration (Professional tenant)”

Expected result: Browse result list updates accordingly to selected “location”. Only 1 non-exact match placeholder displays.
Actual result: “Non-exact match” placeholders display instead of call numbers on UI.
"totalRecords" returns 0 for most call numbers in response of GET “/browse/call-numbers/all/instances”

See attached screenshots:

image-20250225-105351.png
image-20250225-105425.png

UPDATE:
Steps to reproduce (on clear environment):

  1. Create following test data on testing environment:
    - Local Instance A (with selected Location A and call number X) on Member 1 tenant
    - Local Instance B (with selected Location B and call number X) on Member 2 tenant
    NOTE: “Call number” values must be the same for both created Local instances.

  2. Go to “Inventory” >> “Browse” on Member 1

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

  4. Browse for created call number value using non-exact match query

  5. Expand “Effective location (item)” facet

  6. Select “location” from another member tenant, ex.: “Location B”

Expected result: Browse result list updates accordingly to selected “location B”. Only 1 non-exact match placeholder displays.
Actual result: “Non-exact match” placeholders display for each call number which have the same values on both member tenants and belong to Local instances.

See attached screenshots:

image-20250304-105301.png
image-20250304-105323.png

CSP Request Details

Requested 3/18/25

CSP Rejection Details

None

Potential Workaround

None

Attachments

7
  • 26 Mar 2025, 10:55 AM
  • 12 Mar 2025, 05:10 PM
  • 12 Mar 2025, 05:10 PM
  • 04 Mar 2025, 10:57 AM
  • 04 Mar 2025, 10:57 AM
  • 25 Feb 2025, 10:54 AM
  • 25 Feb 2025, 10:54 AM

Checklist

hide

Activity

Show:

Valery_Pilko 18 hours ago

Verified on Okapi ECS Ramsons Bugfest environment - fixed

image-20250326-105317.png

I’m closing this issue.
cc:

Valery_Pilko March 12, 2025 at 5:10 PM

Verified on Eureka Sprint testing environment (Sunflower) - issue from description is fixed
See attached screenshots:

image-20250312-143635.png
image-20250312-150352.png

Following issues found (maybe it’s the same root cause):

https://folio-org.atlassian.net/browse/MSEARCH-994
https://folio-org.atlassian.net/browse/MSEARCH-995

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Spitfire

Fix versions

Release

Ramsons (R2 2024) Service Patch #1

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 25, 2025 at 10:53 AM
Updated 18 hours ago
Resolved March 18, 2025 at 8:26 AM
TestRail: Cases
TestRail: Runs

Flag notifications