As part of the development and introduction of xAPI into a large organisation, it can always be a challenge to provide the benefits. I'd like to share with you how I used xAPI with Articulate Storyline 360, published as SCORM and being delivered via a Learning Management System (LMS). The Learning Record Store (LRS) is Learning Locker.
Understanding how the Experience API (xAPI sometimes known as Tin-Can API) is structured is the first hurdle to knowing just how flexible and powerful the xAPI can be.
Megan Torrance uses survey data to assess the current state of xAPI adoption and the differing perspectives among non-adopters, adopters, and providers.
I went to build my own infograph to make it easier to explain, but why reinvent the wheel! Here are a couple of infographs that explaining the xAPI a little easier to understand :)
SCORM has been a constant within the eLearning world. Discover the "new kid on the block," xAPI, and how it is slowly changing the eLearning community.
I'd searched everywhere for a quick reference guide to the xAPI statements that are passed for each library. Having not been able to locate one, below is a collated list of the xAPI statements for the H5P Libraries that support xAPI.
If you’re confused about xAPI, the specification of the future, it might be time to learn more. Let’s take a look at the differences between xAPI and SCORM.
What should you do when you uncover an issue with your live xAPI data? In this xAPI Governance post, we show you how to clean your data when issues arise.
Continuing on with sharing resources created in a recent course I completed on edX, here is a short video introducing how the Learning Record Store (LRS) plays a part in Experience API (xAPI).