Feature #4391

Advance search is broken in 2.x

Added by Jesús García Crespo over 9 years ago. Updated over 8 years ago.

Status:VerifiedStart date:12/03/2012
Priority:HighDue date:
Assignee:Jesús García Crespo% Done:

0%

Category:Search / BrowseEstimated time:6.00 hours
Target version:Release 2.0.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Related issues

Related to AtoM Wishlist - Feature #5148: Enhance usability of AtoM 2.x Advanced Search New 05/30/2013
Related to Access to Memory (AtoM) - Bug #5583: Advanced search in "any field" is only returning results ... Verified 09/13/2013

History

#1 Updated by David Juhasz over 9 years ago

  • Estimated time set to 6.00
  • Sponsored set to No

#2 Updated by David Juhasz over 9 years ago

  • Target version changed from Release 2.1.0 to Release 2.0 - interim 1

#3 Updated by Jesús García Crespo about 9 years ago

  • Status changed from New to QA/Review

It's fixed. If you have any suggestion on the advanced search behaviour please open a new issue.

#4 Updated by Jessica Bushey about 9 years ago

  • Status changed from QA/Review to Feedback

advanced search works if you search for a term that exists in the database.
advanced search RESULTS in OOPS SCREEN if you leave advanced search box empty and then hit enter search.

#5 Updated by Jessica Bushey about 9 years ago

  • Target version changed from Release 2.0 - interim 1 to Release 2.0.0

#6 Updated by Jesús García Crespo about 9 years ago

  • Target version changed from Release 2.0.0 to Release 2.0 - interim 1

#7 Updated by David Juhasz about 9 years ago

  • Target version changed from Release 2.0 - interim 1 to Release 2.0.0

#8 Updated by David Juhasz about 9 years ago

  • Target version changed from Release 2.0.0 to Release 2.0 - interim 1

#9 Updated by Jesús García Crespo about 9 years ago

  • Status changed from Feedback to QA/Review

Done.
Added an extra did-you-mean suggestion if available.

#10 Updated by Dan Gillean about 9 years ago

  • Status changed from QA/Review to Feedback

Issue outline by Jessica in comment 4 still occurs: if you go to the advanced search page and click search, without entering a term, you get a 500 internal server error message.

Usability notes:

Ideally, an option to clear all fields and perform a new search would be provided, that would collapse the and/or/not added fields back to the initial display. Currently a user must reconfigure the page manually for a new search, or go back up to the search bar and click through to advanced search again. A simple button that would reset all fields (that reloaded the page, basically) would enhance usability when a user is not finding what they want with the first query

Depending on screen size, it can be hard to even notice that a search has been performed - if the user has added several boolean additions to the query (ie, let's say 3 and/or/not fields), then the area where the results are returned is out of view - the user might not know that the results are there, and they must scroll down to them. Perhaps if there is some way of a) loading the page with the first of the search results at the top, or b) indicating to the user that the search has been performed and that the results are below, would help.

What if a user wants results that are either Fonds OR collection, but nothing else? Ideally, the dropdowns could also function as multiple selects - otherwise the user must repeat the same query twice to ensure that they have seen all results for what is, in effect, the same level of description.

Finally, since the right hand side of the page is not being used by the usual context menu items (e.g., export, etc), we should consider adding help text that outlines the wildcards we support: * for example...

#11 Updated by Jesús García Crespo almost 9 years ago

  • Status changed from Feedback to QA/Review

Dan Gillean wrote:

Issue outline by Jessica in comment 4 still occurs: if you go to the advanced search page and click search, without entering a term, you get a 500 internal server error message.

Fixed in commit:24f3d9515dd66e10361d6fcdc5e63846c4d6e5bf

Usability notes:
[...]

Thanks for your usability notes. Could you please file a new issue for that and assign it to the next release? Wireframes are welcomed too.

#12 Updated by Dan Gillean almost 9 years ago

  • Status changed from QA/Review to Feedback

Currently (in FF 21.0 and in IE 10 on Win8), the ES auto-suggest feature when a search term is entered in the search bar is not working - consequently, there is no way to get to the advanced search page.

This is a problem in general as users may not be able to find the advanced search option (and it might be worth considering adding an advanced search shortcut to the dropdown of browse options next to the search bar), and it further means that if there is ever a problem with ElasticSearch behaviour in the search bar, it will also prevent users from arriving at the advanced search page.

Jesus, I will move the usability suggestions to a separate issue for 2.1. I will return to wireframing when we have less pressing deadlines ;)

Let me know if the suggestion to include advanced search elsewhere in the interface should become its own issue as well.

#13 Updated by Jesús García Crespo almost 9 years ago

  • Status changed from Feedback to QA/Review

I've addressed your comments in commit:0512ca0fc0068fd044d9e4cd8fbfe76ab28c1294.

Yes, please, file new issues if you want to keep working on this. This issue was initially created to report a fatal error when the form was submitted and that's been fixed. And that was a critical.

I think that your usability suggestions should go to 2.0 instead of 2.1. Thanks!

#14 Updated by Dan Gillean almost 9 years ago

  • Status changed from QA/Review to Feedback

Search results do not seem to be properly combining boolean fields or filters. Example problems included below

1) To reproduce:
- search for "macdonald" in title - 71 results returned.
- search for "ferron" in title - 10 results returned.
- search for "macdonald" in title OR "ferron" in title - 71 results returned (ie, only macdonald)
- search for "ferron" in title OR "macdonald" in title - 10 results returned (ie, only ferron)

2) Similarly:
- search for "témoigne" in scope and content, with level of description set to fonds - no results.
- navigate to: http://archivescanada.accesstomemory.org/fonds-paul-lavoie and compare against search results.

3) Similarly:
search for "Roméo" in any field OR "romeo" in any field AND "Dallaire" in any field - no results.
However, technically this should capture any records about Romeo Dallaire, regardless of accent use. See:
http://archivescanada.accesstomemory.org/romeo-dallaire-collection
http://archivescanada.accesstomemory.org/general-romeo-dallaire-material

Expected result is that fields can be combined, and that search results reflect what can be found in the database.

#15 Updated by Dan Gillean almost 9 years ago

  • Target version changed from Release 2.0 - interim 1 to Release 2.0.0

#16 Updated by Jesús García Crespo almost 9 years ago

  • Status changed from Feedback to QA/Review

#17 Updated by Dan Gillean almost 9 years ago

  • Status changed from QA/Review to Feedback
  • Priority changed from Critical to High

I have just repeated use cases 1 and 2 provided in [[https://projects.artefactual.com/issues/4391#note-14 comment 14]] and the results are unchanged - search terms do not seem to be combined using OR as in 1), and a search for "témoigne" did not turn up any results in either the French or the English interface. So... still seems that advanced search is not working as expected.

#18 Updated by Dan Gillean over 8 years ago

  • Status changed from Feedback to Verified

All of these use cases can now be met - ideally, a search for a term with an "e" would also return a term with an "é" in it, and vice versa - but the workaround for now would be either:

a) search "Roméo OR Romeo"
b) search "Rom?o" - the ? wildcard will search for any character in that spot. (e.g., roméo romio romeo romao, etc.)

We will revisit search improvements in a future issue. Marking this one verified for now since advanced search is no longer broken.

Also available in: Atom PDF