This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cloudfilesearch [2018_01_30 19:33]
steven [1 Searching files Web]
cloudfilesearch [2018_08_02 14:27]
Line 30: Line 30:
-===== 3 Deeper ​Search ​Options ​===== +===== 3 Content ​Search =====
 +Content search is supported with our on-premises cloud appliance with the [[http://​lucene.apache.org/​core/​|Apache Lucene search engine]]. For more information see [[cloudappliance/​solr]].
 {{:/​cloudfilesearch:​steps:​sme_3_deeper_search_option.png}} {{:/​cloudfilesearch:​steps:​sme_3_deeper_search_option.png}}
-For users who want deeper content ​search ​options we can integrate our on-premise cloud appliance with the [[http://lucene.apache.org/​core/​|Apache Lucene search engine]]Please [[mailto:%20sales@storgemadeeasy.com|contact us]] if this is of interest.+==== 3.1 Content Search Options ==== 
 +Search input: The input string is first split into search ​tokens, by its spaces and punctuation characters (which are ignored). Each of these search tokens are queried in Solr (using AND or OR operators). How these tokenized search terms are used in the query is dependent ​on the modifier flags that you have set when running the query. Searches are case insensitive. 
 +Here's a worked example for the modifiers, if we are searching for "a summer holiday"​.  
 + * **Match exact word or phrase** ​This searches for documents containing ​the exact phrase. If this string is found in the middle of a document, Solr will expect a proceeding word break (space or symbol) before the "​a"​ and after the "​holiday"​. If there'​s a string "a summer holidays"​ then that will not be flagged as a match.  
 +   * To find documents that include every word, but not necessarily together, use the "​AND"​ operator. For example, "a AND summer AND holidays"​ 
 + * **Whole word** - Given each of the word tokens "​a",​ "​summer"​ and "​holiday"​ it would look for documents containing at least one of the words "​a",​ "​summer"​ or "​holiday",​ in any part of the document, regardless of order. So it might flag a document that only contains the word "​holiday"​. The pseudo query would like like"​a"​ OR "​summer"​ OR "​holiday"​So, this could match "I would like a little holiday" ​ ("​a"​ and "​holiday"​ match) 
 +   * To find documents that must include all whole words, use the "​AND"​ operatorFor example, "a AND summer AND holidays"​ 
 + * **Begins with word** - Given each of the word tokens, it searches for documents either containing at least one of those words exactly, or where a word starts with either of those termsThe pseudo query looks like"​a\*"​ OR "​summer\*"​ OR "​holiday"​. 
 +So, this could match "Where are you going on your holidays?" ​ ("​are"​ and "​holidays"​ match) 
 + * **Ends with word** - This is the inverse ​of Begins with WordSo, it searches for words ending in the tokens. The pseudo query looks like: "​\*a"​ OR "​\*summer"​ OR "​\*holiday"​. 
 +So, this could match "could you find my cake?" ("​cake"​ matches)
 + * **Use wildcards** - This is a combination of Ends with and Starts with.  The pseudo query looks like: "​\*a\*"​ OR "​\*summer\*"​ OR "​\*holiday\*"​.
 +So, this could match "could you find my suncream for my summer holidays?"​ ("​cake",​ "​summer"​ and "​holidays"​ match)
 +If you use multiple modifiers, it becomes an OR between them. Here's some notes on that behaviour:
 + * Ticking "​Begins with word" and "Ends with word" is just the same as ticking "use wildcards"​
 + * The modifiers are OR's between each one. So, "Whole word" and "​Begins with word" are probably quite useful together.