I was asked to present at the first xAPI camp of 2016 on behalf of Elements team on the advantages of using a centralized Learning Record Store (LRS) within an enterprise learning ecosystem using xAPI. Whether you are new to the specification or have an xAPI enabled application, these camps are a great way to gain knowledge about the Experience API.
Topics: ADL, AutoCAD, Cognitive Advisors, Learning Division, Events, Learning Record Store, LRS, MakingBetter, Queensland University of Technology, Quinnovation, TryxAPI.com, xAPI Camp, xAPI Camp San Francisco, Yet Analytics
Ever wanted to capture the whole learning experience of your user, but not sure where to start? In this blog I will present on different ways that xAPI has benefited the learning experience and the learning ecosystem. All the case studies in this blog can be found at TryxAPI.com
With the proliferation of complex online services and web based software, training and documentation have become crucial in acquiring and retaining users. Enterprise web-based software need to train their users on how to use their software. That may seem like an obvious statement but providing effective, up-to-date software training for software applications is critical to people actually using the software so they can do their job.
The Riptide Elements team has recently implemented some platform solutions around building and storing xAPI statements with respect to our course ware. The primary issue was: what should happen when attempting to store an xAPI statement with an error or client connection loss? The problem is twofold -- one part being, statements can occasionally be created with malformed structure, and the second is a loss of user data when a bad statement prevents others from being stored to the LRS. To tackle this problem, the Elements engineering team got together to brainstorm some potential solutions.
The Advanced Distributed Learning (ADL) Initiative recently added Riptide’s LRS Test Suite to its list of resources available to the xAPI community. Riptide remains part of the original 22 person workgroup that created xAPI and continues to be part of the xAPI compliance workgroup.