Search details for the "view all" log screen

CSP Rejection Details

None

CSP Request Details

None

CSP Approved

None

Description

Purpose: To create the search details of the "view all" log screen

As a staff person
I want to be able to search within the Data Import logs
So that I can find particular ones that are of interest

NOTE: Moved searches for individual records within files to

Scenarios

  1. Scenario 1

    • Given the Data Import "View all" log screen

    • When the user views the search options in the search and filter pane

    • Then the cursor/focus should start in the search box

    • And they should see these options in a dropdown list

      • Keyword (Import ID, File name) [this is the default]

      • ID

      • File name

  2. Scenario 2

    • Given the Keyword search option

    • When the user selects that option

    • Then display log list results based on string matches of the Import ID number and the file name

    • And make this the default search option

  3. Scenario 3

    • Given the Import ID search option

    • When the user selects that option

    • Then display log list results based on a string match of the Import ID number

  4. Scenario 4

    • Given the File name search option

    • When the user selects that option

    • Then display log list results based on a string match of the file name

  5. Scenario 5

    • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

See attached screenshot

Environment

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux October 24, 2019 at 1:45 PM

Hi Perfect - I somehow missed that we already had wildcards in the search. Let's go with # 2 and I'll tell the library folks to use the asterisk. Thank you! So I'll close this story now.

Mariia Aloshyna October 24, 2019 at 8:52 AM

Hi I investigated how we can do it, and there are two ways:
1. Create a task for stripes, because all methods are on the SearchAndSort smart-component and we just pass to it a value that a user puts into the Search field.
2. The user can decide by himself what result he wants to get:

  • if he wants the search to be a "begins" string search - he should enter "exemplar" to the search field;

  • if he wants the search to be a "includes" string search - he should put an asterisk at the beginning of the search value "*exemplar".

Mariia Aloshyna October 24, 2019 at 8:06 AM

Hi I'm checking if we can do it. I’ll give you the answer as soon as possible.

Ann-Marie Breaux October 24, 2019 at 6:28 AM

Hi Talked with the library group yesterday, and they definitely prefer "includes" instead of "begins" for the file name and keyword searches. Is it possible to make that change? Thank you!

Ann-Marie Breaux October 23, 2019 at 3:34 PM

HI Tested on folio-snapshot. I was just about to ask about the Committed Error thing when I saw your note. All is working as expected.

One question though - if we wanted the file name search to be an "includes" string search instead of a "begins" string search, is that possible? So, for example, if I search "exemplar," I would get the CornellFOLIOExemplars_bibs result?

If that's possible, let me know, and I'll check with the librarians later today on whether they prefer includes or begins, and then update the story accordingly.

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Folijet

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 25, 2019 at 7:15 AM
Updated August 13, 2021 at 8:28 AM
Resolved October 24, 2019 at 1:46 PM
TestRail: Cases
TestRail: Runs