Forum Discussion
SCORM Wrapper
I'm not sure if this is an Articulate issue, or something from Plateau/Success Factors, but here goes.
I'm publishing my Articulate 2013 course in SCORM 2004 v2 for deployment on our Plateau LMS....
Our IT team identified this issue: the SCORM package we exported from Rise no longer included the xmlns definition for adlnav. Therefore, the fix to both delete the terrible navigation button wrappers and make sure you don't get a content upload error that prevents you from uploading to SAP is this:
- Export SCORM 2004 v. 4 file
- unzip
- open imsmanifest.xml file
- edit as follows (using wordpad, not MS Word):
- Add the following text just below the SECOND <title> XXXXX </title>:
<adlnav:presentation>
<adlnav:navigationInterface>
<adlnav:hideLMSUI>continue</adlnav:hideLMSUI>
<adlnav:hideLMSUI>previous</adlnav:hideLMSUI><adlnav:hideLMSUI>exit</adlnav:hideLMSUI><adlnav:hideLMSUI>abandon</adlnav:hideLMSUI><adlnav:hideLMSUI>exitAll</adlnav:hideLMSUI><adlnav:hideLMSUI>suspendAll</adlnav:hideLMSUI><adlnav:hideLMSUI>abandonAll</adlnav:hideLMSUI>
</adlnav:navigationInterface>
</adlnav:presentation>
- Add the following text just below the SECOND <title> XXXXX </title>:
- Check if the identifier xmlns:adlnav=”http://www.adlnet.org/xsd/adlnav_v1p3 is present. If not, add this exactly (include quotation marks at end) in the xmlns definitions:
xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"
notably, we add this just after the line that starts with xmlns:imiss=... - Save and rezip the file
- Upload to SAP
*side note: this doesn't seem to be a change in the SAP software, but in what Articulate includes in the exported content package. Our IT department told us to follow up with Articulate to find out why this had changed.
This works 100% if you understand what is being said. Step 5 is where I suspect most people come apart.
To do all of this, here's what you should do.
Take your published Rise 360 .zip file and extract it somewhere.
Go into the extracted folder, and open/edit your imsmanifest.xml file (I recommend using Notepad++, it's great for this)
There are 2 parts to solving this problem.
- Adding the missing line to the top of your manifest file.
- Adding the code to your manifest file that hides those annoying buttons.
For Part 1 you need to check the very top section of the manifest file. If you compare a manifest file from Storyline 360 output with that of a Rise 360 output you will see there are some lines missing, most importantly, the xmlns:adlnav line that enables the hiding of the elements that we are trying to achieve:
Storyline 360<?xml version="1.0" encoding="utf-8" standalone="no"?><manifest identifier="wpwUr_cb_De7M3C2CYMXohGJzRe6cts1KGHj0ATy" version="1.3"xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"xmlns:imsss="http://www.imsglobal.org/xsd/imsss"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:lom="http://ltsc.ieee.org/xsd/LOM"xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsdhttp://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsdhttp://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsdhttp://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsdhttp://www.imsglobal.org/xsd/imsss imsss_v1p0.xsdhttp://ltsc.ieee.org/xsd/LOM lom.xsd">Rise 360<?xml version="1.0" standalone="no" ?><manifest identifier="wpwUr_cb_De7M3C2CYMXohGJzRe6cts1KGHj0ATy" version="1.3"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"MISSINGxmlns:imsss="http://www.imsglobal.org/xsd/imsss"xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsdhttp://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsdhttp://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsdhttp://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd">What you need to do is add that missing line (bolded) into your manifest file.That takes care of Part1Now you can add the hideLMSUI elements which then forces the LMS to hide those annoying buttons that appear in LMSs like SuccessFactors.Add the following code under the second <title> row of your Manifest file (In-between the 2nd <title> tag and the <adlcp:dataFromLMS> tag<adlnav:presentation>
<adlnav:navigationInterface>
<adlnav:hideLMSUI>continue</adlnav:hideLMSUI>
<adlnav:hideLMSUI>previous</adlnav:hideLMSUI>
<adlnav:hideLMSUI>abandon</adlnav:hideLMSUI>
<adlnav:hideLMSUI>exit</adlnav:hideLMSUI>
<adlnav:hideLMSUI>abandonAll</adlnav:hideLMSUI>
<adlnav:hideLMSUI>exitAll</adlnav:hideLMSUI>
<adlnav:hideLMSUI>suspendAll</adlnav:hideLMSUI>
</adlnav:navigationInterface>
</adlnav:presentation>Once this is done, save the manifest file, and rezip all the contents of the folder back into a .zip file.Import this "updated" zip file into your SuccessFactors LMS and it should work.Attached is a fixed example of a Rise 360 manifest file.Hope this helps anyone else struggling with this!HThanks Heinrich!
Hi Melanie, have you found a solution for CAM 1.3 ? Haven't seen any solutions for CAM 1.3 only SCORM 4TH Ed
Thanks Melanie -this resolved our issue. Like many others we're using SAP/SF LMS and we've decided to move our exams to a SCORM 2004 format. Editing the manifest removes the buttons so that students aren't confused.
