Skip to:

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

LCCN normalization for MARC authority search

Description

Overview: Search on LCCN normalized numbers is relevant in general use of metadata management and especially in the work for Library of Congress. We are aiming for covering all the typical variations of the LCCN number, e.g. specific use of prefixes and other variations. 

Requirements: 

  • For existing "LCCN" search option:

    • LCCN normalization rules:

      • Trim leading, trailing, and internal spaces

      • Case insensitive

      • Allow leading, trailing asterisks (may result in multiple matches)

      • Match with just numbers (may result in multiple matches)

    • Should search 010 $a and $z

Scenarios:

Example LCCN:    n  79021425  (two leading spaces, prefix, one trailing space, two internal spaces)

  • Scenario 1 - Exact matches

    • Given the user is searching LCCN

    • When the user enters a query that is an exact match of the LCCN (   n  79021425 )

    • Then the results should return the matching instance

  • Scenario 2 - Numbers only

    • Given the user is searching LCCN

    • When the user enters a query that does not include a prefix (79021425)

    • Then the results should return any matching instance(s)

  • Scenario 3 - Prefix and numbers with trailing asterisk

    • Given the user is searching LCCN

    • When the user enters a query that contains a trailing asterisk (n  79021*)

    • Then the results should return any matching instance(s)

  • Scenario 4 - Numbers with no prefix, but leading asterisk

    • Given the user is searching LCCN

    • When the user enters a query containing a leading asterisk (*79021425)

    • Then the results should return any matching instance(s)

  • Scenario 6 - All spaces removed

    • Given the user is searching LCCN

    • When the user enters a query that contains no spaces (n79021425)

    • Then the results should return the matching Instance

  • Scenario 7 - Leading or trailing spaces removed but internal spaces retained

    • Given the user is searching LCCN

    • When the user enters a query with no leading or trailing spaces but the query contains internal spaces (n 79021425)

    • Then the results should return the matching instance

  • Scenario 8 - case insensitivity

    • Given the user is searching LCCN

    • When the user enters a query with a capitalized letter (N79021425)

    • Then the results should return the matching instance

Environment

None

Potential Workaround

None

clones

is cloned by

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Polina Ustimenko February 27, 2024 at 4:28 PM

Verified on https://folio-snapshot-2.dev.folio.org/

See screencasts in and linked FAT tickets

could you please review? Thank you!

Denys Bohdan February 1, 2024 at 10:42 AM

Hey , since BE is blocked on searching by $z, should we move it to a separate UI story as well?

Christine Schultz-Richert December 21, 2023 at 12:03 PM

Hey - Yes, any extra spaces should be removed as well (all spaces removed)

Valery_Pilko December 21, 2023 at 8:04 AM

Hi  
Extra spaces should be removed from search query? 
For example: "n      79021425" (with extra internal spaces)

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Release

Quesnelia (R1 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created December 8, 2023 at 4:57 PM
Updated March 12, 2024 at 7:23 PM
Resolved February 27, 2024 at 4:45 PM
Configure
Loading...