Pathgather

Watershed can receive data from any xAPI conformant Activity Provider. Many Watershed cards 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 cards in the best way possible to display that data.

Pathgather is an enterprise learning platform that supports self directed and social learning across a variety of learning activities curated from internal and external sources. Learners can plan their learning by building paths of content which they can share with others. They can collaborate and discuss with others in gatherings or find an expert by searching for skills listed on their profile. Data about all of these activities can be tracked via xAPI and reported on in Watershed alongside other learning and performance data.

This guide has five sections:

Connecting Pathgather to Watershed

To connect Pathgather to Watershed, you will need an endpoint, key and secret for your Watershed account. Then simply get in touch with the Pathgather team so they can configure the connection in your account.

Reporting on Pathgather data

Data from Pathgather mainly relates to content utilization and social interactions. Using Explore’s simple configuration, you can quickly create reports that compare people, activities and time periods by Pathgather usage. You can also compare Pathgather usage to success in assessments, job performance and business metrics. We recommend the Activity Count and Interaction Count measures to report on that activity.

Advanced configuration enables you to get a lot more granular in reporting on Pathgather activity. It lets you ask questions like: ‘who is searching for what?’, ‘what types of thing are being recommended most?’ and ‘what skills do people have?’ The Watershed team will help you set up these Advanced configuration cards, and the sections below give an explanation of the configuration used to create them.

Please note: Pathgather statements include a lot of data, not all of which is utilized in the configuration described below. If you have reporting requirements not covered by the advanced configuration outlined in this guide, just let us know!

Advanced filters

The following filter properties can be use with Pathgather. See Advanced Configuration for more details on advanced filters in general.

Pathgather only

Use a context activities filter to report only on data from Pathgather:

"contextActivityIds": {
  "ids": [
    "https://pathgather.com"
  ]
}

Verb filters

You can use a verb filter to report only particular actions, for example:

"verbIds": {
  "ids": [
    "https://pathgather.com/xapi/1.0/actions/searched_for"
  ]
}

Pathgather actions are outlined in the table below.

Action

Verb id

Searched for

https://pathgather.com/xapi/1.0/actions/searched_for

Started

https://pathgather.com/xapi/1.0/actions/started

Completed

https://pathgather.com/xapi/1.0/actions/completed

Was recommended

https://pathgather.com/xapi/1.0/actions/was_recommended

Added (a skill)

https://pathgather.com/xapi/1.0/actions/added

Commented on

https://pathgather.com/xapi/1.0/actions/commented_on

Joined

https://pathgather.com/xapi/1.0/actions/joined

Was invited to

https://pathgather.com/xapi/1.0/actions/was_invited_to

Logged in

https://pathgather.com/xapi/1.0/actions/logged_in

Created

https://pathgather.com/xapi/1.0/actions/created

Activity Type filters

You can use an activity type filter to report only on actions relating to particular types of thing. For example:

"equals": [
  {
    "fieldName": "object.definition.type",
    "values": {
      "ids": [
        "http://pathgather.com/xapi/activity-type/content",
        "http://pathgather.com/xapi/activity-type/path"
      ]
    }
  }
]

Pathgather activity types are outlined in the table below:

Activity Type

Activity type id

Content item

http://pathgather.com/xapi/activity-type/content

Path

http://pathgather.com/xapi/activity-type/path

Gathering

http://pathgather.com/xapi/activity-type/gathering

Conversation

http://pathgather.com/xapi/activity-type/conversation

Skill

http://pathgather.com/xapi/activity-type/skill

Search query

http://pathgather.com/xapi/activity-type/search

Advanced dimensions

Dimensions control how data is organized. See Advanced Configuration for more details on advanced dimensions in general.

Organize by property of content extension

You can take advantage of Pathagather’s content extension to organize by various aspects of content metadata such as topic, level or provider, as shown in the example below.

{
  "type": "STATEMENT_PROPERTY",
  "statementProperty": "object.definition.extensions.[http://pathgather.com/xapi/extension/content].provider.name"
}

Here’s a complete example of content metadata:

"http://pathgather.com/xapi/extension/content": {
    "id": "5e6ebf36-b5f5-44e0-bca6-493496cf71b9",
    "_type": "Content",
    "name": "Some example content item",
    "description": "This is an example content item. It will take 30 minutes to complete.",
    "created_at": "2016-05-28T16:26:44.752-04:00",
    "updated_at": "2016-08-26T03:01:09.175-04:00",
    "level": "All",
    "rating": 0,
    "reviews_count": 0,
    "content_type": "Course",
    "source_url": "https://provider.example.com/url/of/content",
    "tags": [],
    "enabled": true,
    "deactivated": false,
    "publicly_accessible": true,
    "provider": {
        "id": "5e46a4b8-0b80-40a9-849a-feed471b8dc5",
        "created_at": "2016-05-25T21:07:00.265-04:00",
        "updated_at": "2016-05-25T21:07:00.265-04:00",
        "name": "Some such provider",
        "_type": "Provider",
        "may_require_vpn": false,
        "may_not_be_mobile_friendly": false
    }
}

Organize by person who recommended or invited

In statements about recommendations and invites, the person who was invited or had content recommended to them is the actor of the statement. The person who made the invite or who recommended the content is listed in the context.instructor property. Use the following dimension to organize by instructor:

{
  "type": "STATEMENT_PROPERTY",
  "statementProperty": "context.instructor.person.id"
}

Organize by statement Id

Sometimes you want to look at each xAPI statement individually, for example to see all comments in a gathering or a complete list of searches made in a particular time period. This can be achieved by organizing by statement id and using a ‘value measure’ as described in the measures section below. Use the following syntax to organize by statement id.

{
  "type": "STATEMENT_PROPERTY",
  "statementProperty": "id"
}

Advanced measures

The following types of measures can be used with Pathgather data. See Advanced Configuration for more details on advanced measures in general.

Count and distinct count measures

Advanced measures for Pathgather data tend to be a count or distinct count aggregation combined with one of the advanced filters outlined above. For example:

{
  "name": "Recommendations",
  "aggregation": {
    "type": "COUNT"
  },
  "valueProducer": {
    "type": "STATEMENT_PROPERTY",
    "statementProperty": "id"
  },
  "filter": {
    "verbIds": {
      "ids": [
        "https://pathgather.com/xapi/1.0/actions/was_recommended"
      ]
    },
    "equals": [
      {
        "fieldName": "object.definition.type",
        "values": {
          "ids": [
            "http://pathgather.com/xapi/activity-type/content",
            "http://pathgather.com/xapi/activity-type/path"
          ]
        }
      }
    ]
  }
}

Value measures

Measures can also be used that display the value of a learner’s response, such as a comment or a search query:

{
  "name": "Comment",
  "aggregation": {
    "type": "LAST"
  },
  "valueProducer": {
    "type": "STATEMENT_PROPERTY",
    "statementProperty": "result.response"
  },
  "filter": {
    "verbIds": {
      "ids": [
        "https://pathgather.com/xapi/1.0/actions/commented_on"
      ]
    }
  }
}

For example, the above configuration can be used in a leaderboard organized by statement id in order to display a complete list of comments. The LAST aggregation can also be used with other statement properties such as the actor and activity name.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

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