Communifire's search engine returns results based on relevance. Communifire's search engine searches among the following:
When you start typing in the search bar, a dropdown menu appears that suggests results. If you do not see what you are looking for, you can hit enter or click All results.
When you view all results, you are taken to a results page. By default, results are in descending order of relevance.
On the left are search filters. You can filter and sort results in the following ways:
You can choose to display the latest update date on search results pages by enabling the UpdateDateInSearchResults system property.
Tips for Refining Search
By default, quick search support partial search and the search results page does not support partial search. For example, a quick search for Lon will return results including London . If you hit enter and view the search results page, results including London will not be included.
Lon
London
Admin To enable partial search on the search results page, go to Control Panel > System > System Properties and set AppendWildCardToSearchKeyword to true.
Search searches Page Builder pages based on the meta title, meta description, as well as content within Rich Text, Raw HTML, and Dynamic Property widgets. Anyone can search for Page Builder pages in the top level community and in a Public Space . Only members of a Private Space can search for Page Builder pages in a private space.
The search bar at the top of your intranet searches the entire intranet - all people, all public spaces and private spaces a user is part of, and all content in all the spaces a user has access to. Each space also has its own Space Search that searches through only the content in that space.
You can include external content in search, like your organization's other systems and tools, external reference pages, social media accounts, and more. The external content will appear in search results with a title and description you set. Clicking the page will open the external page.
How to Include External Content in Search
Note: Communifire will not search the inner contents of the external content. Communifire will only search the Page Builder page's meta title and meta description.
Use the following URL format to search by tag:
http://myintranet.communifire.com/searchresults?keyword="Tag"&searchtags=1&spaces=SpaceID
Modify the example URL for your use:
sales
human-resources
Note: You can allow guests (not logged-in users) to access the tag filter on the search page by enabling the AllowGuestsSearchByTag system property. Enabling this option will make your tags visible on the internet.
You can see an overview of the keywords and tags people search for and the click-through rate in Control Panel > Analytics > Search Analytics . You can also see search analytics for a specific space in Manage Space: Search Analytics .
Communifire search uses Elasticsearch. Elasticsearch indexes all records as "documents". A document is a set of fields. Each field has a name and a textual value. Each document typically contains one or more fields which uniquely identify it.
In Communifire, each piece of content, like an article, a blog, an event, etc., is stored as a unique document in Communifire's search index. While indexing an individual article, Communifire indexes the article as a single document and indexes the various fields like article title, article body, tags, comments, etc., as separate fields within this single document. The content title is given more weight while indexing so that search results having the search keyword in the title are prioritized over results which have the keyword only in the body.
In the case of users, each user is indexed as a single document with fields like user name, email, full name, and profile fields (both custom profile fields as well as default profile fields) indexed as separate fields in this single document.
In Elasticsearch, by default, results are returned in descending order of relevance. By default, Elasticsearch makes use of Lucene's practical scoring formula, which represents the relevance score of each document with a positive floating-point number known as the score. The higher the score, the higher the relevance of the document. A query clause generates a score for each document, and the calculation of that score depends on the type of query clause.
score
The score is calculated on the basis:
How often does the term appear in the document? The more often, the more relevant. A document containing five mentions of the same term is more likely to be relevant than a document containing just one mention. How often does each term appear in the index? The more often, the less relevant. Terms that appear in many documents have a lower weight than more-uncommon terms. How long is the field? The longer it is, the less likely it is that words in the field will be relevant. A term appearing in a short title field carries more weight than the same term appearing in a long content field.
How often does the term appear in the document? The more often, the more relevant. A document containing five mentions of the same term is more likely to be relevant than a document containing just one mention.
How often does each term appear in the index? The more often, the less relevant. Terms that appear in many documents have a lower weight than more-uncommon terms.
How long is the field? The longer it is, the less likely it is that words in the field will be relevant. A term appearing in a short title field carries more weight than the same term appearing in a long content field.
Source: What Is Relevance? — Elasticsearch
So if Communifire has indexed a short article and a long article, and the keyword is in the title of both the articles, then the short article will rank higher in relevance than the long article.
To understand all this, let's use some examples. Say we have 4 articles (or any content type) added and indexed in Communifire:
Article 1 with title: "Brown fox brown dog" Article 2 with title: "The quick brown fox jumps over the lazy dog" Article 3 with title: "The quick brown fox jumps over the quick dog" Article 4 with title: "The quick brown fox"
Now if the user searches for this text: brown dog, the results would be the following, sorted in decreasing order of relevance:
brown
dog
title
Let's see another example where we have 3 users with the following data indexed in Communifire:
User 1Name: Maria HoresUsername: hmaria22Favourite Movie: Avatar, Schindler's List
User 2Name: Maria JuanezUsername: maria-juanezFavourite Movie: (not filled)
User 3Name: Maria AntaresUsername: a_mariaFavourite Movie: Titanic, Heat
Now if the user searches for this text: maria, the results would be the following, sorted in decreasing order of relevance:
maria
To learn more about relevance, refer to Elasticsearch's What Is Relevance? page.
Communifire search supports boolean operators, boosting, fuzzy search, phrases, and wildcard search.
Admin To enable using special characters in search, go to Control Panel > System > System Properties, edit LuceneSpecialCharFilter, and remove the special characters from the CSV list.
By default, search terms are optional. Search will return results that match at least one of the search terms. You can use boolean operators to require terms, make terms optional, and exclude terms.
Examples:
"New York City" AND London - Returns results including both "New York City" and "London."
"New York City" AND London
Dallas OR London - Returns results with either "Dallas" or "London."
Dallas OR London
London NOT Paris - Returns results that contain "London" and do not contain "Paris."
London NOT Paris
Use the boost operator ^ to make one search term more relevant than another. The default boost value is 1, but can be any positive floating point number. Boosts between 0 and 1 reduce relevance.
^
Example:
Suppose we have 3 pieces of content:
Article 1 contains "fox" Article 2 contains "quick fox" Article 3 contains "slow fox"
A search for quick^2 fox slow^0.5 will return results in the following order:
quick^2 fox slow^0.5
Article 2 containing "quick fox"Article 1 containing "fox"Article 3 containing "slow fox"
Use the fuzzy operator ~ to search for terms that are similar to, but not exactly like the search term. Fuzzy search uses the Damerau-Levenshtein distance to find all terms with a maximum of two changes, where a change is the insertion, deletion, or substitution of a single character, or transposition of two adjacent characters. The default edit distance is 1. The edit distance can be specified by following ~ with a positive integer.
~
Article 1 contains "quick fox" Article 2 contains "quikc fox" Article 3 contains "quokc fox"
A search for quick~ will return Articles 1 and 2.
quick~
A search for quick~2 will return Articles 1, 2, and 3.
quick~2
Wrap phrases in double quotes to search for the exact phrase.
Example: "Knowledge management"
"Knowledge management"
Wildcard search returns results where the wildcard can be replaced by a single character or multiple characters.
Suppose we have 5 pieces of content:
Article 1 contains "text" Article 2 contains "test"Article 3 contains "tester" Article 4 contains "tent" Article 5 contains "testing"
A search for te?t will return articles 1, 2, and 4.
te?t
A search for test* will return articles 2, 3, and 5.
test*
There are Dynamic Search Properties that can be used as text near search areas.
To use these:
Take advantage of Search Synonyms to create sets of words that are related to each other for search purposes.
To set these:
In this example, if you typed in "HR", it would also grab any content with "Human Resources" in it and vice versa. The same applies to "IT" and "Information Technology". You can also add more words to each line, separated by commas, and all the words would pull content with any others on that line.
=>
In this example, if you searched for "animal" you would also pull content with "dog" in it; but not vice versa.
Note You must rebuild the site index for these changes to take place.
Content Expiration
Ensure that content in your intranet is always current and accurate by using content expiration. Select the date and time to expire content, and whether the content should be visible or hidden after expiration. You'll be notified when the content expires, and can then update or delete the content. Content expiration keeps the knowledge base in your intranet relevant and accurate.
Edit Existing Tags
Users can create new tags by typing keywords in the "Add tags" field when creating content. Misspelled or ambiguous tags can cause confusion. You can edit existing tags to fix spelling mistakes or rename a tag.
Delete Existing Tags
Users can create new tags by typing keywords in the "Add tags" field when creating content. Poorly named or ambiguous tags can cause confusion and clutter content. You can delete existing tags to permanently remove them from your site.
is requesting access to a wiki that you have locked: https://my.axerosolutions.com/spaces/5/communifire-documentation/wiki/view/22607/search
Your session has expired. You are being logged out.