A launch file is a SCORM 1.2 zip (or other required format) downloaded from the LCMS. It does not contain the content but references its location in the LCMS. When launched, the file and a request to the LCMS determine and render the appropriate content.
Is the launch file limited to where it can be launched?
The launch file can be launched on any LXP or LMS. The launch file is a zip file so in theory could be unzipped and the content launched
What is in the launch file?
The launch file is very small, containing the minimum required to make up a SCORM 1.2 package. The main components are an imsmanifest.xml file which contains a metadata describing the content, and an index.htmlfile which is what the LMS or LXP launches and will render the content to the learner.
What security implications need to be considered with the launch file being uploaded to a learning platform and ‘connecting out' to the LCMS?
The launch package contains a reference to a HTTPS endpoint which verifies access according to the embedded API key and configured licence limits. The success response of this endpoint sets cookies and grants access to the content from our CDN. (Content Delivery Network provided through Amazon Web Services)
Does the launch file give you access to multiple pieces of content?
No its one launch file per piece of content
Can the launch file only be uploaded to one platform?
No the launch file can be uploaded to multiple platforms which means all the users access the same content
What types of files can I store in the LCMS?
SCORM 1.2, xAPI, PDF, and any image, audio or video file.
How can I limit access to content published on the LCMS?
The LCMS has a licence feature which lets you control access to content by the number of users or by a period of time or both.
What happens if I publish a new SCORM or xAPI package?
The LCMS has a version control feature so if you publish a new SCORM or xAPI you have the option to make this the ‘live’ version of the content which is what the user will see on their platform
Are statements sent from xAPI content to the LRS affected by using the LCMS compared to directly uploading to the LXP?
Nothing changes the same information is sent to the LRS, the content does not know that it is being accessed on the LCMS
If I mark a user as complete (either LXP or LMS), will it carry through to the LCMS?
No
If I increase the amount of Licences do I need a new Launch File?
No
If I upload in the xAPI will I still be able to report in-depth into the content within the course either in the LRS or Analytics?
Yes. xAPI statements generated by the content are the exact same.
If I mark an object as complete will it carry through to the LCMS?