Skip to main content
ruthg84
Known Participant
January 4, 2017
Question

Building an Index from Several Captivate Projects

  • January 4, 2017
  • 1 reply
  • 742 views

Hi,

I am creating a proofreading and editing course in Captivate 9 (9.0.2.437) and want to build an index that lists all the slide headings from all the different SCORM projects (there will eventually be about 14 different Captivate projects in all). I would like this index to sit on the hosting site (Talent LMS) and to be interactive- so that a user could click on a title and be taken to the correct slide.

Is there a way to create an index that hyperlinks to several different captivate projects?

Best,

Ruth

    This topic has been closed for replies.

    1 reply

    RodWard
    Community Expert
    Community Expert
    January 4, 2017

    What you're describing here is not really allowed by the SCORM standard as each separate SCO is not supposed to call anything outside itself.  The LMS launches each SCO in response to the user's actions clicking the link provided by the LMS to launch that module or course.

    If all of these modules belong to a single course, you can use the Multi-SCORM Packaging tool that comes with Captivate to bundle them all up into a single multi-SCORM course.  If your LMS is able to handle multi-SCORMs then it will create a Table of Contents in the SCORM player with links to launch each of the component SCOs.  But it will not create links to individual slides below that level of the SCO.

    ruthg84
    ruthg84Author
    Known Participant
    January 4, 2017

    Thanks. That's a shame. Can I suggest this functionality as a future development?

    RodWard
    Community Expert
    Community Expert
    January 5, 2017

    Go for it!  But telling anyone here isn't regarded as logging the enhancement request.  You need to log it via this form:

    Adobe Captivate

    However, since the main restriction is really with the SCORM standard rather than with Captivate, you might still find yourself out of luck.  I suggest you investigate the new xAPI (Tin Can) LMS integration standard that is (very gradually) replacing SCORM.  If your LMS is an LRS as well and can support this newer standard then maybe you should be using that.