Skip to main content
Alex-House
Alex-House
Participant
April 7, 2016
Answered

Captiavte 9 Linking Multiple Projects in Multi SCO packings

  • April 7, 2016
  • 1 reply
  • 749 views

Hey everyone,

I'm currently trying to link several Captivate projects together and then package them into one SCORM file with the Multi SCO packaging. My issue is the linking between projects is not working correctly. In some cases I will just be presented with a white screen, in other tests it will go to another slide but will not navigate back or I will receive an error:

"An error has occurred: Error initializing communications with LMS Press 'OK' to view debug information to send to technical support."

So to backup a little bit. I'm using Captivate 9, Publishing each project as SCORM 1.2, Packaging using 'Multiple SCOs', to be deployed on Moodle.

I have 4 files, the first is the landing page that has 3 buttons that each need to link to a different captivate project. The remaining 3 projects have a button that links back to the landing page.

I've played around with making the buttons open the project file or open a url / file. I still don't think they are linking together correctly,

I would really appreciate it if anyone could explain the process of linking the projects together so the links will still work when they are packaged together in one SCORM.

Thanks very much

This topic has been closed for replies.
Correct answer RodWard

Your problem is related to your attempting to use a menu project to launch the other three modules directly. SCORM objects are not supposed to be linking directly to each other.  The SCORM standard actually prohibits it (in theory) stating that all SCOs should be standalone.

Even though your approach MIGHT have worked with some LMSs, with a Multi-SCORM course your user is supposed to launch each module using the links provided in the LMS SCORM player.  This will ensure the LMS sets up the proper communication with the SCO via the SCORM JavaScript API.

However, Moodle has a particular way of delivering each SCO when it is called that usually breaks any attempt to do what you are trying to do.  Moodle stores all the course files in a directory on the server that is usually NOT able to be linked to directly via a HTTP link or relative link.  When your user clicks a link to a given course module's HTM file, it then fetches those files and copies them into a temporary director on the server so that the learner can view them in their browser.  But this means that the content cannot link out to another sibling module because they are all still back in the other folder on the server, not in the same temp folder.

1 reply

RodWard
Community Expert
RodWardCommunity ExpertCorrect answer
Community Expert
April 7, 2016

Your problem is related to your attempting to use a menu project to launch the other three modules directly. SCORM objects are not supposed to be linking directly to each other.  The SCORM standard actually prohibits it (in theory) stating that all SCOs should be standalone.

Even though your approach MIGHT have worked with some LMSs, with a Multi-SCORM course your user is supposed to launch each module using the links provided in the LMS SCORM player.  This will ensure the LMS sets up the proper communication with the SCO via the SCORM JavaScript API.

However, Moodle has a particular way of delivering each SCO when it is called that usually breaks any attempt to do what you are trying to do.  Moodle stores all the course files in a directory on the server that is usually NOT able to be linked to directly via a HTTP link or relative link.  When your user clicks a link to a given course module's HTM file, it then fetches those files and copies them into a temporary director on the server so that the learner can view them in their browser.  But this means that the content cannot link out to another sibling module because they are all still back in the other folder on the server, not in the same temp folder.

Alex-House
Alex-HouseAuthor
Participant
April 7, 2016

Thanks very much for the reply Rod.

Think I'll have another go but this time do it outside the LMS, avoid scorm and just link the html output files and see how it goes.

Reporting was a nice to have at this stage, although disappointing it's not going to work.

Thanks again!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices