Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Call-number browsing fails when value match shelfKey pattern

Description

Call-number browsing fails when value match shelfKey pattern
For example we have a call-number with value "A 11" and it generated shelfKey is "A 211"
So while browsing, call-number value matches shelfKey pattern and browsing by "A 11"
But it's not a shelfKey and record can't be founded.

Approach
Separate call-number search and shelfKey search

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

8

Checklist

hide

TestRail: Results

Activity

Show:

Valery_Pilko August 19, 2022 at 8:53 AM

Verified at MG Bugfest environment - works as expected.
See attached screencast:

Oleksii Petrenko August 17, 2022 at 10:24 AM

Deployed to MG bf environment. Please proceed with verification

Magda Zacharska August 16, 2022 at 12:17 PM

You're absolutely right, - I missed that. Thanks for clarifying it.

Shans Kaluhin August 16, 2022 at 8:48 AM

It happens because, item on snapshot have:

Enumeration= "v. 30 1961" and copy-number = "c.1"

Add this values to Lotus item and you will get the same result.
My changes not affect this, so we should create another ticket to display full Effective call number string instead of just call-number.

Shans Kaluhin August 16, 2022 at 8:15 AM

This two items have different call-numbers

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Morning Glory (R2 2022) Bug Fix

RCA Group

Institution specific (Unexpected usage scenario)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 2, 2022 at 12:32 PM
Updated May 21, 2024 at 8:25 PM
Resolved August 16, 2022 at 12:18 PM
TestRail: Cases
TestRail: Runs