A remote content package is a .zip package that contains the manifest and supporting files for an e-learning course. It enables the course to function remotely. When you upload the package to your LMS and launch it, it will access the content on Skillcast LMS.
If you need to update the course, make your changes using Skillcast content editor and ask your customer success manager to publish the module. The changes will then be reflected on your LMS - you don’t need to export a new package. However, please do not publish changes for rolled-out modules.
If you need a remote 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 remote content packages, this article explains how to do it.
If you need to export a deployed content package, please see the article Export a 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 editable module you want to export. You can follow the steps listed in the article about Finding a module.
NOTE: You can export only editable modules.
2. Select the Export a remote content package link on the right side of the page.
3. At the top of the screen you will find the settings for the remote content package export.
Below the settings, you will find two informational sections - "Remote content package usage" and "History of exported remote content packages".
Remote content package usage | The usage table lists all user domains used to export remote content packages of this module. It also shows the number of active users in each domain and when they last accessed the module. |
History of exported remote content packages | Here 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. |
NOTE: If you try to export a remote content package using the same user domain, you must consider a few things. In short, export a new remote content package in the same user domain, only if you are not already using the existing version and you lost the previous version or if we have implemented technical improvements.
Please note that learners on the same LMS assigned to a new package of a different type may be allocated an additional seat and, therefore, appear twice in the reports.
If the package you are exporting will be used on a different LMS, you should set up a separate user domain and export it there instead. This will allow you to distinguish users accessing the module from a different LMS in the reports.
If you are unsure, please consult with your customer success manager.
Settings
Below is the list of all settings. When you export your remote content package with the required settings, please test it with your Customer success manager before assigning it to the employees.
Package type | Select the version used by the third-party LMS. The available remote content package types are:
|
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 lost the package or we implemented some technical improvements and therefore you need to export the package again and re-upload it to your LMS, you must choose the same domain, as the wrong option can lead to double subscription usage. To confirm, please check the History of exported remote content packages table. |
Export type | 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. |
Duration | Set this to the course length. The approximate time calculation is [number of words] / 150 words = minutes. |
Show advanced settings | Enable to toggle to see available advanced settings (listed below). The settings are applicable to SCORM only. Hence, the toggle is hidden for the xAPI package type. |
Escape special characters in suspend data | Some LMS cannot store special characters, and this setting should prevent related errors. Leave unticked unless required. |
Use minimal meta data in manifest | This option reduces the manifest to its minimalistic and least descriptive form. It can be used for LMSs that lack support for SCORM features. Leave unticked unless required. |
NOTE: If you think you have the incorrect permissions, please contact your company admin or customer success manager at [email protected].