Jive

Watershed can receive data from any xAPI conformant Activity Provider. Many Watershed reports are flexible and you can configure Watershed to display useful visualizations and metrics from almost any xAPI data set. To help you get the most out of your data, we’re working with a number of product vendors to ensure that the data they send is optimized to produce the best possible results in Watershed. We want to help you to configure Watershed reports in the best way possible to display that data.

Jive is a social collaboration platform that enables users to share ideas, resources and discussions. All sorts of Jive activity is displayed to users in an Activity Stream, including posted files and links, comments and likes. We’ve worked with one of our clients to develop a connector for Jive. Watershed clients can take advantage of this connector to track all of the data in Jive’s activity stream to Watershed and report on it alongside other learning and performance data.

Who can use this feature?
 User Types
Any user with access to the report builder (Global Admins, Area Admins, and some Users) can create reports looking at Jive data.
 Pricing
Available on paid plans (Analyst, CLO, and Enterprise).
 Expertise
Anybody can use this feature.

Installing the Jive xAPI Connector

The Jive Connector is a small PHP application configured to pull data from Jive and push data to your Watershed account as a scheduled task. That means you’ll need a PHP server to put the code on. You’ll also need to set up a scheduled task to run the code daily, hourly or however often you want to send data.

The connector works by hooking into Jive’s Activity Streams implementation, a specification which has a lot of similarity with xAPI. This means that the connector is able to translate all Jive events, even those it was not specifically designed to translate.

Of course, the xAPI data is only as good as the underlying Activity Streams data and in some cases custom translation code may be required for custom Jive events. It also means that the connector is limited to the kinds of events that appear in Jive’s Activity Stream, which does not currently include accessing content. Additional events can be captured with development work.

Contact us to get a copy of the code and to discuss any questions that you or your technical team may have.

Jive xAPI data

The Jive connector uses the following xAPI verbs and activity types:

Action

Verb id

Liked

http://activitystrea.ms/schema/1.0/like

Marked as helpful

jive:helped

Created

http://activitystrea.ms/schema/1.0/create

Updated

http://activitystrea.ms/schema/1.0/update

Commented on

http://adlnet.gov/expapi/verbs/commented

Activity Type

Activity type id

Document

http://id.tincanapi.com/activitytype/document

Forum topic

http://id.tincanapi.com/activitytype/forum-topic

Idea

http://id.tincanapi.com/activitytype/suggestion

Space or group

http://id.tincanapi.com/activitytype/community-site

Jive reports

Some examples of Jive reports are outlined below. 

Likes over time

A likes over time report shows Jive activity in terms of likes, and is a way to monitor how much Jive is being used. Other events, instead of likes, could be monitored as well or instead. 

To configure this, create a line report organized by month and use a 'like count' measure. The 'like count' measure can be configured in Measure Editor using these settings:

Most liked suggestion

The 'like count' measure can also be used in a report (perhaps a leaderboard) organized by activity to show a list of the most liked suggestions. This enables you to monitor hot topics in Jive. 

Comments list

You can use Watershed to display a list of Jive comments. This is set up using a leaderboard report organized by statement id and using a 'comment text' measure configured in configured in Measure Editor using these settings:

Was this article helpful?
0 out of 0 found this helpful

If you can't find what you need or you want to ask a real person a question, please contact customer support.