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