Kaseya Community

searching help

  • so this is telligent.....that remains to be seen.... so far.... well you know already don't you.

    I pulled this off the telligent website.... for community server... which I assume is what this facebook forum is.

    anyway.... here is a list from notsotelligent on how to search for things in this forum.

    I hope you find it helpful.  I will be marking it and referring to it frequently to see if it actually helps.



    The following information provides you with suggestions to help you with a search.

    Terms and Phrases

    A query is broken up into terms and operators. There are two types of terms:

    • Single Terms - a single word such as "test" or "hello".
    • Phrases - a group of words surrounded by double quotes such as "hello dolly".

    Multiple terms can be combined together with Boolean operators to form a more complex query (see below.

    The analyzer used to create the index will be used on the terms and phrases in the query string, so it is important to choose an analyzer that will not interfere with the terms used in the query string.


    Lucene supports fielded data. When performing a search you can either specify a field or use the default field. The field names and default field are implementation-specific.

    You can search any field by typing the field name followed by a colon ":" and then the term you are looking for.

    For example, assume a Lucene index contains two fields, title and text, with text the default field. To find the document entitled The Right Way, which contains the text “don't go this way", you can enter one of the following:

    • title:"The Right Way" AND text:go
    • title:"Do it right" AND right

    Since text is the default field, the field indicator is not required.

    Note: The field is only valid for the term that it directly precedes, so the query

    title:Do it right

    will only find "Do" in the title field. It will find "it" and "right" in the default field (in this case the text field).

    Term Modifiers

    Lucene supports modifying query terms to provide a wide range of searching options.

    Wildcard Searches

    Lucene supports single and multiple character wildcard searches.

    • To perform a single character wildcard search, use the "?" symbol.
    • To perform a multiple character wildcard search, use the "*" symbol.

    The single character wildcard search looks for terms that match that with the single character replaced. For example, to search for "text" or "test" you can use the search te?t.

    Multiple character wildcard searches looks for 0 or more characters. For example, to search for test, tests or tester, you can use the search test*.

    You can also use the wildcard searches in the middle of a term, for example te*t.

    Note: You cannot use a * or ? symbol as the first character of a search.

    Fuzzy Searches

    Lucene supports fuzzy searches based on the Levenshtein Distance, or Edit Distance algorithm. To do a fuzzy search use the tilde, "~", symbol at the end of a Single word Term. For example to search for a term similar in spelling to "roam" use the fuzzy search roam~. This search will find terms like foam and roams.

    Beginning with Lucene 1.9, an additional (optional) parameter can specify the required similarity. If a value is between 0 and 1 but closer to 1, only terms with a higher similarity will be matched. For example, roam~0.8. The default is 0.5 if the parameter is not given.

    Proximity Searches

    Lucene supports a proximity search using the tilde "~" symbol at the end of a phrase. For example, to search for apache and jakarta when they are within 10 words of each other in a document, use the search "jakarta apache"~10.

    Range Searches

    Range Queries allow you to match documents whose field values are between the lower and upper bound specified by the range query. Range Queries can be inclusive or exclusive of the upper and lower bounds. Sorting is done lexicographically, as with mod_date:[20020101 TO 20030101].

    This search finds documents whose mod_date fields have values between 20020101 and 20030101 inclusive. Range Queries are not reserved for date fields. You can also use range queries with non-date fields, as with title:{Aida TO Carmen}. This will find all documents whose titles are between Aida and Carmen, but not including Aida and Carmen.

    Inclusive range queries are denoted by square brackets. Exclusive range queries are denoted by curly brackets.

    Boosting a Term

    Lucene provides the relevance level of matching documents based on the terms it finds. To boost a term use the caret "^" symbol with a boost factor (a number) at the end of the term you are searching. The higher the boost factor, the more relevant the term will be.

    Boosting allows you to control the relevance of a document by boosting its term. For example, if you are searching for jakarta apache and you want the jakarta to be more relevant, you can boost it using the ^ symbol along with the boost factor next to the term, as with jakarta^4 apache. This will make documents with the term jakarta appear more relevant. You can also boost phrase terms, such as "jakarta apache"^4 "Apache Lucene".

    By default, the boost factor is 1. Although the boost factor must be positive, it can be less than 1 (e.g. 0.2)

    Boolean Operators

    Boolean operators allow terms to be combined through logic operators. Lucene supports the following Boolean operators:

    • AND
    • "+
    • OR
    • NOT
    • -

    Boolean operators must be ALL CAPS.


    The AND operator matches documents in which both terms exist anywhere in the text of a single document. This is equivalent to an intersection using sets. The symbol && can be used in place of AND.

    To search for documents that contain jakarta apache and Apache Lucene use the query "jakarta apache" AND "Apache Lucene".


    The “ “ operator requires that the term after the “ “ symbol be somewhere in a field of a single document. To search for documents that must contain Jakarta and may contain lucene use the query +jakarta apache.


    The OR operator is the default conjunction operator. This means that if there is no Boolean operator between two terms, the OR operator is used. The OR operator links two terms and finds a matching document if term is in a document. This is equivalent to a union using sets. The symbol || can be used in place of OR. To search for documents that contain either jakarta apache or just jakarta use one of the following queries:

    • "jakarta apache" Jakarta
    • "jakarta apache" OR jakarta


    The NOT operator excludes documents that contain the term after NOT. This is equivalent to a difference using sets. The symbol ! can be used in place of NOT. To search for documents that contain jakarta apache but not Apache Lucene use the query "jakarta apache" NOT "Apache Lucene".

    The NOT operator cannot be used with just one term. For example, the following search will return no results: NOT "jakarta apache".


    The " - " or prohibit operator excludes documents that contain the term after the " - " symbol. To search for documents that contain jakarta apache but not Apache Lucene use the query "jakarta apache" -"Apache Lucene".


    Lucene supports using parentheses to group clauses to form sub queries. This can be very useful if you want to control the boolean logic for a query. To search for either jakarta or apache and website use the query (jakarta OR apache) AND website. This eliminates any confusion and ensures that the Web site exists and either jakarta or apache may exist.

    Field Grouping

    Lucene supports using parentheses to group multiple clauses to a single field. To search for a title that contains both the return and pink panther use the query title:(+return +"pink panther").

    Below is a list of fields defined in CS2 Enterprise Search:

    • body
    • rawbody
    • role
    • url
    • link
    • name
    • app
    • sectionid
    • postid
    • date
    • user
    • userid
    • title
    • settingsid
    • applicationtype
    • applicationkey
    • groupid
    • parentid
    • threadid
    • exact
    • attachmentname
    • attachmenttext
    • tag
    • tagkeyword

    Escaping Special Characters

    Lucene supports escaping special characters that are part of the query syntax. The current list special characters are + - && || ! ( ) { } ^ " ~ * ? : \. To escape these characters, use the \ before the character. For example, to search for (1+1):2 use the query \(1\+1\)\:2.

    For multiple word searches without "and" "or" or "not", "OR" is assumed by default.

    Searching now looks for near matches in post bodies, attachment names, titles, author name, tags and index-able attachments. It also looks for exact matches in the Category/Tag, Author Name, and SectionName fields without requiring additional syntax, although it still supports the advanced syntax, which might make specific data easier to find).

    All fields have equal weight, which could make searching on a common term, especially one used in a tag difficult, as lucene will score matches higher if they occur in a short field.




  • This post I like, your tags even made me giggle a bit (I'm not a fan of tags in general IMO it cheapens the search experience among other things)... the other post... well dead horse comes to mind.

    If I may I'd like to use this to show clients in our app dev side of things how a search fucntion should work, why we did it the way we did and why the caps lock key is evil (see your boolean section).

    Now on to why I came here tonight...

    [edited by: thirteentwenty at 1:08 AM (GMT -8) on 12-9-2010] ...