Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-990

Search. Item. Search option for Call numbers, eye readable (thin thread)

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: F - Sprint 83
    • Story Points:
      5
    • Development Team:
      Prokopovych

      Description

      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 super lightweight normalization: lowercasing (search not being case-sensitive and the user do not need to differentiating between capital and lower-case letters).

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

      Search options Item record

      Scenarios:

      1. Scenario
        • Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Item segment (UIIN-761)
        • When a user wants to search on Call number, eye readable then following search options are in focus of this story:
        • 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 - UIIN-985
      2. Scenario
        • When search on the Effective call number (item), eye readable
        • Then search is left anchored
      3. Scenario
        • When search on the Effective call number (item), eye readable
        • Then right truncation is not set as a default, but can be set explicit by the user by using *
      4. Scenario
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      Out of scope for this thin thread story:
      When search on on the call number, eye readable:

      • Then normalization between lower casing and capitalized letters are happening
      • Then normalization by stripping whitespace are happening

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                mpk35 Michal Kuklis
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases