Forum Discussion
SCORM 1.2 Question Text
I've noticed that our LMS, (SABA) has a field cmi.interactions.n.text that accepts the question text of a slide. Is there any way we can get Storyline2 report the question text to the LMS in this field?
Thanks
25 Replies
- ChristiePollickCommunity Member
Hi, Dave -- Thanks for reaching out with your question! While I cannot speak on using SABA personally, I know we have quite a few SABA users here in the community, so hopefully someone will be able to stop in to offer additional assistance here. :)
- DaveCox-67b3049Community Member
This isn't a SABA issue, but a Storyline issue. Storyline is not forwarding the question text to the LMS.
- BrianAllenCommunity Member
Are you publishing for SCORM 2004? Just wondering if that makes a difference... going to have to do a little testing in our LMS to see if we have the same issue.
- ChristiePollickCommunity Member
I see, Dave -- thanks so much for the clarification! Would it be possible for you to share your file so we might take a closer look?
- DaveCox-67b3049Community Member
I have tried both SCORM 1.2 and SCORM 2004 with the same result. I have a captivate module that reports the question text just fine.
I can send an example of the Scorm logs in the morning. You should be able to duplicate this with any question slide.
I think that this may be a question for your Scorm protocol expert.
Thanks.
- PhilMayorSuper Hero
Hi Dave
In scorm 1.2 Articulate does not send the question text. IN Scorm 2004 it does send the question text https://www.articulate.com/support/storyline/quiz-data-sent-to-an-lms-in-articulate-storyline
I have seen the question text appear in Kallidus LMS, but have never used scorm 2004 in SABA to test this.
- DaveCox-67b3049Community Member
Thank you Phil. You are correct, SCORM 2004 does send the question. I didn't see when when I tried it before becuase I was looking for the wrong parameter. SCORM 2004 puts the value in CMI.interactions.n.description. I was expecting it in CMI.interactions.n.text, which is where Captivate appears to put it.
Thanks for the help with that.
- BrianAllenCommunity Member
This is very helpful to know... Seems like every LMS stores SCORM interaction data differently.
After your post I had started looking at some of ours in our SumTotal LMS and had noticed that it looked like we had question text for 2004 but none for 1.2, so I thought there was something to it...
- MattMayerCommunity Member
Hello Dave,
We also use Saba and have the same issue. It is a SCORM 2004 vs SCORM 1.2 articulate issue. It has nothing to do with Saba. I have had Saba IT pull the files apart and there is no field for.text or .descrption in a SCORM 1.2 quiz published from STORYLINE nor Quizmaker '13.
Did you say that Captivate enables these fields in a SCORM 1.2 Quiz?
We are publishing course for Mobile, and SCORM 1.2 is only available on Mobile, however we need this data set, so we are not able to publish such quizzes for mobile at this time.
- PhilMayorSuper Hero
Matt is the mobile limitation a Saba limitation? there should be no reason why the Scorm 2004 version won't play on mobile devices.
- MattMayerCommunity Member
I believe it may be an LMS limitation. We used to use SumTotal LMS and they did not accept SCORM 2004 on Mobile, and on Saba LMS, and they too do not accept SCORM 2004 on Mobile.
- DaveCoxCommunity Member
I discovered that SCORM_2004 wouldn't work with SABA. I couldn't get it to report any scores at all. We reverted bact to SCORM 1.2.
To solve the problem, I patched the SCORMFunctions.js to send the required text to SABA. Since SABA looks for the question in a text field, I'm sending the information to the value text instead of description. I've updated all of our courses with this patch, and it has been working fine since.
This file is in your packages lms folder.
I added this code after the line: "//ignore the description parameter in SCORM 1.2, there is nothing we can do with it"
if (strDescription != undefined && strDescription != null && strDescription != ""){
blnResult = SCORM_CallLMSSetValue("cmi.interactions." + intInteractionIndex + ".text", strDescription) && blnResult;
}
I'm attaching a copy of the patched file for you here.
I hope that this helps,
Dave
- MattMayerCommunity Member
Thanks Dave! We will test.
- DustinBauman-02Community Member
Dave,
Thank you very much. After working on this for a good while, thinking maybe it had something to do with the stacking order in SL, I found this article. After seeing that the interactions.X.text field was blank and seeing that you had figured this out, I tested and it works perfectly. Thank you very much for sharing this.
Related Content
- 10 years ago
- 8 months ago
- 10 months ago