About Directory Structure

[Jason L-S]

My project contains one main e-learning project, along with 9 lessons, 9 demos and 9 simulations. Each of those is a separate Captivate project. The main project contains links to them.

My question is about how to organize all this. If--in the future--we deploy this to a LMS, is it important to keep each subproject in its own subfolder to accurately track learner participation, etc.?

I'm not sure how uploading a multi-project system is handled by an LMS like Acobat Connect Pro.

[Erik Lord]

This may be heresey, but I'm not really sure Connect Pro is a full LMS.

No matter though...

For multi-'lesson' projects, just keep them separate and let the LMS handle the menu'ing and routing.

Publish each as it's own content package, upload separately to the LMS, and set them all up into one overall 'course', or whatever organization it offers.

Captivate does have the 'Aggregator' but I've not seen anyone have luck blending lessons together with it for use in an LMS. That's not to say it's not possible, but I've not seen that success (nor tried myself).

You could create a 'shell menu' with Flash that loads in the various components to make one overall lesson, but that shell menu then needs to handle the SCORM communication, lesson navigation, etc...

Does that help?

Erik

[Jason L-S]

Thanks Erik. That helps. I think the answer then is to keep everything in separate directories locally. Upload them separately to the LMS. And then let the LMS take care of the organization.