I'm testing full text search (FTS) with Alfresco 6.0.7-ga and I have found that the "phrase search" (Search for a phrase | Alfresco Documentation ) is not what I expected.
Our users want to be able to search:
Obviously we will adapt the search performed by the user to the Alfresco syntax.
I've been playing with the exact term search (Search for an exact term | Alfresco Documentation ) but I'm not able to make it work.
How can I do an exact-exact phrase search?
I've tried combinations of quotes("), apostrophe('), back-slash apostrophe (\') and exact search (=), but none seems to work in either "share general search" or "CMIS FTS search".
Thanks in advance,
Are you using Alfresco in a cross locale environment? Do you have documents in different languages? Are your users accessing from browsers or OSs with different locales?
Yes, we have enabled cross-locale in SOLR.
Yes, mainly we have documents in Spanish and Catalan, but we can have documents in English and French.
Our corporate computers and browsers have Catalan as the default language.
I have created a sample configuration (ES and EN) locales at GitHub - aborroy/search-services-cross-locale: Alfresco Search Services deployment for Cross Locale ...
I tested different sentence searching terms, like "are animals intelligent" and it works as expected.
FTS Searching Sintax (to be included in Share search box and other APIs) is described at Alfresco Full Text Search Reference | Alfresco Documentation
Let me know if it works for you.
sorry for the delay.
I have re-tested the searches.
Searches seem to be exact on my custom type (premsa:Noticia) and non-exact in cmis:document.
The results are the same using or not using quotes.
These are the results I get:
After that, I have download 2 documents of premsa:Noticia (one with "crisi" and one with "crisis") and uploaded them as cmis:document and now these 2 new cmis:documents appear in both queries.
Why do I get these results? Does cmis:document have a special configuration?
We have an open issue for this use case:
Exact term search is not working currently.