default xAPI statements are calling the first page in a scene "home page"
Sep 06, 2023
Hi,
It looks like the default xAPI statements are sending incorrect data for the first page in a scene. I'm using Watershed LRS.
This is the data received on the LRS on opening the first page in a scene. It uses the page title as an UND tag and a random "Home Page" text. The first page of every scene is inserting this extra tag.
"object": {"objectType": "Activity","id": "urn:articulate:storyline:5qQfd1NIKmy/6oQlOapekVd","definition": {"name": {"en-US": "Home Page","und": "Training main page"},"description": {"und": "Training main page"},"type": "http://adlnet.gov/expapi/activities/module"}},
So some parts of the LRS are correctly reporting this as "Training main page", other parts are reporting as "Home page". This is causing a lot of confusion in the reports.
This is the data for another page in the same scene, which just uses the page title as an UND tag.
"object": {
"objectType": "Activity",
"id": "urn:articulate:storyline:5qQfd1NIKmy/5hGjUEuY0aW",
"definition": {
"name": {
"und": "NDP Video"
},
"description": {
"und": "NDP Video"
},
"type": "http://adlnet.gov/expapi/activities/module"
}
However, with a specific xAPI trigger on a button to open a layer and custom text, the text is in the EN-US tag, not the UND tag of the other statements.
"object": {
"objectType": "Activity",
"id": "urn:articulate:storyline:5qQfd1NIKmy/6oQlOapekVd/6rBndY43Az5",
"definition": {
"name": {
"en-US": "Executive Coaching"
}
Is there anyway to stop the two names for the same activity being generated by Storyline please?
Alternatively where is this "Home page " text coming from so I can overwrite it.
Also could you be consistent in which tag you use!
Thanks
4 Replies
Hi Karl,
Happy to help!
One troubleshooting step that you can do is to test how your course will behave in a different LMS such as SCORM Cloud. This test will help determine if the behavior is LMS specific. You'll find additional information for publishing Storyline 360 content in xAPI format here.
If you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
Hi,
I've tried to open a support case, but each time on clicking submit case I get a 404 page not found error.
TL;DR
Storyline is sending a spurious name tag "EN-US:Home Page" which is confusing reporting.
Detail
The first page of the first scene in the project is called "Home Page". However, the first page of every other scene in the project is also reporting the name as "Home Page" as there is an extra tag in the JSON.
Example
"object": {
"id": "urn:articulate:storyline:5qQfd1NIKmy/5skDonxK6n7",
"definition": {
"name": {
"und": "Support Engineering Home",
"en-US": "Home Page"
},
"description": {
"und": "Support Engineering Home"
},
"type": "http://adlnet.gov/expapi/activities/module"
},
"objectType": "Activity"
}
},
This "EN-US" tag does not exist in the first page of the first scene,
"object": {
"id": "urn:articulate:storyline:5qQfd1NIKmy/6HPFJAX8rgi",
"definition": {
"name": {
"und": "Home Page"
},
"description": {
"und": "Home Page"
},
"type": "http://adlnet.gov/expapi/activities/module"
},
"objectType": "Activity"
}
The EN-US is taking precedence over the UND tag in reporting, which results in 7 different IDs all being called Home Page. As there are different IDs I can write some custom reporting to fix it - but I can't expect end users to do that.
My guess is that when it was created the developer copied the scene, then renamed the slide. This has left a hidden tag.
I can't upload a JSON file here, but I can send it via other means (although not email as our system will strip it out)
Thanks
Karl
Hi Karl!
Sorry to hear that you hit a snag when trying to open a support case!
I went ahead and opened one on your behalf so you can connect with our support engineers. You're in excellent hands working with them and they should be getting in touch with you shortly!
Have a great start to your week!
Thanks