BE: Search. Item segment. Search option for Effective call numbers (item), normalized (1st iteration)

Overview: What we are aiming for is basic normalization, which will be adequate for most call number types and most library staff. Search for Effective call number (item), normalized is a search option in the drop down menu in the Item segment. The search will cover usecases which the early implementer libraries have listed (UIIN-857). This work will not include the possibility to do mask of single characters - UIIN-1043, or do normalization of special symbols like e.g. degree symbol (post-mvp).
Search on Effective Call number (item), normalized will be across following three data elements:

• Effective call number prefix
• Effective call number
• Effective call number suffix

Use cases:

1. Staff at circulation desk has a book in hand with no barcode; they search for the Effective call number (item) 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
2. A cataloger is assigning a call number and needs to search for the Effective call number (item) they propose assigning. They search for "rm931d63" to return everything about service dogs or "rm931 d63 h84" to check if that exact number has been used (these examples both require implicit truncation). An example call number that would be retrieved by both searches is RM931.D63 H84 2015.
3. More examples gathered in following spread sheet - 1st tab: https://docs.google.com/spreadsheets/d/1Yi4jhnqv9MytlyR-xahTfijWbM8JMomAyW7Q9PpqRt0/edit#gid=0

Scenarios:
Assume the following item records exist

1. Scenario
   • Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Item segment (UIIN-761)
   • When the search options menu is opened
   • Then a new "Effective call number (item), normalized" option should display:
   • 
2. Scenario NEW scenario since 4/24
   • Given the Call number, normalized
   • When a search term is entered
   • Then search is alphanumeric meaning the search will ignore all punctuation and special characters, except asterisk which is used as truncation symbol.
3. Scenario
   • Given the Effective call number (item), normalized
   • When a search term is entered
   • Then search is left anchored meaning instances containing the following items are expected:

     Search	Expected result	Note
     8 GB439 6	8 G.B.439 :6	search starting with Call number
     germ 350/35 1	H Germ 350/35: 1	search starting with Call number
     ABC123.1 R15 2018	Oversize ABC123.1 .R15 2018	search starting with Call number
     Z2557.D57	A.D. White, Icelandic Z2557 .D57	search starting with Call number and catch also the prefix call number
     94 NF 14 1 3792-3835	94 NF 14/1:3792-3835	search starting with Call number
     Icelandic Z2557 D57	no results	the search start in the middle of the Call number prefix
     1990/146 4	1990/146 4°

4. Scenario
   • Given the Effective call number (item), normalized
   • When a search term is entered
   • Then right truncation is set as a default, meaning instances containing the following item records are expected:

     Search	Expected result	Note
     8 GB439	8 G.B.439 :6	truncation within the Call number data element, and potential call number suffix
     h germ 350/35	H Germ 350/35: 1	search starting with prefix call number, right truncation within the call number, and potential call number suffix
     JUR R III 54 (1) Schm	JUR:R III:54:(1):Schm:1850	right truncation within the Call number data element, and potential call number suffix
     94 NF 14 1 3792	94 NF 14/1:3792-3835	right truncation within the Call number data element, and potential call number suffix
     S537.N56 C82	Rare Books S537.N56 C82++	right truncation catch the call number suffix
     1990/146 4	1990/146 4°

5. Scenario
   • When search on the Effective call number (item), normalized
   • Then normalization between lower casing and capitalized letters are happening
6. Scenario
   • When search on any the Effective call number (item), normalized
   • Then normalization by stripping whitespace are happening
7. Scenario
   • When search on the "Effective call number (item), normalized" search option
   • Then normalization by stripping hypen is happening
8. Scenario
   • When search on the "Effective call number (item), normalized" search option
   • Then normalization by stripping period is happening
9. Scenario
   • When search on the "Effective call number (item), normalized" search option
   • Then normalization by stripping comma is happening
10. Scenario
    • When search on the "Effective call number (item), normalized" search option
    • Then normalization by stripping colon is happening
11. Scenario
    • When search on the "Effective call number (item), normalized" search option
    • Then normalization by stripping slash is happening
12. Scenario
    • When search on the "Effective call number (item), normalized" search option
    • Then normalization by stripping bracket is happening
13. Scenario
    • When search on the "Effective call number (item), normalized" search option
    • Then normalization by stripping parenthesis is happening
14. Scenario
    • When a user wants to search on Call number, normalized then following search options are possible in normalized form:

      Search	Expected result
      8 gb439 6	8 G.B.439 :6
      jur r III 54 (1) Schm 1850	JUR:R III:54:(1):Schm:1850

15. Scenario
    • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

Out of scope - for now:
This work will not include the possibility to do mask of single characters - UIIN-1043

==============================

More examples on call numbers - see: UIIN-857.