Storyline

As an xAPI conformant LRS, 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.

This guide tells you how to correctly configure and publish Storyline courses and then configure Watershed to get the best results.

This guide has 3 sections:

Configuring and publishing Storyline courses

This section outlines what you need to do within Storyline in order for it to produce the best data for Watershed to work with. If you have existing Storyline courses published without following this guidance, we recommend that you re-publish the courses following this guidance.

Important: Use the latest version

Articulate have made important improvements to their xAPI tracking in later versions. We recommend that you updated to the latest version, especially if you are using a version of Storyline prior to 2.5, which was released in May 2015. If you are using any version of Storyline 2, updates to 2.x versions are free.

To find out which version of Storyline you’re using, open Storyline, click HELP, then click About Articulate Storyline. The box that appears will tell you the update number in grey text in the top right hand corner. For example, if the box says “Storyline 2” in big blue letters and “Update 7” in the top right, you’re using Storyline 2.7. If you’re unsure, we recommend upgrading to the latest version anyway.

See Articulate’s website to get the latest version and for instructions on how to upgrade.

Please note: if you already have important data generated from packages published with an earlier version of Storyline, then updating your packages may mean that the new data takes a different format to the old data and may appear differently in reports. It might not be entirely compatible. Let us know if this is a concern.

Give slides and objects helpful names and identifiers

The names and identifiers you use for slides and objects within Storyline will be reflected in Watershed reports, so it’s important to choose good names. Instead of “Untitled Slide”, give each slide a name. Instead of “Oval Hotspot 4”, name your hotspot according to which part of the picture it’s covering. This is a little extra work, but worthwhile so you know what’s what when it comes to looking at the reports in Watershed.

Complete the LMS course information

When publishing your course, you need to configure it to use “Tin Can API”. This is another name for xAPI. It’s really important that you populate the Reporting and Tracking settings correctly. Here’s how to open them:

  1. In Storyline, go to the Home tab on the ribbon and click Publish.
  2. Select the LMS option on the left edge of the publishing window.
  3. From the LMS drop-down list at the bottom of the window, select Tin Can API.
  4. Click the Reporting and Tracking button.

The Reporting tab has four settings. Enter a short but helpful Title and a fuller Description. Both of these may be displayed in Watershed reports. Leave the Launch URL as the default (“story.html”) unless you really know what you’re doing or we’ve advised you to change it.

The Identifier field is the most important. This should take the form of a web address without the http:// at the start. We recommend the format [your organization’s website]/xapi/storyline/[unique course id]. For example, if we created an e-learning course titled ‘Using Storyline with Watershed’, it might have the id watershedlrs.com/xapi/storyline/using-storyline-with-watershed-10142015.

Including the date on the end helps to ensure that the id is unique within our organization. We also recommend that you keep a record of the identifiers you use within your organization to avoid using the same one twice for similar courses. Whenever you re-publish a course you should use exactly the same identifier. If you change the identifier, Watershed will treat it as a completely new course.

In the Tracking tab, make sure you choose the settings that are most appropriate for your course. You can now save those settings and publish your course.

Making changes

If you need to make changes to a course after learners have started using it, we recommend that you make a backup of your Storyline project file before making any changes, that you make the changes carefully, and that you test the new version with you reports before releasing it to learners. Deleting and re-creating slides and objects could result in the identifiers of those slides and objects changing accidentally, which could adversely affect your reports.

Test your courses

Be sure to test the tracking of your Storyline courses. In particular, make sure that quiz results are sent to the LRS correctly when the learner fails, then passes the quiz. Some users have reported a potential issue with this on the Storyline forums.

Launching Storyline courses

When you publish a Storyline course, the course does not know who the learner is or where to send the tracking data. The course has to be told this information when the course is launched by a training delivery system, normally an LMS. The training delivery system should handle collecting information about who the learner is, but you’ll need to configure it with your Watershed LRS credentials and endpoint. Exactly where these configuration settings are entered will depend on what system you are using.

See How do I add an activity provider to Watershed? for details of where to find your endpoint and credentials in Watershed. Ask us if you need help configuring your LMS or other training delivery system, or for advice on launching content without an LMS (e.g. from an e-mail, text message or QR code).

Configuring Watershed to report on Storyline data

Data from Storyline courses works well with all Watershed cards, especially the Activity Card, which reports on course completion, success, time taken and score, and provides detailed question analysis. The Interactions, Activity, Accomplishments and Skills cards do not require any special configuration for Storyline data so we’ll just look at the Leaderboard and Correlation cards below.

Leaderboard

Storyline data about course completion, passes, time spent and scores can all be used within a Leaderboard. Where the learner takes the course multiple times, you might be interested in the first, last, best or worst attempt, or you might want an average or total. All of these measures can be used within Watershed’s Leaderboard card and you’ll likely want to create a single Leaderboard that contains the three or four measures most relevant to your organization and the particular course being analyzed.

Our demo site includes three Leaderboard cards for Storyline looking at time taken, score and course completions and passes respectively. This guide outlines how to set those three Leaderboard cards up. Speak to us for help setting up your own Leaderboard with the specific measures you need taken from the three Leaderboards outlined below.

Time Taken Leaderboard

The Time Taken Leaderboard ranks learners by total, average, fastest, slowest, first and most recent time taken for the course. To set it up, create a new Leaderboard card and open Advanced configuration. Replace all the configuration code with the code below.

{
  "dimension": {
    "type": "PERSON"
  },
  "measures": [
    {
      "name": "Total Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "SUM"
    },
    {
      "name": "Average Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "AVERAGE"
    },
    {
      "name": "Fastest Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "MIN"
    },
    {
      "name": "Slowest Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "MAX"
    },
    {
      "name": "First Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "FIRST"
    },
    {
      "name": "Most Recent Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "LAST"
    }
  ]
}

Now return to Simple configuration to complete the Card Text and add your course to the Activities filter. Then Save as new card.

Key questions answered: Who was the fastest? Who was the slowest?

Score Leaderboard

The Score Leaderboard ranks learners by average, fastest, slowest, first and most recent score for the course. To set it up, create a new Leaderboard card and open Advanced configuration. Replace all the configuration code with the code below.

{
  "dimension": {
    "type": "PERSON"
  },
  "measures": [
    {
      "name": "Average Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "AVERAGE"
    },
    {
      "name": "Best Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "MAX"
    },
    {
      "name": "Worst Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "MIN"
    },
    {
      "name": "First Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "FIRST"
    },
    {
      "name": "Most Recent Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "LAST"
    }
  ]
}

Now return to Simple configuration to complete the Card Text and add your course to the Activities filter. Then Save as new card.

Key questions answered: Who scored the highest? Who scored the lowest?

Completion Leaderboard

The Completion Leaderboard ranks learners by number of completions, passes and failures. To set it up, create a new Leaderboard card and open Advanced configuration. Replace all the configuration code with the code below.

{
  "dimension": {
    "type": "PERSON"
  },
  "measures": [
    {
      "name": "Completions",
      "field": {
        "type": "LONG",
        "id": "result.completion"
      },
      "aggregation": "COUNT",
      "match": "true",
      "value": 0
    },
    {
      "name": "Passes",
      "field": {
        "type": "LONG",
        "id": "result.success"
      },
      "aggregation": "COUNT",
      "match": "true",
      "value": 0
    },
    {
      "name": "Fails",
      "field": {
        "type": "LONG",
        "id": "result.success"
      },
      "aggregation": "COUNT",
      "match": "false",
      "value": 0
    }
  ]
}

Now return to Simple configuration to complete the Card Text and add your course to the Activities filter. Then Save as new card.

Key questions answered: Who has completed, passes or failed the most? Who has never completed, passed or failed the course?

Correlation

As with the Leaderboard, there’s a whole range of measures that you could explore with the Correlation card. Perhaps you want to explore what factors might cause a learner to repeat a course? Maybe you want to know if learners who spend longer in the course get a higher score?

The example on our demo site looks at whether or not learners who have done the course more times have faster and higher scoring most recent attempts than those who have not done the course so many times. Let’s look at how to set that one up; ask us if you’d like to look into any other questions about your courses.

Create a new Correlation card and open up Advanced configuration. Replace all the configuration code with the code below.

{
  "measures": [
      {
      "name": "Completion Count",
      "field": {
        "type": "LONG",
        "id": "result.completion"
      },
      "aggregation": "COUNT",
      "match": "true",
      "value": 0
    },
    {
      "name": "Most Recent Time",
      "field": {
        "type": "DURATION",
        "id": "result.durationCentiseconds"
      },
      "aggregation": "SUM"
    },
    {
      "name": "Last Score",
      "field": {
        "type": "DOUBLE",
        "id": "result.score.scaled"
      },
      "aggregation": "LAST"
    }
  ],
  "dimensions": [
    {
      "type": "PERSON"
    }
  ]
}

Now return to Simple configuration to complete the Card Text and add your course to the Activities filter. Then Save as new card.

Key questions answered: Does repeating the course lead to improved score and reduced time taken in the most recent attempt?

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.