Authority record search - Keyword search option

Description

Purpose/Overview:

The purpose of this story is to support Authority record search by authority by keyword

Assumptions:
The story assumes that authority record is populated with following data: i

Authority field

MARC field

MARC subfields

identifiers

010

$a and $z

personalName

100

all available subfields with the exception of $6 and $8

corporateName

110

all available subfields with the exception of $6 and $8

meeting Name

111

all available subfields with the exception of $6 and $8

unifromTitle

130

all available subfields with the exception of $6 and $8

topicalTerm

150

all available subfields with the exception of $6 and $8

geographicName

151

all available subfields with the exception of $6 and $8

genre

155

All available subfields with the exception of $6 and $8

sftPersonalName

400

All available subfields with the exception of $6 and $8

sftCorporateName

410

All available subfields with the exception of $6 and $8

sftMeetingName

411

All available subfields with the exception of $6 and $8

stfUniformTitle

430 

All available subfields with the exception of $6 and $8

stfTopicalTerm

450

All available subfields with the exception of $6 and $8

stfGeograpicName

451

All available subfields with the exception of $6 and $8

stfGenre

455

All available subfields with the exception of $6 and $8

saftPersonalName

500

All available subfields with the exception of $6 and $8

saftCorporateName

510

All available subfields with the exception of $6 and $8

saftMeetingName

511

All available subfields with the exception of $6 and $8

saftUniformTitle

530

All available subfields with the exception of $6 and $8

saftTopicalTerm

550

All available subfields with the exception of $6 and $8

saftGeorgraphicName

551

All available subfields with the exception of $6 and $8

saftGenre

555

All available subfields with the exception of $6 and $8

Requirements/Scope:

  1. The search is based on the following fields from the authority record:

    • identifiers LCCN - todo: should other identifier be included as well?

    • personalName

    • corporateName

    • meeting Name

    • unifromTitle

    • topicalTerm

    • geographicName

    • genre

    • sftPersonalName

    • sftCorporateName

    • sftMeetingName

    • stfUniformTitle

    • stfTopicalTerm

    • stfGeograpicName

    • stfGenre

    • saftPersonalName

    • saftCorporateName

    • saftMeetingName

    • saftUniformTitle

    • saftTopicalTerm

    • saftGeorgraphicName

    • saftGenre

  2. The search supports:

    • Phrase search

    • Exact phrase search

    • Left anchored search (or right truncation)

    • Boolean operators

  3. Response contains elements:

    • Authority/Reference as described in MSEARCH-212

    • Heading/Reference as described in MSEARCH-211

    • Type of heading as described in MSEARCH-210

Approach:

Acceptance criteria:

  • Search is based on specified field

  • Search supports required search types

  • Response contains required elements

Environment

None

Potential Workaround

None

Attachments

9

Checklist

hide

TestRail: Results

Activity

Show:

Shans Kaluhin December 15, 2021 at 12:46 PM

, Query example for searching:

Khalilah Gambrell December 10, 2021 at 8:06 PM

and , do you know the identifier query string that should use?

Denys Bohdan December 10, 2021 at 5:05 PM

what are the updates to the identifier query string that we need to make?

Khalilah Gambrell December 10, 2021 at 4:00 PM
Edited

Per Falcon meeting

  • , we need to update the identifier query string

  • and I need to discuss with Spitfire how to normalize 010 $a and $z values upon importing/editing record

Khalilah Gambrell December 9, 2021 at 11:30 PM

and , I cannot figure out how to search this field: identifiers > 010 $a and $z

Thoughts?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Falcon

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 17, 2021 at 10:49 PM
Updated February 18, 2022 at 5:59 PM
Resolved December 10, 2021 at 4:02 PM
Loading...