Search. Holdings segments. Search option for Call number, normalized (Elasticsearch)

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

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: https://folio-org.atlassian.net/browse/UIIN-983#icft=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:

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

Scenarios:

  1. Scenario

  2. Scenario

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

      • Call number, normalized

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

  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

Environment

None

Potential Workaround

None

Attachments

9
  • 16 Feb 2022, 10:30 AM
  • 14 Feb 2022, 01:31 PM
  • 14 Feb 2022, 01:23 PM
  • 01 Feb 2022, 08:44 PM
  • 01 Feb 2022, 08:44 PM
  • 01 Feb 2022, 08:44 PM
  • 01 Feb 2022, 08:44 PM
  • 01 Feb 2022, 08:44 PM
  • 01 Feb 2022, 08:44 PM

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte WhittFebruary 16, 2022 at 10:30 AM

Manual test in FOLIO Snapshot version @folio/inventory 9.0.100000831, using Chrome.

All looks great . I'll close the ticket as done.

Michal KuklisFebruary 14, 2022 at 2:10 PM

 thanks for catching this. I will fix it soon.

Charlotte WhittFebruary 14, 2022 at 1:33 PM
Edited

Manual test in FOLIO Snapshot version @folio/inventory 9.0.100000809 and Search Module (mod-search-1.6.0-SNAPSHOT.202), using Chrome.

When testing this, then I notice that the label in the drop down menu, is just called : Call number. This is to be labelled: Call number, normalized - as we did in Juniper (using PostgreSQL)

Juniper

FOLIO Snapshot

 

I tested the functionality, and to me it looks fine (https://folio-org.atlassian.net/browse/MSEARCH-169#icft=MSEARCH-169) - test using misc. normalized variations of PR6056.I4588 B749 2016.
But thorough test during Bugfest, might show further SME requirements for enhancement of https://folio-org.atlassian.net/browse/MSEARCH-169#icft=MSEARCH-169.

I'll put the ticket back In progress, so we can get the search option re-labelled as Call number, normalized

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 1, 2022 at 8:44 PM
Updated April 17, 2024 at 1:55 PM
Resolved February 16, 2022 at 10:31 AM
TestRail: Cases
TestRail: Runs

Flag notifications