A few months ago, we sent out a survey to ask customers to tell us more about how they use SCORM Cloud and what other features they’d like to see. One request we heard from the survey and other conversations with Cloud customers is the ability to set an expiration date for an Invitation or a Dispatch. Well, the wait is over! We just updated SCORM Cloud so now you can set up expiration dates for any invites or dispatches.
It’s a lot of fun working with both hosted and locally installed platforms. Yes, technically the deployments vary a lot (and I’m thankful for our super talented developers who manage both worlds), but it gives us the chance to work with many types of companies and products.
Some folks gravitate towards the flexibility of SCORM Cloud as a hosted solution that scales with them as their business grows. Other folks require a more controlled, locally installed solution and need our Engine player for those very reasons.
Recently we’ve noticed another benefit of offering both deployment options— migrating from one deployment method to the other as business models change.
Case in point? Atomic Learning.
There are many organizations that have multiple LMSs, and many of them have the same problem—they wish they had just one LMS, with all of their data in one place.
SCORM Cloud Reportage provides a simple snapshot of your learners’ activities, but sometimes you don’t want a picture of ALL your learners.
Want to know the completions of a specific department? The average score of learners within a specific geography? The amount of time new learners are spending per course?
By using the tagging feature in SCORM Cloud, you can pull customized reports in the Reportage screen. This allows you to exclude certain criteria and to pull data about isolated groups.
With SCORM Cloud tagging, you can do this with only a few clicks. The key is to add appropriate tags to your learners and then filter by those tags in Reportage. Take a look:
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?
Older Posts »