We're finding more and more need for multi-SCO projects, and Adobe's packager is very limited. (Can't save the package?)
I'm wondering - reluctantly - about Reload Editor. The learning curve looks pretty steep. Has anybody used it, and does anybody know of any instructions for using it to chain Captivate swfs?
Thanks for any help!
Here's a recorded session that may help with the Adobe packager:
Here's one for exactly what you're asking about!
I'd love to know how it works out for you...
One more note - for Erik or anyone else. Does anyone know if, with Reload Editor, you can "nest" courses so they appear in several levels in the TOC after publishing? We have a LOT of files we want to group in a multi-SCO project, but we don't want to scare people by having them see them all at once, so we'd like to be able to collapse/expand courses to show sub-courses.
I think that would be a feature the LMS itself would need to support. I've never seen an LMS-based menu, one created from a multi-sco package, that had more than one level of lessons. I don't think the Reload Editor would allow you to structure that...as such support would probably be pretty unique to the LMS...
In our LMS, we'd probably handle this by creating multiple courses (i.e course 101, course 102, etc) then having the multi-sco package load the various lessons into the proper courses...just to keep them less daunting...
A multi-SCO SCORM package is one course. It cannot be a collection of courses. However, you CAN have a course with multiple SCO modules, and the SCORM standard allows you to specify sequencing rules in the manifest file to specify in what order (e.g. SCO A must be completed before you can open SCO B) or under what conditions (e.g. SCO A must be passed before you can attempt SCO B). This allows you to build in at least some kind of a hierarchy and structure.
I don't personally use RELOAD but I believe it does have some ability to build these structures into your manifest file.
At the end of the day though, it all has to be within one course, and the components will be modules of that course. The LMS defines your curriculum or collection of courses.
Thanks, Rod. I used the term "course" wrongly, probably. What I'm talking
about is combining modules that are now imported into the LMS as separate
courses, into a single "course" by treating them as separate SCOs.
Yes, thanks, I know about prerequisites, but that's not the answer I'm
looking for. I was hoping SCOs could be listed in the TOC in a tree
Even if you WERE able to define a hierarchy of SCOs, I think the way it would be represented would depend entirely on the abilities built into your LMS SCORM player.
All of the LMSs I've worked with only support one level of SCO hierarchy in their TOC.
Another related question about SCOs in Captivate. (We're dealing with SCOs for the first time.) Should the identifier in the SCO be different from the identifier for the course? If yes, should they be related, e.g. "O1" and "O11". Any suggestions for how to name the identifiers?
Thanks for any help...
Yes. I use something like MyFirstCourse as the Course ID and MyFirstCourse_01_ModName as the SCO ID for each module. This way you can always tell which course and course module you are dealing with, even if they should get separated for some reason. And it means they cannot get mixed up in the LMS either.
Europe, Middle East and Africa