2004-04-14 10:34:36
I am using ATutor 1.3.3. I am trying to import a Scorm package, but I keep getting the following error
"IMS manifest file is missing. This does not appear to be a valid IMS content package."
I have imported the same package to a commercial LMS without any problems.
Any ideas?
thanks,
Luis
2004-04-14 17:27:18
I'm not aware of a commercial system that has implemented the current IMS/SCORM content packaging specification yet. Most are working with IMS CP1.1.2 or earlier, which had some major flaws. ATutor only supports the current specification (IMS CP 1.1.3).
Packages created with Reload and ATutor are interoperable, and Reload does support older specs. So you might be able to import your packages into Reload, then export them again using the new spec. Then try importing into ATutor. We'd be interested to hear if this works or not.
Reload
http://www.reload.ac.uk/
We, and the Reload folk, have both had trouble with content packages from a couple of the big commercial systems. It might be that propriatary markup is breaking the conformance of their packages. Investigating is on our todo list, but it may be a while before we can get to it (its a long list).
If you can send us a copy of the imsmanifest file that came with your package, we might be able to track down the exact problem. (or even send a whole package if its not too big: eg < 1mb to info/AT/atutor.ca)
2004-04-16 09:39:07
Here's the imsmanifest.xml
<?xml version="1.0"?>
<manifest identifier="SaturnCourseManifest" version="1.0"
xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2"
xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_rootv1p2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
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">
<organizations default="SB1">
<organization identifier="SB1">
<title>Saturn Service Parts Operation</title>
<item identifier="SS1" identifierref="index" isvisible="true">
<title>Hazardous Part Shipping Awareness</title>
<adlcp:masteryscore>70</adlcp:masteryscore>
</item>
<metadata>
<schema>ADL SCORM</schema>
<schemaversion>1.2</schemaversion>
<adlcp:location>course.xml</adlcp:location>
</metadata>
</organization>
</organizations>
<resources>
<resource identifier="index" type="webcontent" adlcp:scormtype="sco" href="index.htm">
<metadata>
<schema>ADL SCORM</schema>
<schemaversion>1.2</schemaversion>
<adlcp:location>course.xml</adlcp:location>
</metadata>
<file href="index.htm" />
</resource>
</resources>
</manifest>
The package is available but it is around 10Mb.
thanks,
Luis
2004-04-19 07:22:17
I am having a similar problem importing pre-packaged content.
While it is possible that the changes in packaging specification are causing a problem, it seems that the main problem is the way that ATutor handles the contents of html files in the package.
The packages I am trying to import make extensive use of scripts and css references all in the <head> part of the html file. Some also use framesets.
From the way ATutor handles these pages it seems that all the code outside the <body> tags is lost. As a result the stylesheets are lost and frameset pages appear blank.
I have dabbled with RELOAD to convert the packages to the latest SCORM spec, but this does not address the fundamental problem with the way the pages are rendered.
Am I missing something in the way I am loading the packages?
Jim
2004-04-19 14:59:05
This manifest is based on the old specification. You'll nned to upgrade it to IMS CP 1.1.3
[reply][b]In reply to:[/b]
Here's the imsmanifest.xml
xmln...
[op]forums/view.php?fid=7;pid=1502;page=1#1515[/op][/reply]
2004-04-19 15:29:11
I don't know the nature of the scripting in your pages, but if its SCORM SCO scripting, ATutor does not support SCOs, primarily because of their reliance on embedded Javascript. Javascript is problematic from an accessibility perspective, and embedding it within SCOs is a flaw of the SCORM specification. In the SCO sense, scripting should be a function of the LMS rather than the content. In many cases you can relocate scripts embedded in the head within your content pages if needed.
ATutor doesn't use frames or display framed content, but such content could be uploaded as a zip file with the filemanager, unpacked there, then the main frameset page linked from somewhere for students to access independant of ATutor. Frames can also create accessibility problems, and unless the content of ATutor were displayed in a frame or iframes it would not be possible to display a frameset within ATutor. Frames should not be used in content packages. They can be used to display the content within a package as ATutor does, but they should not be part of the content itself.
[reply][b]In reply to:[/b]
I am having a similar problem importing pre-packaged content.
While it is possible that the changes in packaging specification are causing a problem, it seems that the main problem is the way that ...
[op]forums/view.php?fid=7;pid=1502;page=1#1520[/op][/reply]
2004-04-26 16:24:48
this may sound silly.. but how does one upgrade the schema?
2004-04-26 18:38:02
...good question, actually.
I'd suggested a while ago that someone try converting older content with Reload. I've now had a chance to try this myself and could not find a way to reformat packages to the newer specification. Reload recognizes the specification of each imported package, and lets you build content within one specification, but it does not provide a way to convert between specifications.
See if the Reload people can provide any guidance...
http://www.reload.ac.uk/
[reply][b]In reply to:[/b]
this may sound silly.. but how does one upgrade the schema?
[op]forums/view.php?fid=7;pid=1502;page=1#1554[/op][/reply]