Storyline SCORM 2004 packaging error

Hi all,

I've been publishing a Storyline file for SCORM 2004 3rd edition using Storyline's publish for LMS feature. I've encountered a weird behaviour: the imsmanifest.xml file never seems to be valid. Here's an excerpt from the file:

<manifest

xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd

http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd

http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd

http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd

http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd>

Notice at the end of four of the lines there is " " (which is an HTML Encoded line feed character). I've never seen these before in an imsmanifest.xml file. When I remove these characters and re-ZIP the files, my files validate.

This seems really bizarre and I was wondering if anyone else has had the same problem or could offer ideas on a fix.

I'm using Storyline update 3: 1305.2012 on Windows 7.

Grateful for any help.

11 Replies
Stimpson Cat

Hi Leslie, thanks for your reply.

I'm testing on a range of LMSs, but ultimately it's being deployed on an in-house LMS. At run-time it has no effect on the operation of the course, which is good. Reporting is OK as well.

I'm getting the error:

  • on ADL's SCORM 2004 3rd edition test suite the imsmanifest fails the content package conformance test at the lines with the line feed character strings
  • on a local instance of Ilias, where it fails the validation step of the publish process.

I've tested on SCORM Cloud, and at publish and run-time there are no errors. However, I don't know if SCORM Could validates the files at any stage.

I've used the ADL test suites for a while now and have never seen this particular error. Ordinarily I would remove the errant characters as part of best practice, but since various people will be producing Storyline-authored SCOs this won't be done all the time.

Since there are only validation errors perhaps this thread should be changed to a bug report.

Justin Grenier

Aidan, can you share how this is impacting you?  Is this (like Stimpson above) only a failure within the ADL SCORM Test Suite, or is this also causing a failure within your LMS?  If it's causing a problem in your LMS, what LMS are you using, and what specific problem is it causing?  We'd like to get a clear picture of the impact this is causing.

Thanks!