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 »
Why People Pay Us
Categories: Ideas and Thoughts, Rustici Software, SCORM, Standards Evolution
25 May 2011
Before we bought 30 inch monitors for everybody, we used to print out all of the SCORM specs as they came out. The hard copy made them a whole lot easier to digest even though it meant the slaughter of many innocent trees. In unpacking the last boxes in our new office today I came across all of them. It makes a nice visual for why it makes sense to work with Rustici Software if you’re serious about providing standards support.
4 Comments | Post a comment »
Key Points:
- Biggest issue is still interoperability, though we haven’t encountered many problems.
- Mobile learning is increasingly in demand. Offline use, and the JavaScript API are the main (API) problems to be solved.
- Currently have a portable LMS, runs off a flash drive.
- Our portable solution will work well without new standards.
- Customers are asking for social learning.
- When having trouble in a section of a course, identify people in your network who did well.
- LMS could provide access point and tracking for social networks.
- Learning will become much more individualized.
No Comments | Post a comment »
Key Points:
- Customer wants to allow learners to share and comment on notes: within a topic, or across courses.
- There is increasing demand for mobile delivery.
- We have extremely large libraries of content.
- Clients desire a simpler way to find, manage, and deploy content from within their LMS.
- Each LMS provides different properties to adjust course behavior.
- Some systems don’t provide bulk import.
- Cross-domain, JavaScript issue. We would prefer to host the content, and just deploy meta-data.
- Discussion of marketing new API.
- Meta-data should be more extensible, content provider should be able to add meta-data that will be displayed, and acted upon if understood.
- Trend: tracking, reporting on more detailed assessment data.
- People want to have access to one and the same library of content from a range of different devices.
- Versioning: important to keep track of what version of a course was experienced, but also the fact that multiple versions are logically the same course.
- Multi-lingual content is an important use-case for versioning.
- We provide robust simulations, and have added gaming concepts. But we would like to share some information across users, e.g., add a competitive component.
- Monolithic courses will to some extent be replaced by smaller, or interactive experiences.
- Another trend is vLabs, our virtual labs product that provides live sessions to actual hardware.
No Comments | Post a comment »
Key Points
- 90% of content loaded into our system is SCORM 1.2 — because it’s perceived as simple by our clients.
- Demand for SCORM 2004 support seems to be mainly as a “check-box”, something you’re supposed to have.
- Mining industry: simulating big trucks. Have objectives & interactions to track but don’t have a way to track them.
- Support for distributed content is our biggest issue.
- “Content as a Service”, need to manage IP, licensing, discovery of distributed content.
- API needs to keep track of what version of content is used. And report on it.
- Would be great to have an instructor API to allow an observer to indicate an objective has been met.
- Reporting API may make sense, but our clients aren’t asking for it.
- System integrations generally consist of passing certification status (yes or no).
- Discovery, license, and use of content needs to become more like buying an iPhone app for your organization.
- Cross-platform will be big
- SCORM should have a mission statement, and a roadmap, that should allow people to feel more comfortable putting effort into it.
1 Comment | Post a comment »
« Newer Posts — Older Posts »
