<p id="function(){return A.apply(null,[this].concat($A(arguments)))}" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" title="function(){return A.apply(null,[this].concat($A(arguments)))}" lang="function(){return A.apply(null,[this].concat($A(arguments)))}">The Multi-SCO tool is designed more specifically for LMSs in that it allows you to take two or more individual SCORM-compliant modules created in Captivate and package them all together into one big module for your LMS. The tool creates a new imsmanifest.xml file that lists all the component modules in the package so that the LMS can build it's own menu of links in its SCORM player. Users just click these links to launch each lesson module. Each lesson can have its own TOC if desired, but the menu of links in the SCORM player is all you get for a TOC that shows all modules. That's the way SCORM was originally designed to work.</p><p id="function(){return A.apply(null,[this].concat($A(arguments)))}" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" title="function(){return A.apply(null,[this].concat($A(arguments)))}" lang="function(){return A.apply(null,[this].concat($A(arguments)))}"> </p><p id="function(){return A.apply(null,[this].concat($A(arguments)))}" ondblclick="" onkeydown="" onkeypress="" onkeyup="" onmousemove="" onmouseout="" onmouseover="" onmouseup="" title="function(){return A.apply(null,[this].concat($A(arguments)))}" lang="function(){return A.apply(null,[this].concat($A(arguments)))}">The Captivate Aggregator on the other hand was designed to take multiple Captivate published outputs and merge them together in a single large project with a hierarchical merged TOC that listed the contents of all projects. I don't believe the original intention of the Captivate team was for aggregated projects to be used in LMSs but some Captivate developers have managed to get this to work by setting up all the individual projects as SCORMs and then hacking the imsmanifest.xml file to fool the LMS into thinking this was a single large SCO.</p>