Overview: When searching by Call number, FOLIO allows for Call numbers to be following many Call number schemes (Call number types) and the numbers can be entered with a variety of special characters and symbols. For this first iteration we want to implement the basic search on Call numbers, eye readable.
When searching the call number, eye readable, you search exactly as data is populate in the data element; except some light weight normalization: normalization of white space, and not being case-sensitive (the user do not need to differentiating between capital and lower-case letters).

Holdings record:

Item record:

Use cases:
Staff at circulation desk has a book in hand with no barcode; they search for the call number, eye readable – 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

Examples on real life search - see: UIIN-857.

Search for Call number is a search option in the drop down menu in the Holdings segment and the Item segment:

Scenarios:

1. Scenario

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

   • When a user wants to search on call number - whether it's Call number, eye readable, or Call number, normalized then following search options are in focus of this story:

     • Holdings Call number block

       • Call number prefix

       • Call number

       • Call number suffix

     • Search options are labelled:

       • Call number, eye readable - listed after Accession number, and before Call number, normalized -
         

2. Scenario

   • go to Inventory, Search & filter pane, and select the Item segment ()

   • When a user wants to search Call number, eye readable, then following search options are in focus of this story:

     • Item Call number block

       • Effective call number prefix

       • Effective call number

       • Effective call number suffix

     • Search options are labelled:

       • Effective call number (item), eye readable - listed after ISSN, and before Effective call number (item), normalized -
         

3. Scenario

   • ensure following search are covered (both segments: Holdings and Item):

     • Call number, eye readable - use cql relation: adj (substring phrase match: all words of the query string exist consecutively in that order)

4. Scenario

   • When search on any of the call number options (both segments: holdings and item)

   • Then search is left anchored

5. Scenario

   • When search on any of the call number options (both segments: holdings and item)

   • Then right truncation is not set as a default, but can be set explicit by the user by using *

6. Scenario

   • When search on any of the call number options (both segments: holdings and item)

   • Then normalization between lower casing and capitalized letters are happening

7. Scenario

   • When search on any of the call number options (both segments: holdings and item)

   • Then normalization by stripping whitespace are happening

8. Scenario

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