Learning Standards
When you
Add Content to your portal and select
Upload SCORM or xAPI, Launch scans the package, detects the format, and pre-configures your new content according to the learning technology standard.
cmi5
Although you select Upload SCORM or xAPI when you Add Content, the option works with cmi5 packages too. Launch scans the cmi5.xml manifest and automatically extracts the properties of the course when it adds the content to your portal. Otherwise, the rest of the settings for a cmi5 course are the same as an xAPI course, and Launch treats them the same way: sending the extra xAPI data to an LRS. The learner has the same experience, in every case.
xAPI (TinCan)
Veracity Launch plays xAPI-enabled content packages, and most easily and securely those that support
the xAPI-Launch algorithm: a protocol to send xAPI to a separate LRS, as set-up in the LMS. When you publish a course in your authoring tool, choose xAPI/LRS settings that say, “initialized at runtime”, or “supplied by LMS”, or simply leave the endpoint blank, which tells the package to let Launch manage integrating the LRS.
Settings in Articulate Storyline 360, dominKnow | ONE, iSpring Suite, and Gomo Learning
You
set-up the separate LRS in Launch, but Launch still stores a copy of xAPI statements internally and uses that data to measure learner’s completion, success, and score. To view the internal store, select
Reports from the left menu, and click the
View Statements button.
When you upload a package to Launch, we host the package on our server, but you can also play xAPI content hosted on another server (
using Launch as a proxy).
SCORM 1.2 and SCORM 2004
SCORM is a common legacy format for content packages. Veracity Launch supports single- or multi-SCO* packages in either SCORM 1.2 or SCORM 2004 versions. When you upload the course, Launch reads the imsmanifest.xml and automatically extracts the properties of the course when it adds the content to your portal.
*Veracity Launch does
not support
the SCORM sequencing model for a multi-SCO course. Instead, it marks the parent course
Complete only when it gets completion data for every child SCO. However, Launch marks a single-SCO course
Complete as expected.
Player Types
Veracity Launch supports uploading individual files such as videos, images, or PDFs. It can track if a learner viewed an external link. Launch even lets you link to a course on a different server: when complete, Launch asks the learner to upload a copy of their certificate.
Video (MP4)
Launch marks the video as Complete when the learner has seen the entire content. If a learner skips to the end of the video, then Launch does not mark it as Complete.
Acrobat File (PDF)
Veracity Launch offers an xAPI-enabled PDF viewer. When the learner flips pages, the viewer sends a left statement for the previous page and an experienced statement for the next page.
Only when the learner flips all the pages (regardless of order) does Launch marks the content Complete.
To get xAPI statements to flow to your LRS from the PDF viewer, you must enter the properties of the endpoint in the LRS Settings for the content.
Other File Types
When you upload other types of files to Veracity Launch, it sends them to the learner’s browser. If the browser has built-in support for the filetype, then it displays the content. Otherwise, the browser prompts the learner to download the needed support.
Launch marks the content as Complete when the learner views the file.
External Link
We can track an external link as a content type.
Launch marks the content as Complete when the learner opens the target link.
External Certificate
Launch offers you the option to let the learner take a course outside the LMS. However, the learner must attest to their completion and upload the certificate they got from the course before Launch marks it as Complete.