Table of Contents
In Zimbra Social 8.5, search enhances the user experience with smart queries and relevant suggested results.
- Search is always available on the page. The Social theme has a static header that keeps the search field visible wherever a user scrolls on a page.
- Search automatically returns results for the context where it's being used. For example, while searching in a specific group, the header will say "Search in <group name>". If searching in a group's application, it will say "Search in <group name> 's <application>." Other filters or parameters can be applied.
- Searching in a forum will return similar forum threads as the query is typed - in order to save the user from needlessly posting a similar thread.
- Search quality is improved by filter buttons - Contents, Groups, or People. If being used in a group or application, Search will also display an Anywhere filter button.
- Enhanced search result display - if the user clicks Advanced Search in the search field, Zimbra Social furnishes additional parameters for relevancy, content type, location, author, or recency.
- Searching by people is enabled at the site level.
Search results are weighted for quality so that the best, most relevant results are displayed first. Factors contributing to this scoring include liking, helpfulness, ratings, tagging, bookmarking, views, sharing, subscriptions, comments, and marking as featured.
When using the default search provider, Zimbra Social search supports a simplified subset of the Lucene syntax:
- + - ex. +registration class
- - - ex. registration -event
- Quotes/Grouping - ex. "client API"
- Field query - ex. "title:enrollment". When a field query is used, you can use Boolean operators. (View a list of fields used out of the box.)
Boolean operators are ignored, except when using field queries - in other words, AND and OR are ignored in most cases.
The query processing in Zimbra Social's search engine, Solr, is extremely configurable. Zimbra Social uses Solr's DisMaxRequestHandler for any query that does not contain a colon (:). For queries that do contain a colon, the StandardRequestHandler is used. The default behavior is for all clauses to match. For example, when you search for the term "class enrollment", Solr (technically the DisMaxRequestHandler) will take responsibility for building a query based on the handler configuration and return documents that match the specified terms.
The DisMaxRequestHandler configuration is the best place to start if you want to tune queries.
Search result pages and search result pages are tagged as "nofollow," ensuring that they are not crawled and indexed by search engines.
This section contains the following articles: