Rustici Software's
SCORM Blog

Subscribe

 Subscribe in a reader

Enter your email address:


Archive


Tweets by Tim Martin



Topics

Authors

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.

2 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 »



Key Points:

  • Our content is constantly updating, so we need to keep control of it on our servers.  This doesn’t work well with SCORM.
  • We provide the ability to personalize the content, mix and match assets as desired, quickly.
  • For customers who do want SCORM tracking, we develop a way to send that data for each customer.
  • Everyone always uses the latest version of the content.
  • Recording informal learning — message boards, instant messages, is important for preserving knowledge.
  • Looking into mobile, at least tablets.
  • Providing “just in time” searchable access information, doesn’t have to be taken all at once as large courses.
  • New API should make use of open source.

1 Comment | Post a comment »



Key Points:

  • Current LMSs focus too much on Management, not enough on Learning
  • Need to customize the learning experience not just by learning need but also by learner type
  • LMSs should be able to design, offer and track informal learning such as job shadowing or mentoring
  • There is a great need to make user generated learning / content available through a standard LMS.
  • LMSs should evolve into Personal Learning Environment (PLEs) or enable them
  • Learning Management Systems should evolve into Learning Network Management Systems
  • There is too much focus on measurement – is there a need to measure every click, every page view, every second spent within the course
  • Learning is evolving from being more personal and less organization driven
  • As organizations pass on the learning responsibilities to the learner, the need to track and report may reduce.
  • Newer concepts such as MOOCs should be available through the LMS
  • Integration of mobile devices and tablets is a clear need – apps for mobile platforms, Kindle, tablet versions etc
  • LMSs should help individuals find more information within their

3 Comments | Post a comment »


Older Posts »

Browse Categories

Using the Standards

Tips, tricks and solutions for using SCORM and AICC.

Standards Evolution

Our chronicling and opinion of the evolution of SCORM.

Rustici Software

Stories about who we are and what we're up to.

Products

News about our products. Notifications of new releases and new features.

Ideas and Thoughts

Miscellaneous thoughts and ideas about e-learning, entrepreneurship and whatever else is on our minds.

Software Development

Ideas about software development and how we manage things internally.