double quotes in opensearch / firefox search

[michaelgk]

I have installed the "alfresco keyword search" as one of the firefox search engines. I notice in this and in the opensearch sidebar that using "double quotes" to group search terms results in no results.

i.e.  I have documents containing …     Issac Newton
I can search for     Issac Newton     and get results but if I use "Issac Newton" in the search box I get no results.  Is this correct behavior ?  How can I group the terms (like I would expect with double quotes) ?

[dnind]

These two posts may help shed some light on the problem:
http://forums.alfresco.com/viewtopic.php?t=5685&highlight=opensearch
http://forums.alfresco.com/viewtopic.php?t=6004&highlight=opensearch

[michaelgk]

I saw these posts but they don't address my question… (double quotes)

[dnind]

My understanding (from experimentation and the mentioned post) is that Alfresco OpenSearch does not yet support/expose phrase searching (between double quotes) or boolean searching (AND, +, -).  It does support wildcard searching (word*).

Alfresco will implement/expose more functionality in future versions so it is the same as the standard searching available in the web client.

So at the moment with Alfresco's OpenSearch you get:
- key word searches: wordone wordtwo
- wildcard searching: word*

You can change the default configuration for your repository so that it defaults to AND searching i.e. find documents with both wordone and wordtwo, as opposed to the default which finds wordone or wordtwo. 

From:
http://forums.alfresco.com/viewtopic.php?t=5685

The OpenSearch keyword search defaults to OR.  There's no support for AND or + operators in the search syntax.

Search behaviour is consistent across local and remote repositories - they're all using the same search back-end.  So, I'm not sure why you're getting inconsistent results.

A freemarker template is used to build the keyword search query - it's in config/alfresco/templates/api/KeywordSearch_query_.ftl.  It could be changed to use AND instead of OR.

In 2.1, I hope we can support the same syntax as the Web Client search.