SCORM Wrapper

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:

1. Export SCORM 2004 v. 4 file
2. unzip
3. open imsmanifest.xml file
4. edit as follows (using wordpad, not MS Word):
   1. 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>

5. 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=...
6. Save and rezip the file
7. 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.