During this coming weekend, we will be rolling out an enhancement to how cloud search handles recently created or edited documents. Today's behavior merges search results from recently edited documents and from the main search index into one set of results (with the recent edits on top). This means that if you create a doc, then search for it, you find it - but it also means that recent edits get a short term boost in how they are displayed by the search system. We have received feedback from many customers that this behavior is problematic and we are working on a long term fix for it. However, we have also decided that a good short term fix will be to only include the the recent edits of the current logged in user in the "recent index" that gets boosted.
The primary impact it will have on users is that recently edited documents will no longer get an extra boost (except for documents that user recently edited himself). The potential downside is that for recently created documents - users will have to wait for the documents to be included in the main index (usually ~15 minutes lag time) before they can be found (via search) by users who are not the author.
*Note: This change is happening this weekend for our US (PHX) data center. Due to scheduling, the EMEA data center update (AMS) will be in the next few weeks.
I am pleased to announce some important improvements to the cloud search service which are releasing to coincide with our Fall Cloud release but are applicable for all cloud search customers.
The search team has a set of improvements in the hopper and they are being deployed in phases. This first phase is releasing this weekend and includes:
When a content object is associated with an outcome, we will update the rank of the object accordingly. Objects marked as "outdated" will be ranked lower, and objects marked with other outcomes will be ranked higher -- among which objects marked as "official" and "final" will get the strongest boost. Leveraging these outcomes will make it much easier for users to find content that the company cares about most, and it is one of the most requested features by customers around search. Of course, this improvement only applies to our cloud customers or to those who upgrade to Jive 7 to get the structured outcome functionality.
As content ages (as determined by last modification date), we will reduce its relevance score. Since it is a very new feature, the decay function is relatively moderate. This is another most requested features by customers around search.
Tokenizing tags by underscores
When a tag contains multiple terms, the terms are usually concatenated by underscores. However, we didn't tokenize tags by underscore (e.g., searching for term "search" wouldn't match tag "cloud_search"), and so tags were not very useful in search relevance. This should make tagging much more effective and help with search relevance!
Accents are removed during search, e.g., searching for "protege" will get protégé search test . For now, we only applied it on English content. We will be investigating other languages.
Thai becomes an official supported language. We have full support on Thai now!
Setting ranking factors per content type
Different content types have different characteristics. Blogs can't be marked as "final". Status updates decay fast. Polls are very short. Using a universal algorithm + configuration for all content types is apparently less ideal. Starting from this update, we will treat each individual content type somewhat differently. The difference is minor now, but we expect to have more and more special treatment per content type as it makes sense.
That's the list for phase 1 - look for updates on phase 2 in the coming months!
I'm happy to announce the availability of 6.0.1. This is a maintenance release that fixes several issues. You can download this update from your purchases page.
The 6.0.1 release includes a number of significant improvements to resource usage and other performance improvements. We also added Dutch, Russian, and Traditional Chinese to our supported languages. You can now upload images or other files for use in your HTML and Rich Text widgets which allows for better performance. Finally, we dramatically increased our compliance with accessibility standards.
More details on specific issues fixed can be found here:
I'm pleased to announce the availability of 5.0.5. Jive 5.0.5 is a maintenance release that contains a significant number of bug fixes. To find out more about the specifics of the bug fixes, look here: Fixed Issues in Jive 5.0.5
Jive SharePoint Connector 220.127.116.11 is now available! This Jive SharePoint Connector 18.104.22.168 can only be used with Jive 5.0.x, and is not an upgrade from the Jive SharePoint Connector 1.6 plugin. SPC 5.0 has the same features as Jive SharePoint Connector 1.6. If you use Jive version 4.5, you can download SharePoint Connector 1.6, which is the most current version. If you have previously purchased the SharePoint Connector module and would like the latest version, please create a case in your customer group, and we will reply with a link and password. You can get the Jive SharePoint Connector by creating a case in your customer group. You cannot download it from your Purchases or the Plugin Downloads space.
SP-1851: Intermittent connectivity issue related to the SharePoint location's cached connection state.
SP-1849: All day calendar events may show up on the wrong day when you change the timezone.
SP-1852: SharePoint performance issue when Socialization is enabled.
SP-1524: When you unsocialize a site/list/library, you still see the Jive Status column in the list.