This was the most helpful thing I've found so far concerning using xAPI in Storyline.

@DevlinPeckYT

Жыл бұрын

Glad to hear it! Thanks for the support.

Thank you for these replays. Very useful for those outside US timezones like me and also I get a chance to write notes and watch it over and over. Thanks, Devlin!

@DevlinPeckYT

2 жыл бұрын

You're welcome! Thanks for catching the replay :D

Thank you Devlin for all those wonderful resources.

@DevlinPeckYT

2 жыл бұрын

You’re welcome! Thanks for watching 😃

I can confirm for the benefit of the group that, at least in Blackboard, the "Actor supplied via launch URL" option captures the Blackboard username as the Actor in Veracity Learning LRS.

@DevlinPeckYT

Жыл бұрын

Thanks so much for confirming, James!

Hi Devlin, thank you so much for your sharing! I do have one question about the LRS setup. In your video 'Send an xAPI Statement from Articulate Storyline' uploaded 2 years ago, you disabled 'Read permission' when configuring the LRS (14:06 timestamp in that video). I followed that tutorial and I got an error message in the Storyline publish page that it 'Could not connect to your LRS endpoint'. I then found this more updated video and followed the instructions here. I noticed that the 'Read permission' is set as 'true' and I was successful in getting statements from Storyline in my LRS (Veracity Learning). May I know is there a reason for that change? Thank you so much for your time and sharing!

@DevlinPeckYT

Жыл бұрын

Hi, yes! If you include the LRS credentials in the JavaScript file (like with our custom approach in prev tutorials), then anyone who "inspects" the page could acquire those credentials. With read permission turned on in the LRS endpoint, they'd be able to query all of that data with those credentials...so it would essentially expose all of the LRS data to someone with basic web dev know-how. If you're managing the credentials on the LMS back-end then you should be secure + good to go :D

@sharonlearningdesign

Жыл бұрын

@@DevlinPeckYT Thank you so much for your clarification! I really like your tutorials!

I just want to put all these xapi statements into a s3 bucket, is it possible without needing to implement an LRS?

hello, please explain more about "Jason"! that you said we should first learn it? Since I am confusing about using xAPI... is it possible to you to provide short video to teach whole process of using xAPI statement in eLearning -FROM FIRST TO FINAL PROJECT- thanks so much Devlin!

@DevlinPeckYT

2 жыл бұрын

Good question! It is spelled JSON (that should help you find resources on it), and I have an xAPI tutorial series on the channel that dives much deeper into it :D

I was able to follow and duplicate the steps here -- great job of describing the process ! Now I'd like to publish the resulting course via Storyline to create a .zip file in xAPI format and then upload that .zip file to an LMS (say, SCORM Cloud) for testing. If I use Storyline to generate the .zip, it doesn't look like the .zip file includes the two external .js files (xapiwrapper.min and the file constructed in this video). So, if I upload to an LMS, the .js-related functions don't work. I tried to generate the .zip, unzip it, add the two .js files, re-zip it, and import to SCORM Cloud, but it throws an error ("file contained no courses"). I'm probably missing something blindingly obvious, but what's the method for importing this video's resulting content to an LMS that includes the two external .js files and the references to them in the story.html file? (Hope this question makes sense!)

@DevlinPeckYT

5 ай бұрын

This article and video might be helpful for connecting some of the missing pieces! Thanks for watching :) www.devlinpeck.com/content/how-to-use-lms

Thanks for this. Do you have any training on building custom dashboards and working with the data? I want to see more data display options besides the basic ones provided by the default dashboard.

Thank you for posting this. Is this all still pretty revelant and accurate for Storyline today (2024)?

@DevlinPeckYT

2 ай бұрын

Yes! this should still work, but you can check out Articulate's article on the topic if you get stuck: access.articulate.com/support/article/Storyline-360-Custom-xAPI-Statements

Hi Devlin. Fantastic video! I followed along with adding the result score variable around the 42 min mark. I have checked that my code is exactly the same as yours, but my LRS (ScormCloud) won't accept the score object (the statement doesn't even show in the activity stream) . If I delete the score object, the result works fine. I can pass a number instead of the variable as the raw score. Everything else is working as you demonstrated. Any other ideas?

@DevlinPeckYT

2 жыл бұрын

Hmmm...does it work with any other LRSs? Did you use a built-in variable by any chance?

@craigagnew2886

2 жыл бұрын

@@DevlinPeckYT Thanks for the reply. It was a custom variable (exactly the same as yours). I'll check using another LRS to see if that was the problem. Thanks again!

@jimmygalaxy1917

2 жыл бұрын

I have the same issue. I've tried two different LRS's and neither will accept the custom variable. I've moved the "result" verb to different locations within the statement, tried a built-in variable, same result. Remove the "raw" attribute or hard code a number and it works fine. Bug in Articulate? The LRS? no clue. I'm already invested in the initial LRS so my options are limited.

@jimmygalaxy1917

2 жыл бұрын

Figured it out, use the Number() function. ie: "raw": Number(myVariable)

Send the static mailbox lack of uniqueness for the variables to Storyline's dev team. That's a miss on their part. Tell them to make dynamic accounts.

@DevlinPeckYT

2 жыл бұрын

Yeah, we will see how they progress with this! Hopefully it gets more useful :D