Thanks Steve,

So where does the xAPI data come from? Is it being pulled into Totara from an external LRS so you can report within Totara, or is it created and stored within Totara when learning events occur, or something else?

Simon

That's exactly the kind of specific feedback I was after, thanks Amir for taking the time to explain your thoughts.

Obviously the scope to implement all of the above is quite large. If we were to start tackling parts of this, where would your priorities lie?

Simon

Hi

Just resurrecting this topic as it is an area we are looking more closely at.

Has there been any more progress towards Totara being able to work with xAPI?

In our context we are developing a central content repository where we publish once and distribute across multiple platforms and channels.

We would ideally like to be able to write to Totara as well as the LRS via xAPI

Any update from last year would be great.

Thanks

Paul

The consensus seems to be that xAPI is unlikely to ever replace SCORM as the most widely-used standard, but that cmi5 probably will.

So well done to the Totara team for making the decision not to invest time and resources on xAPI :-)

However, for the company I work for, there are clear benefits of being able to use cmi5.

Even an "interim solution" keeping everything inside the LMS, and without a Learning Record Store, would have benefits for us, including:

• Being able to use several Actionable Units instead of a single large SCORM would allow for much better progress monitoring/reporting
• The "learner" staying in one browser tab throughout a course would create a better user experience

In fact, we would probably prefer having such an "interim solution" first, so we can get used to how that works, before moving into the realms of external resources, offline learning and Learning Record Stores.

Our content creation tool (Articulate 360) claims to export cmi5 already, so we would love to see cmi5 appear on the roadmap for Totara.

Thanks all.