Overview: What we are aiming for is basic normalization, which will be adequate for most call number types and most library staff. Call number search in Inventory covers search option on call numbers, normalized in the Holdings segment, so usecases which the early implementer libraries have listed are covered and searchable (). This work will not include the possibility to do mask of single characters - , or do normalization of special symbols like e.g. degree symbol (post-mvp). Search on Call number, normalized will be across following three data elements:

• Call number prefix

• Call number

• Call number suffix

Use cases:

1. Staff at circulation desk has a book in hand with no barcode; they search for the call number – 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 Call number 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 holdings records exist

# Scenario

•  

  • Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Holdings segment ()

  • When the search options menu is opened

  • Then a new "Call number, normalized" option should display:
    

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

2. Scenario

   • Given the Call number, normalized

   • When a search term is entered

   • Then search is left anchored meaning instances containing the following holdings 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|1990/146 4°| |

3. Scenario

   • Given the Call number, normalized

   • When a search term is entered

   • Then right truncation is set as a default, meaning instances containing the following holdings 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° | |

4. Scenario

   • When search on Call number, normalized

   • Then normalization between lower casing and capitalized letters is happening

5. Scenario

   • When search on Call number, normalized

   • Then normalization by stripping whitespace is happening

6. Scenario

   • When search on Call number, normalized

   • Then normalization by stripping hypen is happening

7. Scenario-

   • When search on Call number, normalized

   • Then normalization by stripping period is happening

8. Scenario

   • When search on Call number, normalized

   • Then normalization by stripping comma is happening

9. Scenario

   • When search on Call number, normalized

   • Then normalization by stripping colon is happening

10. Scenario

    • When search on Call number, normalized

    • Then normalization by stripping slash is happening

11. Scenario

    • When search on Call number, normalized

    • Then normalization by stripping bracket is happening-

12. Scenario

    • When search on Call number, normalized

    • Then normalization by stripping parenthesis is happening

13. 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|

14. 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 - .