Support

Joe Donnelly Dec 17 SCORM Engine/LMS

We've just released a new version of SCORM Engine (2014.1)!  This version includes a number of improvements that make this one of the most robust upgrades in the history of the SCORM Engine, so you definitely want to think about getting your application updated to use 2014.1.  If you are ready to start talking upgrade, go ahead and contact us or just shoot us a message if you have any questions!

Here are some of the highlights:

1.  It's SCORM and Tin Can conformant!  The new Tin Can (xAPI) Conformance Test Suite from ADL includes hundreds of tests to assess LRS conformance.  Rest assured, SCORM Engine 2014 passes them all.

2.  Engine supports Recipes!  It automatically indexes incoming Tin Can API statements using these Recipes' specifications, making Tin Can even simpler.

3.  It's even faster than before.  We've made significant database improvements for increased speed and overall performance.

4.  Improved Tin Can implementation with focus on performance

5.  Tin Can conformance bug fixes (see #1)

6.  Added Postgres V3 support

7.  Improved Oracle performance

8.  Improved DB Retry support

9.  Fixed XSS vulnerabilities found in security audit

Where can you find more information?

For more top-level technical details on the new release, visit the Documentation page or contact us.

Tammy Rutherford Aug 25 The Latest News

It’s happening! Large (successful) corporations are using Tin Can AND finding it helpful in driving business decisions. Want proof?

AT&T engaged in a proof-of-concept to trial a new approach to compliance and ethics training—difficult things to measure. To bridge the analytic gap, AT&T leveraged Tin Can and Watershed LRS to examine how learners interact with content. This involved two levels of situational simulations that were randomly assigned to learners who chose to participate.

 

Simulation 1: Basic text and graphics with one branch that provided immediate feedback based on the learner’s response. Think: basic read and click.

Simulation 2: Video-based, experiential simulation with multiple branches. Branches provided provided emotional responses from supervisors or customers based on learner choices. Learners were also encouraged to “rewind” and explore multiple paths.

att-tin-can-api

This graph does not reflect actual results. This is a sample graph based on the hypothesis.

Why the two simulations? The goal was to determine if the effectiveness of the video-based approach justified the additional expense. Also, to identify which motivators produced the highest volunteer response rate.

What was being tracked? Tin Can statements were generated from the following experiences:

  • Pre and post surveys to compare learner opinions about the current compliance training format compared to the simulations
  • Tracking learners’ interactions with the simulations
  • Moving forward, monitoring how participation in the two simulations affected the number of calls placed to the compliance hotline

Since all of the survey, learning, and performance data resides in one place, it’s easier to make correlations and see which actions lead to the desired outcomes.

To learn more about how AT&T is leveraging Tin Can and an LRS, you can view the AT&T webinar recording here, or access the Q&A page that has questions and answers that occurred during our AT&T/Tin Can API webinar.

Tammy Rutherford May 01 SCORM Cloud / Dispatch

Great news! You can create a Dispatch of a Tin Can course. Here's how you can make it happen:

 

1. From your "Library" page, select the Tin Can course/s you want to create Dispatches for (yes, you can select more than 1 at a time if they are both going to the same Client LMS)

2. Click on the "Dispatch" button 

Screen_Shot_2014-05-01_at_6.56.01_PM.png

 

3. Follow the instructions on setting up the Dispatch.

4. Download the Dispatch file to save it locally. 

5. Provide Dispatch file to your clients for them to load into their LMS- just like any other SCORM 1.2 file.

 

Voila! Tin Can courses now launching from a SCORM LMS. Tin Can statements are stored in your Cloud LRS. SCORM data is reported back to the client LMS.

Tammy Rutherford November 25, 2013 3 SCORM Engine/LMS

We've just released a new version of SCORM Engine (2013.2)- chock full of some new tools to make your TinCan API experience with Engine even better. And some improvements including a new face to Console. If you're ready to upgrade to the latest version, just contact us at support@scorm.com.

Notable New Features

Tin Can / SCORM Parity Reports

We’ve listened and heard the need for more aggregated reporting based on the Tin Can activities your learners are using outside of the LMS. Engine now has a new reporting feature set that provides easy access to pull data from the LRS to answer such questions as “What activities have my users been completing?”, “How has Joe been performing on his activities?”, “How much time has a user spent in our basic training course?” 

This functionality will provide a companion LRS endpoint to allow you to extract aggregated results data on any user and activity combination in your system.

Check out the developer documentation here and let us know if you have any questions.

Statement Forwarding

You can now forward your statements, or allow your learners to forward their statements, to any other LRS for which you have credentials. See the documentation here for more details.

TinCan 1.0.1 compatibility

Note that this release of the Tin Can API (xAPI) Specification is only a patch release. In accordance with semantic versioning, which Tin Can API (xAPI) follows, there are no functional changes within this version.

Other Fixes and Improvements

  • Improved SCORM Engine Console functionality (e.g., added pagination for package browsing, new Bootstrap-based UI)
  • Added a minimum Commit Frequency for Engine’s client-side JavaScript
  • Added config option for setting commit frequency
  • Fixed concurrent launch detection timezone bug
  • Added UTC column to LaunchHistory table
  • Fixed security vulnerabilities found in software-based audit
  • Fixed miscellaneous OAuth bugs
  • Added configuration option to disable RedirectOnExitURL
  • Fixed Tin Can document creation bug
  • Fixed .NET issue with URLs containing a ‘+’
  • IE10 meta-tag support in IECompatibilityMode
  • Fixed Package Property JQuery usage bug
  • Improved TinCanRegistration handling when used in context.registration statement JSON
  • Added ClearRegistration method in ScormEngineManager
  • Fixed issue where Tin Can content launches with same activity ID always preferred most recently imported content
  • Fixed Tin Can Central / Remote launch functionality
  • Removed unneeded user-facing assertion not present in 2004 sequencers
  • Improved Dutch translations
  • Improved offline SCORM support
  • Added allowance for Tin Can 0.9 statements in statement conversions

Tammy Rutherford September 10, 2013 Tin Can API / Webinars/ Presentations/ Resources

We get a lot of questions about how Tin Can API statements should be structured and used. We thought we'd help folks out with some resources on how to  use Tin Can the right way.  Our very own Brian Miller has basically been writing a book about the anatomy of a Tin Can statement.  We've broken it down for you- there's a lot here, so take your time and get to know Tin Can

 

Tin Can API Statement Deep Dive Series

 

 

 

 

Overview | Recent