Skip to main content
RodWard
Community Expert
RodWardCommunity Expert
Community Expert
July 1, 2014
Question

Multi-SCORM Packager Takes the SCO Title from the wrong field

  • July 1, 2014
  • 1 reply
  • 912 views

I think I've just stumbled across a huge bug in the Cp7 Multi-SCORM Packager tool.  Can anyone else confirm seeing this same issue?

I have a multi-SCORM course with several modules.  Each SCO is set up in the LMS Manifest dialog with a unique ID in the SCO Identifier field (e.g. My_Course_Module_ID) and the SCO Title field underneath has the correct name of the same module (e.g. My Course Module).  When published to SCORM zip files the imsmanifest.xml files for these modules are correct.

However, I've just discovered that when packaging up a number of these SCORM modules using the Multi-SCORM Packager tool, the resulting imsmanifest.xml file it produces is NOT using the SCO Title. When uploaded to an LMS the SCO Title shown in the LMS TOC seems to be whatever had been used as the Project Title field text in the Publish dialog at the time the SCO was published.

Here's the issue: The Publish Title field ends up being used for the file names of the output.  So if you use a Project Title such as: My Course Module it will mean your HTM and SWF output file are named as My Course Module.htm and My Course Module.swf.  The problem with this is obviously that the spaces in the filenames mean you cannot use them on the web.  So, I normally use a lowercase name with underscore characters in the Project Title field (e.g. my_course_module) to ensure the output is web-compatible (e.g. my_course_module.htm, my_course_module.swf).

It doesn't matter whether you are publishing for SCORM 1.2 or 2004, the result is the same. The TOC in the LMS comes out with the wrong text string.  The issue with this bug in the Multi-SCORM Packager taking the Title attribute for the imsmanifest.xml from the wrong dialog field means that the TOC strings displayed in the LMS are incorrect.  So far I've found no way to resolve this issue other than manually modifying the combined imsmanifest.xml.

Has anyone else seen this issue?  Can Adobe confirm if this is a known bug/issue so that I know if I need to log it or not?  Is there a fix or workaround (other than manually editing each and every imsmanifest.)

    This topic has been closed for replies.

    1 reply

    shriyanshagnihotri
    shriyanshagnihotri
    Participating Frequently
    July 1, 2014

    Hi Rod,

    I am not able to re-produce the same issue on my end. Please share following to my id (agnihotr@adobe.com) for further investigation.

    1) Sco zip package.

    2) new Sco package screen shot (means the fields that you filed while creating sco)

    3) all projects cptx and also published output.

    In our end we are getting correct sco title and name on TOC as well as on imsmanifest.xml of sco content when pushed to scorm cloud.

    Regards

    Shriyansh

    Adobe Captivate Team.

    RodWard
    Community Expert
    RodWardCommunity ExpertAuthor
    Community Expert
    July 1, 2014

    Shriyansh,

    Are you using the Cp7 version of the Multi-SCORM Packager or the Cp8 version?  I'm talking about the Cp7 packager app.

    I've tried this Cp7 SCORM Packager on two different machines installed a year apart and they both do the same thing.

    Here is my Manifest dialog settings:

    Note that what I'm expecting to see in the TOC of the LMS SCORM Player is the Title field name of the SCO (About Working in Courts in this case).  But what I'm seeing appear is actually not that field, and it's not even the SCO ID field above it.  (I tried changing that field as well to see if its value was what ended up getting written into the imsmanifest.xml for the multi-SCORM package.)

    What ended up being used as the Title of the SCO in the package turned out to be the contents of the Publish dialog's Project Title field.

    I verified this by changing the values in this Project Title field for a couple of SCOs, published them to zips and then compiled them into a Multi-SCORM.  THEN  I was seeing those values in the TOC of the LMS player.

    Currently, when I create a Multi-SCORM Package with the Cp7 app, here's what I see in the Title tags of the Organizations block:

    As you can see above, what's coming out is NOT the SCO Title tag value from the Manifest dialog, and although it looks similar, it's not the SCO ID either.  The value is in fact taken from the Publish dialog's Project Title field.

    Weird.  I've never seen this issue in any previous version of the Multi-SCORM Packager tool.

    Any ideas why this is getting so badly screwed up?

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