If you have to make Captivate-generated SCORM 1.2 content in your (web) platform and you want *more* information about what's going on, this guide might help. One of the trickiest things about Captivate and SCORM is that Captivate doesn't handle the credit/no-credit (cmi.core.credit) very well.
Extending a little bit on my latest post about howto test SCORM interactions in Dokeos, I'd like to add an important piece of information about our implementation of the SCORM 1.2 standard (and specifically the interactions). Although the SCORM 1.2 Runtime Environment documentation is not very clear about this, there are two "hints" that interactions IDs must start at 0, and not at 1. First, the description of the SetValue() method on cmi.interactions.n.id says:
Following my article on SCORM 2.0 White Paper call, and the kind personal invitation to contribute from Mike Rustici, I decided to go ahead and submit my list of suggestions to the SCORM 2.0 thinking process team just before the deadline (I've been quite busy on other stuff, including urgent personal matters). This is the first time ever that Dokeos contributes somehow (even though it's a very little piece of the enormous puzzle) to the design of an e-learning standard.
I just finished debugging one client's portal. For some reason, he couldn't see his SCORM content although he could see them in other LMS (Moodle, Claroline, ...). After spending 2 minutes checking the files and directories names, I realised he had stuff like this:
Act_Positive%20and%20negative/.as root SCORM path.
I thought I'll write a short update on what we are doing at Dokeos at the moment, so you don't think we're just sleeping through the summer holidays... Eric and Julian, of the French team, are currently working on a project for a specific hospital management school in France, and on a large and long-time review project before the migration of portals to version 1.8.5 for an important Belgian client.
I've had to review the SCORM content migration from 1.6 to 1.8 just today, and really, this is not something I'm enjoying.
LETSI, Learning Education Training Systems Interoperability, is entering a phase of study for the next version of SCORM, version 2.0. Of course, given the little level of adoption of SCORM 2004 (or 1.3), this might seem a little premature for some, but the making of such a large norm takes time, so it's probably better to get started early. The 2.0 version is said (in the announcement of the
I've mentioned SCORM before, but I didn't enter into the details.