From Kentucky to Kraków
Categories: Clients, Ideas and Thoughts, SCORM Cloud, SCORM Engine, SCORM Engine
4 Oct 2011
There’s a new TV show “Around the World in 80 Ways” that challenges 2 guys to use 80 different modes of transportation to circumnavigate the globe. We’re not trying to do that, but we do want to see our SCORM solutions adopted around the world and eliminate the hurdles that come with internationalization.
No Comments | Post a comment »
PENS: Turbo Charging Your eLearning
Categories: SCORM Cloud, SCORM Cloud, SCORM Engine, SCORM Engine, Standards Evolution, Using the Standards
11 Jul 2011
These days, with one click, you can buy a song from iTunes and automatically sync it to your iPod. Remember how long it used to take to buy a CD, burn the songs to your computer and transfer them to your MP3 player? Just think about how much time you saved from this one little improvement- more time to listen to your music, which is what you wanted to do in the first place.
No Comments | Post a comment »
It’s that time again…we just announced the availability of our latest SCORM Engine version, v2010.1. And, yes, I know you’re thinking: “BUT, it’s 2011 now dummy”. Of course, you’re right, but only because this blog post was delayed a few days while we migrated our site to a new server…I promise, we really did put it out in 2010 
.
But, really, who cares about the name? There’s some really good stuff in this release. You can find the full release notes from either our SCORM Engine History page or on our support site (you do know you can subscribe to product notifications there, right?).
I’m most excited about the two new standards we now support: LETSI RTWS and PENS.
LETSI RTWS is a web services communication framework that alleviates some of the common technical barriers SCORM imposes on content deployments. RTWS is a huge step towards enabling remote content hosting, games, simulations, virtual worlds, offline content, secure communications and mobile delivery.
PENS is a standard that allows for the automatic publishing and import of content. With a PENS enabled authoring tool, you can publish new or updated content to your LMS with a single click.
1 Comment | Post a comment »
Blackboard is big time. Blackboard Learn™ leads the higher education learning management world. Blackboard Learn serves more than 20 million learners.
And starting in 2011 (or thereabouts), Blackboard is going to be rocking the SCORM Engine in Blackboard Learn.
We are nothing short of thrilled to announce that Blackboard has signed a long term agreement with Rustici Software to deliver all SCORM and AICC based material in Blackboard Learn, their flagship product.
Ultimately, we’ll let Blackboard tell their story of why they opted to go with the SCORM Engine, but this is what we know.
- Blackboard had a prior SCORM delivery setup based on an open source SCORM implementation, and they found it to be inadequate in supporting their customers.
- Blackboard considered building their own SCORM implementation, but realized they could do it better and more cost effectively by working with us.
- Blackboard considered other commercial SCORM technology… briefly.
Blackboard’s adoption of our rock solid SCORM technology will make things better for Blackboard learners and those people who provide content to Blackboard. This is a huge step for us as well toward one of our long term goals:
Rustici Software would like to provide the technology that makes every SCORM transaction go.
Consider this an invitation to all of the big LMS providers. Each LMS provider that adopts the SCORM Engine reduces the pain associated with eLearning for the industry as a whole. Blackboard’s adoption of the SCORM Engine is a big step toward our goal.
For more on Blackboard’s commitment to SCORM and open standards in general, check out today’s blog posts by Ray Henderson and John Fontaine.
5 Comments | Post a comment »
I don’t know how many times I’ve said to someone on the phone, “SCORM is difficult, especially for the LMS provider.” There are many moving parts, countless interpretations, and vagaries in the specification itself. For the most part, we handle these things exceptionally well. Sometimes we make mistakes, and sometimes those mistakes can compound themselves.
The Source of Today’s Problem
In SCORM 1.2, mastery_score and lesson_status can interact with each other strangely. Frankly, the specification can be interpreted in two ways.
From Section 3.4.4, “The SCORM Run-Time Environment Data Model”, in the cmi.core.lesson_status section (henceforth called “The Narrow View”):
After setting the cmi.core.lesson_status to “completed”, the LMS should now check to see if a Master Score has been specified in the cmi.student_data_mastery_score, if supported, or the manifest that the SCO is a member of. If a Mastery Score is provided and the SCO did set the cmi.core.score.raw, the LMS shall compare the cmi.core.score.raw to the Mastery Score and set the cmi.core.lesson_status to either “passed” or “failed”. If no Mastery Score is provided, the LMS will leave the cmi.core.lesson_status as “completed”.
3 Comments | Post a comment »
Older Posts »
