eLearning Content (SCORM, et al.)

The Wisetail LMS supports several types of files that are authored and created outside of the Wisetail LMS:

1. SCORM
2. AICC
3. CMI5 (xAPI). ^[NEW]

It’s very easy to upload and use an eLearning file within a module. Follow along to see how you can add SCORM, or other content content to your LMS.

Adding eLearning Content

Begin in the Admin tool by navigating to the Content tab and selecting the eLearning pill. This pill houses all eLearning content. It’s also the place where Admins can upload and edit eLearning files.

Click the blue ‘Add eLearning’ button and select the file to upload. Once uploaded, you’ll be in the eLearning profile where you’ll be required to designate a title and place an optional description.

Using eLearning is pretty straightforward, so the eLearning profile offers just a couple of options.

Change eLearning Thumbnail: In the upper right-hand corner, you can click the three dots within the Thumbnail to add an image from your computer.

Preview eLearning Content: This allows you to launch the eLearning file from the admin tool to see how it plays on the LMS.

Download eLearning Content: To the right of the The Preview button you can select a drop-down arrow that allows you to download the eLearning file to your computer.

Once eLearning has been uploaded into this pill you can simply pull it into a module and start offering eLearning content to your users.

Updating eLearning Content

Instead of having to delete an existing SCORM/eLearning Media package and uploading the updated version of the same file again, Admins can upload updated versions of a SCORM/eLearning Media package directly. With this functionality Admins save time and effort when updating the eLearning  packages in the system. It also retains all of the history, completions, etc. that are associated with the existing eLearning file.

When an Admin is looking to update an existing eLearning file in the LMS, they simply need to navigate to the appropriate piece of media, and under the drop-down menu next to the Preview button, the Admin will find a Re-Upload Media option. 

When the Admin selects “Re-Upload Media”, a warning modal appears to advise the Admin that this action will replace all instances of that SCORM/eLearning Media file across the LMS. Users that are in progress in the existing file will be able to complete the existing version.

NOTE: There is no way to track which particular changes were made from one version to another, nor (currently) to report on which specific version any given user completed. Therefore, for any situation where there is a significant change between versions (such as when it could be legally important to understand which version a given user completed) it is recommended to create a new, distinct, piece of eLearning content rather than uploading a new version of the content.

When an Admin uploads a new version of an eLearning Media file, users that have already started a previous version must complete the version they originally started. They cannot access the new version until they complete the in-progress version. This includes admins. Therefore, if you upload a new version of an eLearning Media file, after having previously viewed the original version, you will not see the new version until & unless you complete the originally uploaded version.

Requirements and Best Practices for SCORM

• No Flash.  Due to a change in browser settings (outside of the Wisetail LMS), SCORM that contains any sort of Flash no longer plays nicely in any web browser! This is not a setting that you the creator, nor Wisetail, the LMS, has control over. The authoring tools that you use to export your SCORM file no longer support FLASH and instead are using HTML5, which should be built into your SCORM export.
• Your SCORM packet needs to send either Complete/Incomplete or Pass/Fail to the LMS for the ‘Mark Done’ button to be triggered and a completion initiated. Whether or not that complete or pass flag is sent is set up in your SCORM authoring tool and controlled outside of the LMS platform.
  • Tip: If using separate triggers to send completion and exit the course, please make sure the triggers are listed in order: Send Completion and then Exit. If not, the course may exit before sending a completion and will not trigger the completion in the LMS.
  • Tip: Users taking courses on mobile devices should ensure they use the SCORM course exit button to leave the course. Using the browser X button or a swipe gesture to close the course on a mobile device can result in the completion not being recorded by the Learning Management System as the mobile browser may not provide enough time to complete the communication before closing the backround processes.
  • Tip: CMI5 uses a launchMethod key in the cmi5.xml file within the course .zip file
    • • OwnWindow value will override the LMS window settings such as frameset
        
      • AnyWindow value will allow the LMS window settings to take effect
        

eLearning Settings

In each piece of eLearning Media the file has a Settings panel on the right hand side which contains the following Settings:

• Player Width (In Pixels)
  • Values in this field must be numeric, must be positive number, greater than 100 pixel, & less than 5000 pixels.
• Player Height (In Pixels)
  • Values in this field must be numeric, must be positive number, greater than 100 pixel, & less than 5000 pixels.
• Player Size Note:
  • When an Admin uploads an eLearning Media file with custom / preferred dimensions, the
    system will read the dimensions and display them in the Settings panel. When an Admin
    uploads an eLearning Media file with no presets, the Settings panel displays default values
    dictated by the eLearning Media engine. Admins can make adjustments to an eLearning
    Media file in the Settings panel and the content will display according to the new
    configuration.

Player Launch Type

Specifies how the individual parts of the course should be launched

*Note that due to variations in SCORM / AICC authoring options, the launch settings may be defined by the content itself rather than these settings; Additionally Browser settings may prevent the selected launch configurations desired outcome