You don’t have to wait for content players to catch up! If you’re creating Tin Can courses but getting frustrated by the limited number of players that can actually launch and report on them, here’s some great news:
SCORM Cloud’s Dispatch service has a new feature that enables a SCORM-only LMS to handle Tin Can packages—without losing reporting data.
How is that possible?
First, you have to understand how SCORM Cloud Dispatch works. Tin Can data is collected throughout the activity experience and stored in your CLOUD LRS. Once the user exits out of the course, the Dispatch updates the client LMS with the user progress in the form of SCORM data.
Why would I want to use this?
While the number of Tin Can conformant LMSs is growing, many LMSs are still in transition. Dispatch allows for an immediate way to launch Tin Can activities in LMSs that only support SCORM. You don’t have to be limited to SCORM-only courses while you wait for LMSs to catch up!
Content Creator Benefits:
- There are now more types of courses you can distribute to customers
- You can now maintain detailed Tin Can statements in Cloud while still satisfying clients’ SCORM reporting needs
- You’re no longer limited to SCORM-only courses
- You can continue to receive SCORM-conformant reporting data
Where do I sign up?
Last time, I cautioned you against clicking the “Delete” button. Well, some things are just too important to delete—like users. That’s why the option to delete users in SCORM Cloud is not available. It just can’t be done.
Story time! Here is a cautionary tale of why you can’t delete users:
Origin of DELETE
Latin deletus, past participle of delēre to wipe out, destroy
First Known Use: circa 1605
First Known Use: circa 1605
Ever hit “delete” only to later find the file hiding somewhere in a trash folder, refusing to let go? That’s really annoying, right? Especially when you intended for it to be gone—forever.
Many people have become used to having a trash folder or recycle bin that piles up all your garbage. Well, we don’t like garbage—it takes up space. We think our customers are just as smart (or smarter) than we are so we try to be particular and intentional about the way we make our product decisions.
So, we set up the “delete” button to do what its name promises. When you hit “delete” in SCORM Cloud, it really means delete. The course, invitation, or registration doesn’t go to a graveyard where it waits to be resurrected. Instead, it disappears, as if it never existed.
Folks like to use Cloud because it makes the business of SCORM a lot easier—we’ve done most of the heavy lifting for you! SCORM Cloud hosts services that allow you to test content, deliver courses, and house learning data in one straightforward platform.
We try to design all our products with our user’s experience in mind, but from time-to-time the things that may seem clear to us are a little cloudier to others. To help clear things up, we’re starting a new blog series dedicated to addressing some common SCORM Cloud questions. The “What Now?!” blogs will be basic, short, and will usually link to our support forum for those who want more meaty explanations.
To kick it off, I’ll be telling you a few things you should know about the “Delete” button. Stay tuned!
There’s something that we like to do here at Rustici Software — make life easier by solving problems with software. This time around, it’s solving some Tin Can (xAPI) problems in SCORM Engine and SCORM Cloud.
SCORM Engine and SCORM Cloud have been updated to v. 2013.2. I won’t list all of the updates in this post, but I’ll point out a few of the big ones.
« Newer Posts — Older Posts »