Tammy Rutherford November 25, 2013 •
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 firstname.lastname@example.org.
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.
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 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
Tammy Rutherford June 12, 2013 •
Tin Can API / Tin Can API + SCORM Cloud
If you use the SCORM Cloud application a lot, you may have noticed a new tab that we just added to the interface- LRS. While SCORM Cloud has had Tin Can support for quite awhile, it wasn't always easy fo know where to go to see the statements housed in your SCORM Cloud hosted LRS. Now, we've made it much easier to do a bunch of cool stuff with Tin Can in SCORM Cloud. And it supports Tin Can 1.0!
What's in the LRS section of SCORM Cloud?
This is your window to the Tin Can API world. Here, you can discover the Tin Can LRS endpoints available to your account, give activity providers access to these endpoints, and view the Tin Can statements that have been stored in your LRS.
Each application in your SCORM Cloud account has it's own unique endpoint. Any registrations launched from these applications (SCORM or Tin Can) will send Tin Can statements to that endpoint/ LRS.