Forum Discussion

NatalieSantos's avatar
NatalieSantos
Community Member
3 years ago

Rise 360 - imsmanifest file includes headers throwing a 404 error

I have published a Rise 360 as Scorm1.2 for LMS. I have noticed that the imsmafest.xml file includes the following headers:


<manifest identifier="yntZxa0dTrj4nXCFktOIARPJKykZZf4os3yR04Qj" version="1" xsi:schemaLocation=http://www.imsproject.org/xsd/imscp_rootv1p1p2 imscp_rootv1p1p2.xsd http://www.imsglobal.org/xsd/imsmd_rootv1p2p1 imsmd_rootv1p2p1.xsd http://www.adlnet.org/xsd/adlcp_rootv1p2 adlcp_rootv1p2.xsd>

Those addresses all return 404 not found errors:
http://www.imsproject.org/xsd/imscp_rootv1p1p2 imscp_rootv1p1p2.xsd
http://www.imsglobal.org/xsd/imsmd_rootv1p2p1 imsmd_rootv1p2p1.xsd
http://www.adlnet.org/xsd/adlcp_rootv1p2 adlcp_rootv1p2.xsd

These urls are generated by default when I publish the Rise file. Can someone explain why they are generated?

Would appreciate the assistance.

Thank You

  • Natalie's original question was:

    Why is Rise generating scorm packages that contain links to addresses that return 404 not found errors.

    Can you explain why that's happening?

    • LeaSAgato's avatar
      LeaSAgato
      Staff

      Hi Luis and Natalie!

      Those addresses found in the imsmafest.xml file are essentially instructions to the LMS on how to read the special formatting or version of the xml document.  It's part of SCORM specifications and not really related point to any course data.  I hope this helps!

       

  • By the way, Natalie, I wanted to let you know that your comment will include your email signature why you reply to a thread via email. Please feel free to edit out your personal info here if desired.

  • Ok, getting my head around this...

    The http://www.imsproject.org/xsd/imscp_rootv1p1p2 address in the imsmafest.xml redirects to https://www.imsglobal.org/sites/default/files/xsd/imscp_rootv1p1p2.xsd

    Great!

    And the http://www.imsglobal.org/xsd/imsmd_rootv1p2p1 address in the imsmafest.xml redirects to https://www.imsglobal.org/sites/default/files/xsd/imsmd_rootv1p2p1.xsd

    So that makes sense...

    But the last one, http://www.adlnet.org/xsd/adlcp_rootv1p2 redirects to a 404 page not found message. So presumably the scorm package doesn't get to load the adlcp_rootv1p2.xsd file - aka the SCORM Content Aggregation Schema - because the above address is wrong. What impact does this have on the scorm package? Could this result in the LMS (Moodle) not being able to load the scorm package correctly - resulting in a blank white screen being displayed when a user opens the scorm activity?

    • Crystal-Horn's avatar
      Crystal-Horn
      Staff

      Hi there, Luis. The .xsd references in the manifest refer to file types that historically enabled additional features for SCORM output. Because we aren't using those features for Rise 360 output, we don't use these files at all. You shouldn't see an issue solely because those files are included in the manifest.

      I see my team is working with Natalie on the Moodle issue. Currently, we're looking at tidying up the overall manifest and SCORM output to reduce package size, so this is a really timely question!

  • How can we update the imsmanifest xml file to hide the adlnav buttons for a RISE SCORM 2004 4th ed course? We used the following in the imsmanifest xml file for a course published from StoryLine and it worked just fine. However, this same code does not appear to function as expected when inserting it into the manifest file from a RISE course. Any ideas? Does anyone have a copy of a manifest file from RISE with the buttons hidden?

    <adlnav:presentation>
    <adlnav:navigationInterface>
    <adlnav:hideLMSUI>continue</adlnav:hideLMSUI>
    <adlnav:hideLMSUI>previous</adlnav:hideLMSUI>
    <adlnav:hideLMSUI>exit</adlnav:hideLMSUI>
    <adlnav:hideLMSUI>exitAll</adlnav:hideLMSUI>
    <adlnav:hideLMSUI>suspendAll</adlnav:hideLMSUI>
    <adlnav:hideLMSUI>abandonAll</adlnav:hideLMSUI>
    </adlnav:navigationInterface>
    </adlnav:presentation>

  • Hi folks, quick update! We've released a change to our file structure for Rise 360 LMS packages. We've cleaned up some unnecessary files, including a lot of .xsd files that we talked about earlier in this discussion. 

    Feel free to reach out to us here if you have specific questions about your output's performance in your learning management system.