How to try out xAPI tracking with Rise ?

Hi Philippe! It looks like you reached out to someone from the Talent LMS support team over here, so I wanted to link that discussion for anyone following along. ☺️

One more thing, Philippe! I noticed you mentioned SCORM Cloud throws communication errors with the LRS. We'd like to test it out on our end and take a closer look at those errors. I opened a case on for you--you'll hear back from our team soon!

Hi Alyssa, thanks for your help. I will investigate these issues separately (TalentLMS said it's an Rise problem).

I was wondering if anyone can share how to test the possibilities of xAPI with Rise courses.

Thank you :)

Hi Philippe!

I just peeked in on your case, and it looks like Renato has requested some information from you. I'll also share your question about testing the possibilities of xAPI with him. ☺️

Hi Alyssa, Renato investigated the issue, a solution consists of duplicating the course before an xAPI export. Scorm Cloud doesn't display errors anymore. However, the xAPI tracking display IDs and not activity names. I'll see if Renato can help :)

Hi, it seems normal that the statements display IDs as Justin Grenier from Articulate explained it.

Some LRSs like GrassBlade seem to be able to translate Articulate IDs to human readable names.

Will post my findings here :)

Hi,

I start to wonder if Rise is not including the wrong object id in its xAPI statement...

When a learner clicks on an custom activity, here is what I get in the LRS (same issue on scorm cloud) :

In the course's tincan.xml file, here is the activity definition :

Some part of the id is the same but it still differs...
I don't have such issues with Storyline xAPI packages.

What do you think ?

Thanks :-)

Hi Philippe!  Thanks for keeping us in the mix with all of your testing!

What you are seeing from the LRS is the activity ID tagged onto the endpoint URL of where the content is hosted.  The ID at the end of that URL appears to match what is stated in the tincan.xml.  We would expect, then, that the LRS is going to understand that ID and be able to match it to the .xml file.

Let me know if the reporting isn't working for you, and we'll have a deeper look!

Hi Crystal, thanks for your help.

The content is hosted on scorm cloud, I think think we see that in the URL from these screenshots.

I appears that the activity ID from the tincan.xml file is not exactly the one we see in the statement. Is it why the name is not retrieved ?

I'm not sure if I should submit a case or if I'm missing something here. With Storyline, I don't have such issue.

Thank you :)

Philippe,

  I did a project recently for the xapi cohort with Torrence Learning and found the same thing with Scorm Cloud.  Does it behave differently with different LRSs? I haven't seen whether anyone else has tested this.

  The engineers told me that this was expected behavior.  It really is not sustainable to use this if the statements aren't human readable!