Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P2
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 19.3.0
-
Template:customfield_11100 35014
-
Sprint:Core: F - Sprint 93
-
Story Points:5
-
Development Team:Prokopovych
Description
Overview: When we implemented search on the Call number, eye readable, then right truncation is not set as a default - UIIN-858, but can be set explicit by the user by using *
But that has lead to unintended behavior, which for a user seems confusing: When you search only on data in the call number data element, then you don't get all the expected results, if you do not use the right truncation. This unwanted behavior has been confirmed by MM-SIG SMEs.
Scenarios
Assume two instance records with following holdings records exist
| Example | Concatenated call number | Call number prefix | Call number | Call number suffix |
|---|---|---|---|---|
| 1 | GE77 .F73 2014 | GE77 .F73 2014 | ||
| 2 | GE77 .F73 2014 Curriculum Materials Collection | GE77 .F73 2014 | Curriculum Materials Collection |
- Scenario
- Login to FOLIO Snapshot, go to Inventory
- When searching in the Holdings segment, using the search option Call number, eye readable,
- and enter in the search box: GE77 .F73 2014 (with no asterisk)
- Then both instance records will be found
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-1040
Holdings record. Call number, eye readable. Search on exact data in Call number data element
-
- Closed
-
- defines
-
UXPROD-2298 Q2 2020 Timebox for Priority Inventory Search and Filter Enhancements
-
- Closed
-
-
-
- Closed
-
- relates to
-
MODINVSTOR-481
Item record. Effective call number (item), eye readable. Search on exact data in Call number data element
-
- Closed
-
-
UIIN-1041
Item record. Effective call number (item), eye readable. Search on exact data in Call number data element
-
- Closed
-