Tiny Timeline Tidbits – lilybiri’s posterous
Tips and shortcuts for the Captivate timeline
10 eLearning Freebies: Instructional Design and eLearning: Tips, Advice and Reviews
Free templates, sound effects, graphics, and more
Resources from my presentation at Innovations in e-learning Symposium | Kapp Notes
Research highlights on learning with avatars, games, and simulations
What Does Your e-Learning Yield?
A great analogy to use when someone asks you to create e-learning in an absurdly short time like a week.
This is only possible by concluding that the only time necessary to create e-learning is that which is physically required to manipulate the tools to translate content onto the screen. That thinking applied to my strawberry crop would go something like this:
I want us to start having strawberries, and I think we would benefit from producing about six quarts. I see that over at Edwards Berry Patch it takes about 5 minutes to pick a quart of strawberries. So since we need six, you should be able to get them for us in about a half hour.
It’s utterly ridiculous; it ignores the fact that it took a year’s worth of effort to make that strawberry production possible.
Adobe Forums: Creating one LMS Scorm package from…
Discussion on how to daisy chain multiple Captivate projects into one big project. Includes a comparison of Aggregator projects versus Multi-SCORM
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.
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.
Posted from Diigo. The rest of my favorite links are here.