https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28884
--- Comment #26 from David Cook <[email protected]> --- (In reply to Janusz Kaczmarek from comment #12) > Still, I would not expect from the users of the catalogue the knowledge > about quite advanced, wildcarded ES queries... s/he is usually is not > interested in what is in the back-end. Hence, I would prefer to prepare > Koha to first "understand" a normal user instead of advanced search engines > operator. One more comment and then I'll be done. (Apologies if my comments are coming across overly negative. I've spent over a decade looking at Koha's search code, and I've had a lot of librarians grumpy with me about Koha's search functionality in that time. More now with the switch to Elasticsearch than ever really...) The difficulty here is that we're already expecting them to understand OR/AND and () when it comes to Elasticsearch. One could argue that we should escape () and wrap every query in double quotes, if we don't think a normal user can understand complex search queries. But that will really irritate power users (on both staff interface and OPAC). And that's not what we've done historically. We try to outsmart the user, and it only kind of works. Sometimes I think we should just make a full decision one way or another. The Google style search box should probably just be a simple search with auto-escaping for reserved characters. Then we could have a Power Search or something like that in the Advanced Search area for power users where we "take off the kid gloves". If you use Google as an example, they actually do explain their search query syntax on their Advanced Search page. (Of course, I just found a little bug in Google's Advanced Search. Nothing is perfect...) I think that's where system preferences can be powerful, and individual libraries could then also analyze the search behaviour of users to see how they should tweak their search settings. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
