SCORM Root Activity and CC Root Folder

Coordinator
Sep 26, 2008 at 12:19 PM
In SCORM 2004 (an implicitly in SCORM 1.2) the manifest is used to build an "activity tree" that is typically represented as a "Table of Contents" rendered with a root directory that can be expanded/collapse to dispay descendent "directories" and "files". The SCORM 2004 specification is explicit that the "root" of this "activity tree" is built from an <organizations/> element in the manifest. For example:

  <organizations>
        <organization>
            <title>Root Activity</title>
            <item >
                 <title>Child Activity</title>           
            <item >
  </organization>
</organizations>

In the CC cartridges that are available, it seems that CC is taking a different approach to defining the "root folder" in a table of contents. For example, from the OU:

      <organizations>
        <organization identifier="ORG01" structure="rooted-hierarchy">
            <item identifier="ShellItem">
                <item identifier="FolderItem">
                    <title>Global Warming</title>
                    <item identifier="Forum1" isvisible="true" identifierref="Resource13">
                        <title>Unit Forum</title>
                    </item>
               <item >
           <item >
       </organization>
   </organizations>

So in the CC aproach the "root" appears to be a grandchild element of the <organization /> element, but in SCORM the root is the <organization/> element itself.

We will need to confirm this requirement for "rooted-hierarchy" and then implement the XSLT to transform the SCORM root activity to the equivalent CC root folder.