Friday, 13 November 2009

SCORM 2 CC

~ This page describes the experience of converting existing SCORM content to IMS Common Cartridge format~

In this blog entry I am going to describe the process for converting training content from the ADL SCORM 1.2 format to the IMS Common Cartridge 1.0 format - using software tools from Icodeon and from the IMS Common Cartridge Alliance.

The final result is shown below - a launch button embedded into a web page that launches the content into a new browser window:

~ Webcontent Launch Tool from Icodeon CC Platform ~

These are the steps:

  • First, I downloaded the freely available SCORM to Common Cartridge Converter called SCORM2CC from the Codeplex Open Source site. The software is Windows only, and comes with an installer that downloads any dependencies that might be missing on your system.

  • Next, I chose a SCORM package .zip file that I wanted to convert and ran it through the SCORM2CC tool. The tool outputs a directory and a .zip file of exactly the same name as the original SCORM .zip file - so make sure you do not get mixed up between the original SCORM .zip file and the new Common Cartridge .zip file!

  • To check that everything had been converted correctly I downloaded the Common Cartridge Conformance test tool which is available if you first sign up and join the IMS Common Cartridge Alliance. I ran the new Common Cartridge .zip file through the tester - and received a report that said no errors. So far so good! (...but see my comment later: the original SCORM package manifest did not include all the required references to dependent files...).

  • Then I uploaded the newly converted and tested Common Cartridge .zip file to the web based Icodeon Common Cartridge Platform and launched the content in the Cartridge Explorer tool. Everything looked great until I tried to run a few SCORM API calls - which gave errors. On further investigation it turned out that the source imsmanifest.xml in the original SCORM package did not list all the files in the package - there were some

    <resource/>
    
    XML elements missing file dependencies.

  • So the SCORM2CC tool trusts the original source manifest to list all the dependent files - and if the original manifest is not being completely honest about all the resources it needs, then the new Common Cartridge .zip file will be missing these dependent file also. So keep an eye out for that!

  • Finally, I wanted to integrate the launch of one of the SCORM learning objects (the "SCO"s as they are called) into a web page (actually this page), so I used the embed tool in the Icodeon Cartridge Explorer tool.

    To do this I first generated an API key on the Icodeon Cartridge Platform for the domain where I wished to launch the SCORM learning object (this sub-domain actually, which is called "ccplatform.blogspot.com") and then used that API key in the embed tool to generate an HTML tag like this:

<!-- add this tag to your page -->
<script type="text/javascript" 
src="http://www.common-cartridge.com/cartridges/
SCORM_Detective_1p2/items/ITEM1
/webcontent.js?_api_key=my_api_key"></script>
  • If you look carefully you can see the URL address conforms nicely to the Icodeon CC Platform URL Language - you can find out more about that language here.

http://{host}/cartridges/
{cartridge}/items/{item}/{resource}.{ext}
  • So once the HTML tag had been generated with the correct API key, all I had to do was add the single HTML tag to the webpage (this page actually) and voila! - a launch link was written to the web page.

  • SCORM 2 CC done.

  • Have you converted SCORM to Common Cartridge? Why not add your comment on your experiences on this blog?

1 comment:

  1. interesting blog. It would be great if you can provide more details about it. Thanks you

    Scorm E Learning

    ReplyDelete