Time to see if everything works. I’m going to test my code using two different manifest files:
- A single SCO manifest file created by Captivate – [download manifest file]
- A multiple SCO manifest file that I created using Lectora – [download manifest file]
To be honest, I don’t think I’ve ever come across a multiple-SCO content package in a real application, but I do need to be able to handle it if I do stumble across it.
So let’s try the single SCO manifest file. When I run my manifest file reader, I get the following output.
| Identifier | Title | MasteryScore | LaunchData | SCO Entry Point | Required Files |
| P1 | Browser Options | 80 | Simulation.htm | Simulation.swf Simulation.htm SCORM_support/scorm_support.htm SCORM_support/scorm_support.js SCORM_support/scorm_support.swf |
This is what I’d expect from a manual analysis of the manifest file. So far, so good.
Now the multiple SCO manifest file. This is more challenging since, if you look at the manifest file itself, you can see that there are a host of linked resources, and that a number of the resources are shared by the two SCOs. So let’s give it a try – here’s what I get.
| Identifier | Title | MasteryScore | LaunchData | SCO Entry Point | Required Files |
| I_A001 | A001 | 75 | a001index.html | a001index.html a001content.html a001titlemgr.html a001_page_1.html a001_page_2.html images/backoff.gif images/backclk.gif images/backrol.gif images/homeoff.gif images/homeclk.gif images/homerol.gif images/nextoff.gif images/nextclk.gif images/nextrol.gif images/dlg-titlebar.gif images/dlg-close.gif apiwrapper11.js scofunctions.js trivantis.css dialog.css trivantis.js trivantis-timedate.js trivantis-cookie.js trivantis-dialog.js trivantis-button.js trivantis-inline.js trivantis-titlemgr.js trivantis-strings.js a001_page_3.html a001_page_4.html a001_page_5.html a001_test_a001_page_4.html images/std_qt_canceloff.gif images/std_qt_cancelclk.gif images/std_qt_cancelrol.gif images/std_qt_backoff.gif images/std_qt_backclk.gif images/std_qt_backrol.gif images/std_qt_nextoff.gif images/std_qt_nextclk.gif images/std_qt_nextrol.gif _tobj23.xml a001_test_a001_page_3.html a001_test_a001_page_1.html a001_test_a001_last_test_page.html images/std_qt_doneoff.gif images/std_qt_doneclk.gif images/std_qt_donerol.gif |
|
| I_A002 | A002 | 95 | a002index.html | a002index.html a002content.html a002titlemgr.html a002_page_1.html a002_page_2.html images/backoff.gif images/backclk.gif images/backrol.gif images/homeoff.gif images/homeclk.gif images/homerol.gif images/nextoff.gif images/nextclk.gif images/nextrol.gif images/dlg-titlebar.gif images/dlg-close.gif apiwrapper11.js scofunctions.js trivantis.css dialog.css trivantis.js trivantis-timedate.js trivantis-cookie.js trivantis-dialog.js trivantis-button.js trivantis-inline.js trivantis-titlemgr.js trivantis-strings.js a002_page_3.html a002_page_4.html a002_page_5.html a002_test_a002_page_3.html images/std_qt_canceloff.gif images/std_qt_cancelclk.gif images/std_qt_cancelrol.gif images/std_qt_backoff.gif images/std_qt_backclk.gif images/std_qt_backrol.gif images/std_qt_nextoff.gif images/std_qt_nextclk.gif images/std_qt_nextrol.gif _tobj42.xml a002_test_a002_page_1.html a002_test_a002_last_test_page.html images/std_qt_doneoff.gif images/std_qt_doneclk.gif images/std_qt_donerol.gif |
A lot more complicated but, comparing the output with the manifest file, it would certainly seem that I’ve successfully disentangled all of the dependencies, and identified the two SCOs.
All looking pretty good so far. Tomorrow I’ll post a copy of the manifest file reader code for you to download and play with.
Hi Steve,
I have a multiple SCO course that I uploaded to my LMS. When I launch the course the initial window opens and allows me to select the first SCO title. However, when I complete the first SCO and click exit it doesn’t take me back to the window with the SCO listings, it kicks me out of the LMS session? Is there something in the manifest file that I could change so that it just closes the current SCO and not the course?
Regards
Garry