Call numbers of other types are displayed when user goes to another page with browse results

Description

Overview: Call numbers of other types are displayed when user goes to another page with browse results
Preconditions:
1. Create (at least) 7 Instances.
2. Add Holdings with specified call number types to each created Instance, according to following table:

Instance

Dewey

LC

NLM

SuDoc

Other scheme

Local

Folio, ex.: "MOYS

Instance 1

331.042

PR9199.3 1920 .L33 1475 .A6

QS 11 .GA1 E53 2005

L37.2:Oc1/2/conversion

FIC WAL

Local1

Folio1

Instance 2

331.01

PQ2678.K26 P54

QS 11 .GA1 E53 2006

L37.s:Oc1/2/991

B WASHINGTON

Local2

Folio2

Instance 3

331.016

PQ8550.21.R57 V5 1992

QS 11 .GA1 F875d 1999

Y4.F76/2:Af8/12

FIC CLE

Local3

Folio3

Instance 4

331.1

PQ8550.21.R57 V5

QS 11 .GA1 Q6 2013

T23.19/2:P94/2

B JORDAN

Local4

Folio4

Instance 5

331.041

PR919 .L33 1990

QS 11 .GA1 Q6 2012

T22.19/2:P94

SC BRU

Local5

Folio5

Instance 6

331.198

PR9199 .A39

QS 11 .GI8 P235s 2006

L36.202:F15/990

SC VIV

Local6

Folio6

Instance 7

331.0413

PR9199.48 .B3

QS 124 B811m 1875

J29.2:D84/982

DVD F GON

Local7

Folio7

3. Add an Item to each created Holdings.

4. Log into Snapshot FOLIO environment as User with following permission: Inventory: All permissions
5. Go to "Inventory" >> "Browse"

 

Steps to Reproduce:

  1. Select "Library of Congress classification" (or any other browse option for which call numbers were created)

  2. Enter a browse query, which will return the end of the list with created call numbers, ex.: "xx"

  3. Click on the "Search" button

  4. Click on the "Previous" pagination button

Expected Results: Only call numbers with appropriate call number type are displayed on the previous page, ex.: only "Library of Congress classification".

Actual Results: Call numbers with other call number types (not like selected browse option) are displayed on the previous page, ex.: "Dewey", "Other scheme", "SuDoc", "Local", "Folio".

Additional Information:
1) Issue doesn't reproduce when user doesn't use pagination button
1) Issue doesn't reproduce when user browse using "Dewey Decimal classification" browse option
2) Issue reproduces when user browse using following browse options:

  •  Library of Congress classification;

  • National Library of Medicine classification;

  • Other scheme;

  • Superintendent of Documents classification;

  • Local;

See attached screencast:

Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4
  • 30 Oct 2023, 08:51 AM
  • 30 Oct 2023, 08:51 AM
  • 24 Oct 2023, 05:15 PM
  • 19 Oct 2023, 07:32 AM

Checklist

hide

TestRail: Results

Activity

Show:

Yauhen ViazauOctober 31, 2023 at 1:17 PM

Viacheslav KolesnykOctober 31, 2023 at 10:25 AM

 

1) Separate issue should be created. Could be reproduced on a snapshot, steps:.

  • Add holding to instance

  • Add item with cn type "Dewey" and cn value "968.9707" to holding

  • Add item without any cn/cn type to the same instance/holding (this what causes the problem)

  • Browse for "Dewey" with value "968.9707" - 500 status from a mod-search

2) Sounds similar to https://folio-org.atlassian.net/browse/MSEARCH-613#icft=MSEARCH-613 where typed call number browse by one letter issue is descibed

Yauhen ViazauOctober 30, 2023 at 8:58 AM

Tested on https://bugfest-poppy.int.aws.folio.org/ - issue found Warning

When browsing with a query for some of the existing call numbers of Dewey, SuDoc types using appropriate call number type browse option, no results are shown (ex.: "968.9707" for Dewey, "Y4.J89/1:118-13" for SuDoc)

Browsing with Dewey, SuDoc types browse option also yields not results when query is a letter or arbitrary string of text ("a", "b", "bbb", "asdasf", etc.)

See attached screencasts:

  •  

This issue was not reproduced on Snapshot

- please review

Oleksii PetrenkoOctober 28, 2023 at 9:56 AM

Deployed to Poppy bf ebv. Please proceed with verification

Valery_PilkoOctober 24, 2023 at 5:19 PM

Verified on Snapshot-2 environment - the issue was fixed.
See attached screencast:

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Poppy (R2 2023) Bug Fix

RCA Group

Implementation coding issue

Affected releases

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 19, 2023 at 7:25 AM
Updated May 21, 2024 at 8:25 PM
Resolved October 31, 2023 at 1:18 PM
TestRail: Cases
TestRail: Runs

Flag notifications