Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

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

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, 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).

Holdings record:

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:

Search options Holdings record

 

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, eye readable 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

    • When search on any of the call number, eye readable

    • Then search is left anchored

  3. Scenario

    • When search on any of the call number, 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:
When search on any of the call number, eye readable:

  • Then normalization between lower casing and capitalized letters are happening

  • Then normalization by stripping whitespace are happening

Environment

None

Potential Workaround

None

Attachments

10

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte WhittMarch 5, 2020 at 12:42 PM
Edited

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

I did misc. test:
Following works as expected:

That all looks perfect .

But if I search only on the value in the holdings call number data element: R11.A38 and there is call number (R11.A38) with suffix (Test), then I get no results, unless I do a right truncation using wildcard *

- I'll close the story as done, and will file a bug re. the possibility to search eye readable on the value in the call number element without having to set a wild card truncation to suppress for the suffix data.
I do understand that this behavior comes from:

  1. Scenario

    • When search on the Call number, eye readable

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

But for a user - this behavior does seem to be confusing, when you search only in the call number data element. I'll ask around to get feedback from more SMEs

Cate BoeremaFebruary 24, 2020 at 9:12 AM

Just adding Core: Functional as the dev team. Without the dev team assigned, it doesn't show on the scrum board (and won't get pulled into a sprint)

Charlotte WhittNovember 12, 2019 at 1:51 PM

- the effective call numer is constructed data.
And I'm not sure this is what the SMEs expect to search on. But I'll loop in the SMEs who have reviewed these stories (, and )

Cate BoeremaNovember 12, 2019 at 1:48 PM

Thanks! One follow-up:

You said "yes" to my queston #2 but then included this screenshot:

That screenshot highlights the item call number data, not the item effective call number data. These are quite different. We don't yet display the item effective call number data on the item record, but will when we complete: and .

Charlotte WhittNovember 12, 2019 at 12:43 PM
Edited

Hi

Re. 1 and 2 - then Yes -
See:

Yes, I'll talk with Jakub, how he want the story/stories - 6 stories sounds a bit overkill to me

Re. Item effective call number (keyword) - then I'll double check with the SMEs.

Re. scenario 4, then call number normalizations, is only expected for when the user use "Call number, normalized"

See also examples in (task)

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 8, 2019 at 11:39 AM
Updated April 17, 2024 at 1:55 PM
Resolved March 5, 2020 at 12:43 PM
TestRail: Cases
TestRail: Runs