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
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 email@example.com.
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.
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.
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