Inventory (UXPROD-785)

[UXPROD-2264] Inventory. Search call number, normalized (Core functional) Created: 12/Feb/20  Updated: 16/Sep/21  Resolved: 19/May/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2020
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: call_number, inventory, metadatamanagement, po-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2019-12-04 kl. 14.46.11.png     PNG File Skärmavbild 2019-12-04 kl. 14.48.42.png    
Issue links:
Defines
is defined by MODINVSTOR-485 BE: Search. Holdings. Search option f... Closed
is defined by MODINVSTOR-488 BE: Search. Item segment. Search opti... Closed
is defined by UIIN-857 Normalize Call numbers for Call numbe... Closed
is defined by UIIN-983 Search. Holdings. Search option for C... Closed
is defined by UIIN-993 Search. Item segment. Search option f... Closed
Gantt End to Start
has to be done before UXPROD-1714 FOLIO wide search by call number for ... Open
Relates
relates to MSEARCH-169 Support normalized search for call nu... Closed
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Medium < 5 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Niels Erik Nielsen
Estimation Notes and Assumptions: Outstanding questions:
* Implemented as a search index or as a persisted field containing the normalized version of the call number?
* Hard-code normalization rules or configurable?
Development Team: Prokopovych
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:

  1. Search across data elements (holdings and item):
    • Call number, prefix
    • Call number
    • Call number, suffix
  2. Implemented two indexes:
    • Call number, prefix
    • Call number and Call number, suffix
  3. Search option in the Holdings segment: Call number, eye readable (with no normalization)
    1. outstanding un-intended behavior - story: UIIN-1040 Closed
  4. Search option in the Item segment: Call number, eye readable (with no normalization)
    1. outstanding un-intended behavior - story: UIIN-1041 Closed

Summary of normalization functionality:

  1. 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
  2. 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:

  1. Wildcard for exact one character, e.g. “!” - UIIN-1043 Closed
    • 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
  2. Wildcard for 0-n characters, e.g. “#”

Documentation:



 Comments   
Comment by Cate Boerema (Inactive) [ 12/Feb/20 ]

Hi Charlotte Whitt, it looks like this feature was just created and added to Q1? It's not possible to add new features to the quarter at this point unless we remove something of equal size.

Comment by Charlotte Whitt [ 25/Mar/20 ]

Hi Marc Johnson and Zak Burke - I need your help with estimating this feature.
Cate has asked for the estimates to be ready by EOD Friday (3/27/2020).

In your estimates then please include that we probably will need to add another index - so it's possible to do:

  1. search left anchored - sometimes start with the prefix
  2. search left anchored - start with call number (include) suffix
  3. search only on the 'call number' data element
Comment by Marc Johnson [ 25/Mar/20 ]

Jakub Skoczen Can you help out with the estimation. I think we will need 3 indexes, each for holdings and items.

What I'm unclear about is how much development will be needed to achieve the normalization for these indexes?

Comment by Cate Boerema (Inactive) [ 14/May/20 ]

Hi Charlotte Whitt. When you are done testing the two In review issues, can you please mark this feature done? Thanks

Generated at Fri Feb 09 00:22:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.