Cloud Search service

About Cloud Search service

Jive Cloud Search service is available when you are using the Jive Cloud. It is enabled by default.

The Cloud Search service follows best practices for data separation. All data is written, stored, and accessed with a tenant-ID unique to the owner of the data, and no access to data for a given tenant-ID is permitted unless a client also presents a secret key for verification in accordance with OAuth. All communication is over HTTPS.

Attention: The Cloud Search service is based on the Amazon Elasticsearch service. If your organization requires you to whitelist IP addresses, see Required Jive domains and firewall rules for the addresses you need to whitelist.

Cloud Search benefits

Cloud Search provides the following benefits:

Infinite scale: By leveraging a cloud-based Big Data infrastructure, the search service can scale to any level while providing full redundancy.
Continuous improvement: Because search is deployed as a separate service, it can be improved at any time without disrupting other Jive functionality. Just as with familiar web search tools, the relevance of Jive search results gets better over time.
Redesigned architecture: The Cloud Search Service is based on Amazon Elasticsearch Service. The main benefits are improved stability and performance, greater relevance due to enriching Jive objects with metadata, and reduce the downtime for reindexing of content, people and places. For more information about the employed services, see Amazon Elasticsearch Service on the AWS portal.
Attention: The Cloud Search Service reindexes only the first 40,000 characters of each content item.
Better experience for users: Enhanced filtering options, user's search history, suggestions that are based on the context of your community, and other search aspects make using search more intuitive and comfortable for users. For example, spelling corrections when you search for people are provided from the community users corpus. And suggestions for content search are provided from the text corpus of your community, including the object metadata.

Basic search algorithm

Searching is done on the available fields, where a field is a single piece of information within the content, place, or user profile you're searching. For example, in a document, you have the title/subject, the content, and the tags. For a user, you have first name, last name, expertise, tags, and many more.

By default, Cloud Search uses AND search on types of searches; that means that all search terms must be present in the result. Users may specify search operators directly if necessary: OR if at least one term must be present, NOT to exclude specific words, and others. Additionally, users can apply special modifiers, such as quotes or keywords, to make search phrases more specific. The algorithm searches all included text, including attachments and comments – not just the initial blog post, document, or discussion. For more information on constructing search queries, see Search overview and Search rules in the Cloud User Help.

The results depend on what users are searching for: content, people, or places. For more information on how different search types work, see Content search and People and place search.

Spotlight search and Advanced search

The Spotlight search appears at the top of each page. It’s intended as the "quick access" search feature, with suggestions, frequently used items, and search history. So, when typing the first few letters in the search box you can see suggestions based on the quick search performed in the background – including content completion and spelling correction options. In order to initiate the search, you will need to click on one of the suggestions or press Enter.

In order to initiate the search, you will need to click on one of the suggestions or press Enter. At this point, the Spotlight search adds a wildcard (*) to the end of your search term. This means that if you’re searching for Library of Congress and press Enter after typing Librar, it searches for library, libraries, and other words with the same stem, not just librar. Note that the Spotlight search searches for tags as well as content, people, and places.

If that is not enough, you can switch to the Advanced search. It offers more options to refine your search and does not apply the wildcard, as it expects you to provide all of your detailed criteria for the most specific results. For example, here you can limit a document search by author.

For more information, see Search and browse features and Using Spotlight search in the Cloud User Help.

@Mentions

When you start to @mention someone or something, Jive searched similarly to the Spotlight search. The search algorithm takes what you've typed in so far and adds a wildcard (*) to it. This means that no stemming is done with this search.

The main difference from the Spotlight search is that @mentioning only searches the title of content or place and username, name, and email of a user.

For @mentions, search synonyms work only on exact words (not suffixed with a wildcard *). For example, let's see how it works for a mention query that looks like this: Alice_Ford OR (Alice AND Ford*). In this case, synonyms will be used for Alice only unless Ford* has been added to the synonyms list.

For more information about using @ mentions, see Search overview in the Cloud User Help.

Suggestions

The Cloud Search Service provides suggestions based on the index content. So, when you type first few letters in the search box you can see suggestions based on the quick search result done in the background for you.

These suggestions are based on a special multi-valued field data that is provided during document indexing; is field is not used in the regular search. For people search, it contains person first name and full name, for other content it contains the title (subject).

The search service checks for prefix matches that user types in the search box at the same time allowing fuzzy matching to be able to provide suggestions to correct some spelling mistakes. In practice, the first letter must always match. And the longer search phrase is the less exact matches are allowed.

Suggestions respect user access rights, as well as access to content and filtering by type. So if a user wants to search just for some blog post and they selected the Blog posts type filter, in suggestions, they will see only blog posts which they can access.

Note that suggestions are not affected by synonyms, both for content and people search.

Search configuration

For more information about configuring search, see Configuring content search, Configuring user search, and Configuring OpenSearch.