Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Q2 2020
-
Component/s: None
-
Labels:
-
Template:customfield_11200 32898
-
Epic Link:
-
Analysis Estimate:Small < 3 days
-
Front End Estimate:Medium < 5 days
-
Back End Estimate:Medium < 5 days
-
Front-End Confidence factor:Low
-
Estimation Notes and Assumptions:
-
Development Team:Prokopovych
-
Calculated Total Rank:
-
PO Rank:125
-
PO Ranking Note:CW: Aligned PO rank with Calculated Total rank
-
Rank: Chalmers (Impl Aut 2019):R2
-
Rank: Cornell (Full Sum 2021):R1
-
Rank: Duke (Full Sum 2021):R1
-
Rank: 5Colleges (Full Jul 2021):R1
-
Rank: GBV (MVP Sum 2020):R2
-
Rank: TAMU (MVP Jan 2021):R1
Description
The elements Call number, and Call number type are implemented in the Holdings and Item records.
Use cases:
Multiple times daily catalogers and other library staff need to search by call number; system needs to search normalized version, not exact text string.
Several libraries have expressed a requirement on being able to search by normalized call number - besides search on call number as an exact string, we'd also need search where we handle removing of misc. qualifiers, and more.
Status on work being implemented in Inventory (thin thread) Q1 2020:
- Search across data elements (holdings and item):
- Call number, prefix
- Call number
- Call number, suffix
- Implemented two indexes:
- Call number, prefix
- Call number and Call number, suffix
- Search option in the Holdings segment: Call number, eye readable (with no normalization)
- outstanding un-intended behavior - story:
UIIN-1040
- outstanding un-intended behavior - story:
- Search option in the Item segment: Call number, eye readable (with no normalization)
- outstanding un-intended behavior - story:
UIIN-1041
- outstanding un-intended behavior - story:
Summary of normalization functionality:
- Search option in the Holdings segment: Call number, normalized
- Normalization between lower casing and capitalized letters
- Searching must be possible
- with and without spaces
- 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
- Search option in the Item segment: Effective Call number (item), normalized
- Normalization between lower casing and capitalized letters
- Searching must be possible
- with and without spaces
- 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
Examples in scope:
- 8 G.B.439 :6
- JUR:R III:54:(1):Schm:1850
- 94 NF 14/1:3792-3835
- Z 557: 54.1961/62,7-12
- Y 43839 (2017/18)
- 1990/146 4°
- 426/083 4° SH 34
Out of scope - to be implemented post-mvp? - UXPROD-2360:
- Wildcard for exact one character, e.g. “!” - UIIN-1043
- Search variants:
- geo 1! → geo 11 and geo 12
- geo 1!! → geo 100 and geo 123
- geo 1* → geo 11 and geo 12 and geo 100 and geo 123
- Search variants:
- Wildcard for 0-n characters, e.g. “#”
Documentation:
- Notes on call number search (p.13-17) in https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit#
TestRail: Results
Attachments
Issue Links
- has to be done before
-
UXPROD-1714 FOLIO wide search by call number for any item search functionality
-
- Open
-
- is defined by
-
MODINVSTOR-485 BE: Search. Holdings. Search option for Call numbers, normalized (first iteration)
-
- Closed
-
-
MODINVSTOR-488 BE: Search. Item segment. Search option for Effective call numbers (item), normalized (1st iteration)
-
- Closed
-
-
UIIN-857 Normalize Call numbers for Call number searching in record
-
- Closed
-
-
UIIN-983 Search. Holdings. Search option for Call numbers, normalized (first iteration)
-
- Closed
-
-
UIIN-993 Search. Item segment. Search option for Effective call numbers (item), normalized (1st iteration)
-
- Closed
-
- relates to
-
MSEARCH-169 Support normalized search for call numbers
-
- Closed
-