Skip to main content

Export a content package

Updated over 5 months ago

If you need a content package to host on a non-Skillcast LMS, please contact your Customer success manager at [email protected], who can assist you. However, if you have permission to export deployed content packages, this article explains how to do it.

If you need to export a remote content package, please see the article Export a remote content package. You can read about the differences between deployed and remote content packages in the article titled E-learning standards and features.

1. Find the module you want to edit. You can follow the steps listed in the article about Finding a module.

2. Select the Export a content package link on the right side of the page.

3. At the top of the screen you will find the settings for the content package export.

Below the settings, you can see the "History of exported content packages" table, where you can check previously used settings, who exported the package and when. You can select each entry in this table to see the full settings list.

General settings

Below is the list of all general settings. When you export your content package with the required settings, you must inform your Customer success manager to perform final checks before assigning it to the employees.

Package type

Select the version used by the third-party LMS. The available deployed content package types are:

  • SCORM 2004 4th Edition

  • SCORM 2004 3rd Edition

  • SCORM 2004 2nd Edition

  • SCORM 1.2

  • SCORM 1.2 for Moodle

  • xAPI

  • Untracked content package*

*It requires additional permission. It is a package that can be hosted on a web server instead of LMS. It does not have tracking or bookmarking.

Skin

The skin should match the published module skin to ensure the module looks and behaves the same way. Please confirm by checking the Publish module screen.

Module Version

Select the name of the module for the tracked content package.

User Domain

Choose the staff domain that the content package will be tracked in.

NOTE: Be cautious when selecting User Domain. If you are unsure which domain to use, please get in touch with your Customer success manager at [email protected]. If you need to export the package again and re-upload it to your LMS, you must choose the same domain, as the wrong option will lead to double subscription usage. To confirm, please check the History of exported content packages table.

Module Version and User Domain are related and must both be correctly selected.

Export type

You can download the package to your machine or upload it to File Exchange (FE). If you choose to upload it to FE, select the domain the receiver can access.

Author

Type in your own name or Skillcast.

Duration

Set this to the course length. The approximate time calculation is [number of words] / 150 words = minutes.

Version number

The version number is used in the title and manifest file of the exported package.

For the initial version, leave it as 1.0. Depending on the significance of the changes made, increase to 1.1, 1.2 or 2.0, 3.0, etc. each time you need to export a new content package.

Show advanced settings

Enable to see the advanced settings, or disable to hide them.

Advanced settings

Most commonly, we can leave the default advanced settings; however, some LMS require specific settings to be selected for the SCORM to work properly.

Always report best score

Selected by default.

Ensures that the best score achieved is always recorded. If unchecked, it would report the last score.

Track assessment questions as SCORM interactions

Selected by default.

Responses to individual assessment questions will be recorded in the LMS.

For SCORM 2004, it stores question ID and text, what are the correct choices stored as text, correct answer, user answer stored as text, and correct/incorrect status.

For SCORM 1.2 it stores question ID, what are the correct choices stored as indexes, correct answer, user answer stored as indexes, and correct/wrong status.

If betting is on in the assessment, it is indicated by the weighting column in SCORM interactions, where 1 means the user was confident and 0 – not confident. If the betting is off, all interactions have a weighting of 1. This is applicable to all SCORM versions.

Add module debugging to package

If there is a SCORM error, this setting adds a debugger panel which helps users record the information for the developers.

Do not add cache param for CSS and JS resources

Prevents file caching. It calls the file directly with no cache controls. Can be used if there is an issue loading media files.

Do not export media files in content package

Stops content files like Images/Font/Video and Audio from being bundled into the zip package. This option also updates content file paths to come from Skillcast servers. The media files will be visible in the module; however, Skillcast will be hosting them.

This can be used to reduce the file size for testing, but we should avoid using it for the final SCORM package.

Do not set Failed completion status (SCORM 2004 only)

Select this option if you don't want the success status to remain unchanged on your LMS when the user has failed all of their attempts.

Escape special characters in suspend data

Some LMS cannot store special characters, and this setting should prevent related errors.

Force window close after LMS Finish is called

If the LMS doesn’t close the module when the user selects the Close module button, this setting can help force this action.

Hide LMS frames

The setting might still be applicable for the older LMS platforms. It modifies the client's LMS behaviour by hiding the LMS framing around the module so the user can see the module content only.

Open module in a new window

When launched, the module will open in a new window, breaking the module out of the LMS' framing.

It also ensures the module does not lose access to the SCORM API.

Set lesson status for modules with no assessment to "completed"

Select if the module has no assessment. This option sets the module status to complete on the third-party LMS (instead of passed).

Show warning if LMS commit fails

Shows a warning that the tracking is not working properly instead of ending the session with an error screen.

Specify primary objective in manifest

Related to ‘Specify roll up rules in manifest’ setting for 2004 SCORMs.

It gives detailed information about what the SCORM package contains.

Specify roll up rules in manifest

Related to ‘Specify primary objective in manifest’ setting for 2004 SCORMs.

Forces the completion behaviour of the LMS, allowing the content to dictate the completion.

Start new tracking attempt after completion

​Saba LMS does not add completed training records to user transcripts if cmi.core.exit is set to "suspend", so adding a new publish option to prevent this from happening.

Store tracking data locally during sessions

Changes the way the module tracks. Instead of the traditional module tracking, a custom code tracking is called.

Track assessment scores as SCORM objectives

Tracks each assessment attempt score. It is related to the SCORM objective name setting in the assessment, where we can set it to page title or page number.

Use frameset to force scrolling

Adds an HTML iFrame tag with auto scroll set to true. This is needed if the third-party LMS cuts off the content. This makes the content scrollable.

It also ensures the module does not lose access to the SCORM API.

Use GetLastError to check LMS performance

When experiencing module errors on LMS, this setting would record the last error for the developers to investigate by extracting more information from the client's SCORM API.

Use minimal meta data in manifest

Reduces the manifest to the minimalistic and least descriptive form. It can be used for the LMS that lacks support for SCORM features.

Use post message for utilisation tracking

Select when the module is set to utilisation tracking. This setting overcomes cross-domain security issues.

Use question text for interaction IDs

The setting is for SCORM 1.2. Instead of question ID, question text is stored.


NOTE: If you think you have the incorrect permissions, please contact your company admin or Customer success manager at [email protected].

Did this answer your question?