Forum Discussion
RESOURCE: Full Guide to xAPI and Storyline
Hello lovely Articulate Storyline users!
I've been working on an in-depth guide to sending custom xAPI statements from Articulate Storyline courses for over a year now, and the full guide is final...
Hi Devlin! Thanks so much for posting these tutorials! I've followed the basic ones backward and forward but am running into a snag because I'm trying to apply what you've written to a different use case.
1. I would like to use the TinCan compatible LMS "LearnUpon", not a standalone LRS like you've shown. My understanding is that the LMS will supply the "actor" information. I'm not sure if I still need to call GetPlayer() somewhere or not.
2. I would like to use Storyline's default ability to create statements for graded questions and then integrate them with my own statements. I'm hoping to load the whole zip package into the LMS and have it produce one report that contains both default and custom activity statements. From my testing, when I publish a storyline course using TinCan, Storyline produces a file called tincan.xml. The rules of this output are published here. I believe (but am not certain) that the purpose of this file is the same as the script called xapi-statement.js in your tutorials. The LearnUpon LMS looks for the tincan.xml file in the root folder and won't publish without it. In the tutorial files you've published as Web, not as TinCan. Why is that?
Do you know how I might adapt all the good information in your tutorials to somehow have the javascript triggers execute an activity statement that ends up in the tincan.xml file? Or, is there another approach I could use with an LMS?
