Table of Contents

Potential Pitfalls

...

As mentioned on the Import SCORM Courses the only version support by our LMS is version 1.2.  This can be checked by opening the imsmanifest.xml in the root of the zipped SCORM package.

In the <metadata> tag there will be a <schemaversion> which should be 1.2.  If the version is incorrect, the client/vendor must re-package the course using the correct version:

...

Note: Reserved html characters should be viewed with suspicion.  To fix this issue, remove the offending characters, and re-zip the packaged files with a new name, and re-import the course to the LMS.

No Error (infinite loading) alternative

We have also seen rare instances (e.g. NCLH) of Scorm course making external calls.  Normally this is not supported, but we have made exceptions (specifically for NCLH).  This can be seen in the Network trace in the developer window. It will manifest as 403 or 404 errors, and in rare cases, a Content-Security-Policy exception:
Image Added

Note this has been fixed on NCLH by changing the CSP to use frame-src instead of script-src and whitelisting cloud.scorm.com. Additionally, this must be tested with https as external sites (e.g. cloud.scorm.com) will rejected an unsecured http request. Use hotbackup for testing.

Course Is Not Viewable By Students

There is currently an issue on 4.2.x with the importScorm command, caused by 

• After running importScorm, navigate to the course itself (final link).
• Before changing the template to the SCORM course template as you normally do, you need to Edit > Links > Publish the link.
  Image Added
• Then you can change the template to the proper SCORM template. (Edit > Page > Change Template)

Currently the SCORM templates (at least SCORM.Course.Simple.cshtml) don't seem to be aware of this and so no error is shown anywhere in the console or network trace.