Searching for parent metadata leads to error

[ShanaLMoore]

Summary

Searching for parent metadata leads to a No Matches Found error in the UV.

Related

ref: #21

Make sure that the work to enable searching for all metadata is enabled or included for your local development. ref: notch8/britishlibrary#390

Acceptance Criteria

If there is a parent match...

• We should not see the No Matches Found error
• the parent thumbnail should be highlighted with a blue magnifying glass, in the UV's left pane.

If there is no matches...

• we should see the No Matches Found error.

Screenshots or Video

Searched for the word "dog" which is the parent's Alt Title:

Testing Instructions

Manually or via bulkrax, create a work with child works.
On the catalog page, search for metadata that exists on a parent work but not its children.

• you will probably need to replicate this by editing the parent metadata directly, with a unique input.
  From the catalog page, search for that unique word. The parent work should return.
  Click into the parent work. It should auto perform a search in the UV.
• before this would immediately result in a no matches found error
• We don't want to see that error because there actually is a match on the parent.
• The parent's thumbnail (in the UV's left pane) should be highlighted with a blue box and magnifying class, if a match is found.

Perform a bogus UV search (one that should not result in a match).

• we should see a no matches error msg

Notes

[DiemBTran]

This passes SoftServ QA: See attached screenshots.

tested on:

• parent work: https://dcadmin-test.dlib.indiana.edu/concern/scientifics/st74cq441?locale=en&parent_query=tran

Searching for a parent work's metadata in the catalog leads to an auto-UV search for the query. Conducting a bogus search leads to an error message (correct).