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

Search. Holdings and Item segments. Search option for Call numbers, normalized - 1st phase

    XMLWordPrintable

    Details

    • Template:
    • 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, normalized. Later we'll refine, so all use cases the early implementer libraries have is covered and accessible - See: UIIN-983). Some initial normalization will be e.g. strip any internal punctuation like hyphens, punctuation, spaces, bracket and parenthesis no matter which version is in the Holdings call number data elements, or the Item call number elements:

      Holdings record:

      Item record:

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

      A librarian might perform a call number search to see a browse list of all numbers starting with a particular stem (e.g., everything in RM931.D63 for works about service dogs) – in this case they would want to search just 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 Holdings record Search options Item record

      Scenarios:

      1. Scenario
        • Login to FOLIO Snapshot, go to Inventory, Search & filter pane, and select the Holdings segment (UIIN-758)
        • 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, normalized - listed after Call number, eye readable - UIIN-858
      2. Scenario
        • go to Inventory, Search & filter pane, and select the Item segment (UIIN-758)
        • When a user wants to search on call number - whether it's Call number (all), Call number, eye readable, or Call number, normalized 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), normalized - listed after Effective call number (item), eye readable - UIIN-858
      3. Scenario
        • ensure following search are covered (both segments: Holdings and Item):
          • Call number, normalized
      4. Scenario
        • Given the "Call number, normalized" search option
        • When used
        • ensure following normalizations are covered whether it's the holdings segment of the item segment: space, hyphen, period, comma, colon, slash, bracket, and parenthesis
          • Call number, normalized
            • with and without space
            • 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
      5. Scenario
        • When search on any of the call number options (both segments: holdings and item)
        • Then search is left anchored
      6. 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 *
      7. 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
      8. Scenario
        • When search on any of the call number options (both segments: holdings and item)
        • Then normalization by stripping whitespace are happening
      9. Scenario
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases