Join David Rivers for an in-depth discussion in this video Understanding LRS vs. LMS, part of Up and Running with SCORM and Tin Can API.
- So now we should understand how the next…generation of SCORM, Tin Can API,…or Experience API allows for the tracking…of all kinds of learning activities,…not just courses and scores.…It's not limited to the use…of learning management systems.…Quite often, xAPI will make use of an LRS,…or Learning Record Store, for storing…a learner's learning records.…Here's how an LRS is different from an LMS.…With xAPI, anything a learner does as part…of a learning program, generates an xAPI activity statement.…
of a learning program, generates an xAPI activity statement.…Could be starting an online course, completing a quiz,…or things like attending a meeting,…reading a document, and so on.…Simply put, an LRS is the database where these xAPI…activity statements, in other words their learning records,…are stored for each individual learner.…An LRS can easily be built right into an LMS,…or it can be a standalone product as well.…An LMS that has a built-in LRS supports…the Experience API, and also does all the other things…an LMS can do to manage the learning delivery.…
This course introduces the what, why, and how of SCORM, and the tools for creating SCORM-compliant content. Author David Rivers also covers the second generation of compliance integration, the Tin CAN API (aka the Experience API), which allows for learning events to be recorded and analyzed.
- What is SCORM?
- Why is SCORM important?
- Publishing to an LMS with tools like Adobe Captivate and Lectora Inspire
- Keeping SCORM-compliant by reporting scores
- Understanding the Tin Can API