STORY: Authority search

Description

This card continues to support cataloger workflow around assigning authorities in the Work entity edit mode.

Following Refinement on July 17, we decided to split this card into two smaller cards: the first will cover only the search screen in the modal and the second will cover the search results screen in the modal. There are only two sprints (196 and 197, July 22 - August 16) before Citation freezes development for the Beta release (Sept 2 - 6). Splitting the cards allows the team to spread work over the remaining two sprints.

Scope

  • Search modal

  • Search results

Out of scope

  • Display of full authority resource

  • Filters

  • Changes to resource description in edit mode

Search

When a cataloger needs to assign a new authority to a resource description - for either a new or existing resource - they’ll do so by searching for an authority through the authority search screen, which will be displayed as a modal hovering over the resource description.

The modal has similar properties to the bibliographic search feature in the Linked Data Editor

  • Simple input box

  • Search button

  • Section for displaying search results

  • Exit icon ('X' in upper left of modal)

  • Filters (outside scope of this card, but illustrated in design below)

Search results

The cataloger conducts a query by entering search terms and selecting the ‘Search’ button. Result set presented within the modal with the following properties:

  • Search box still displayed with search terms (and, eventually, filters / limiters still displayed)

  • Table listing matches on the search query

  • Table will list additional properties of the authority resource

  • An ‘Assign’ button for assigning an authority to the resource

  • (Same) exit icon

When the cataloger selects a resource from the list, the modal closes and the value selected is displayed in the appropriate component of the Work entity. The corresponding Subclass will also be populated in the Work entity.

The cataloger can always elect to change the authority by clicking the ‘Change authority’ link in edit mode.

If the cataloger selects the exit icon, the modal closes and the cataloger returns to the resource description in Work entity edit mode, with no changes applied to the authority field.

NOTE: The design shows hyperlinks for headings. That is out of scope for Beta, but will be added after Beta. Also for Beta, we will show only the LCCN number itself, not the URI to id.loc.gov. That hyperlink can follow Beta (if needed).

Environment

None

Potential Workaround

None

Attachments

6

is defined by

Checklist

hide

Activity

Show:

Doug Loynes August 2, 2024 at 10:00 PM

Will close this card and add a small clean up card for design details that should be amended.

Tetiana Kovalchuk August 2, 2024 at 9:53 AM

Tested on qld env.

Build version: #316

Test cases and evidences attached.

Tetiana Kovalchuk August 1, 2024 at 7:43 AM

  1. Modal window is opened under the header

  2. Main label should be bold

Siarhei Karol August 1, 2024 at 6:59 AM


Regression testing is needed for:

  1. Search - basic and advanced;

  2. Pagination;

  3. Back to search results.

Doug Loynes July 30, 2024 at 1:54 PM

  1. Saving Work resource with assigned authority record? No, outside of scope. That will be addressed in UILD-347

  2. How should the search work? Shall the user be able to search by heading only, part of heading value, full heading value? We will support ‘left-anchored searching’ - but that will be addressed in the next ticket.

  3. What mapping should be used for data in the search results table? Search results will be covered in the next ticket.

  4. Shall the search results and query be preserved when closing and re-opening the Search modal? Don’t think so. This is a thin thread only.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Citation

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 16, 2024 at 11:46 PM
Updated August 26, 2024 at 2:42 PM
Resolved August 2, 2024 at 10:00 PM
TestRail: Cases
TestRail: Runs