Won't Do
Details
Assignee
UnassignedUnassignedReporter
Christine Schultz-RichertChristine Schultz-RichertLabels
Priority
P3Development Team
SpitfireRelease
Quesnelia (R1 2024)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Christine Schultz-Richert
Christine Schultz-RichertLabels
Priority
Development Team
Spitfire
Release
Quesnelia (R1 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 9, 2024 at 3:53 PM
Updated January 10, 2024 at 1:35 PM
Resolved January 10, 2024 at 1:34 PM
Purpose: The goal of this story is to support using Keyword search to retrieve authority records in which the 010 $a/$z contain values that end with a backslash.
Requirements:
When the authority record 010 $a/$z contain a value that ends in the backslash, entering the query in Keyword search with the backslash should retrieve the record
When the authority record 010 $a/$z contain a value that ends in the backslash, entering the query AND replacing the backslash with a wildcard/asterisk in Keyword search with the backslash should retrieve the record
Scenarios:
Scenario 1: No spaces in the 010 $a/$z contents
Given the 010 $a/$z in the authority record contains an LCCN with no spaces (such as n79021425) but has a trailing backslash
When the user enters the exact match in the Keyword search option
Then the search results should contain the matching authority record
Scenario 2: Spaces in the 010 $a/$z contents
Given the 010 $a/$z in the authority record contains an LCCN with spaces (such as n 79021425) but has a trailing backslash
When the user enters the exact match in the Keyword search option
Then the search results should contain the matching authority record
Scenario 3: No spaces in the 010 $a/$z contents, trailing backslash replace with wildcard asterisk
Given the 010 $a/$z in the authority record contains an LCCN with no spaces (such as n79021425) but has a trailing backslash
When the user enters a query in the Keyword search option and replaces the trailing backslash with a wildcard/asterisk
Then the search results should contain the matching authority record
Scenario 4: Spaces in the 010 $a/$z contents, trailing backslash replace with wildcard asterisk
Given the 010 $a/$z in the authority record contains an LCCN with spaces (such as n 79021425) but has a trailing backslash
When the user enters a query in the Keyword search option and replaces the trailing backslash with a wildcard/asterisk
Then the search results should contain the matching authority record