Done
Details
Assignee
Michal KuklisMichal KuklisReporter
Charlotte WhittCharlotte WhittTester Assignee
Charlotte WhittCharlotte WhittPriority
P2Story Points
3Sprint
NoneDevelopment Team
ProkopovychFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Michal Kuklis
Michal KuklisReporter
Charlotte Whitt
Charlotte WhittTester Assignee
Charlotte Whitt
Charlotte WhittPriority
Story Points
3
Sprint
None
Development Team
Prokopovych
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 1, 2022 at 8:44 PM
Updated April 17, 2024 at 1:55 PM
Resolved February 16, 2022 at 10:31 AM
Overview: When searching by Call number, FOLIO allows for Call numbers to be following many Call number schemes (Call number types) and the numbers can be entered with a variety of special characters and symbols. For this first iteration we want to implement the basic search on Call numbers, normalized. Later we'll refine, so all use cases the early implementer libraries have is covered and accessible - See: https://folio-org.atlassian.net/browse/UIIN-983#icft=UIIN-983). Some initial normalization will be e.g. strip any internal punctuation like hyphens, punctuation, spaces, bracket and parenthesis no matter which version is in the Holdings call number data elements, or the Item call number elements:
Holdings record:
Use cases:
Staff at circulation desk has a book in hand with no barcode; they search for the call number in normalized form – they will want to search based on prefix / call number / suffix but will not expect to have to enter location, call number type, or copy number as those are not part of the call number
A librarian might perform a call number search to see a browse list of all numbers starting with a particular stem (e.g., everything in RM931.D63 for works about service dogs) – in this case they would want to search just the call number.
Examples on real life search - see: UIIN-857.
Search for Call number is a search option in the drop down menu in the Holdings segment and the Item segment:
Search options Holdings record
Scenarios:
Scenario
Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Holdings segment (https://folio-org.atlassian.net/browse/UIIN-758#icft=UIIN-758)
When a user wants to search on call number - whether it's Call number, eye readable, or Call number, normalized then following search options are in focus of this story:
Holdings Call number block
Call number prefix
Call number
Call number suffix
Search options are labelled:
Call number, normalized - listed after Call number, eye readable - https://folio-org.atlassian.net/browse/UIIN-858#icft=UIIN-858
Scenario
ensure following search are covered (both segments: Holdings and Item):
Call number, normalized
Scenario
Given the "Call number, normalized" search option
When used
ensure following normalizations are covered whether it's the holdings segment of the item segment: space, hyphen, period, comma, colon, slash, bracket, and parenthesis
Call number, normalized
with and without space
with and without hyphen
with and without period
with and without comma
with and without colon
with and without slash
with and without bracket
with and without parenthesis
Scenario
When search on any of the call number options (both segments: holdings and item)
Then search is left anchored
Scenario
When search on any of the call number options (both segments: holdings and item)
Then right truncation is not set as a default, but can be set explicit by the user by using *
Scenario
When search on any of the call number options (both segments: holdings and item)
Then normalization between lower casing and capitalized letters are happening
Scenario
When search on any of the call number options (both segments: holdings and item)
Then normalization by stripping whitespace are happening
Scenario
Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot