Branching to multiple projects within a SCORM-compatible LMS
I'm close here, but I'm not quite getting what I want. Hopefully someone can point to the "easy" way to do this...
I am creating a single course that is composed of multiple Captivate 5 projects. The user is branched to different projects along the way based on the answers to embedded questions (such as passing/failing a pre-test). In the final project I have a post-test. That's the only one that needs to send a score to the LMS.
So let's simplify it for an example:
- User enters in Module 1 and takes a pre-test.
- If they pass with a certain score, they go to Module 3. If they fail, they go to Module 2.
- If they're sent to Module 2, they go to Module 3 after they complete it.
- In Module 3 they take a post-test and that score gets recorded.
Running this scenario on my desktop is easy. Putting it in a SCORM environment is taxing my brain.
Currently, I'm publishing each Module as its own SCO, keeping the Course ID and Title consistent between them.
I tried using the Multi-SCO Packager, but that results in entries in my LMS for Module 1, 2, and 3 separately. Not what I want.
I have tried moving the folders for Modules 2 and 3 to make them sub-folders of Module 1. That seems to work (I get one course entry point, for Module 1, and I exit with the correct score from Module 3), however in reviewing the LMS reports, this results in an artificially elevated "# of accesses" figure. The reason seems obvious: every time I load Module 1 it's one access, and then when I branch to Module 3, it's another access, because really I'm reloading the page with a new module and SCORM manifest, right? Plus I'm a little worried that this kind of gerry-rigging is going to break something.
I don't really want to use the Aggregator, because I don't want a TOC - they shouldn't have the ability to jump directly to Module 2, for example - but I tried it anyway. And I found that even if I can get it to flow the way I want to, I can't figure out how to package the Aggregated project into a SCORM Manifest.
There's got to be a way to do this. What am I missing? Is there something obvious I'm not considering?
