A Learning Record Store, or LRS, is an application that stores records about learning. From a data perspective, an LRS sits at the center of your learning ecosystem and brings data together from all your learning systems, applications, and content. It also will often connect to operational systems to gather data about job performance.
Not every database of learning records is an LRS, though. The term “LRS” refers to a specific type of application defined by the Experience API (xAPI) specification. And because xAPI sets strict rules around the core functionality of LRSs, it’s important to use an LRS that strictly conforms to those parameters. A non-conformant LRS will cause problems when you try to connect other applications via xAPI or use the data later.
If an LRS was part of a house, for example, it would be the plumbing—not the window. In other words, learners don't typically interact with or see an LRS as it collects data about their interactions and influences their learning experiences behind the scenes.
Most of the additional features discussed above aren’t simply checking a box with yes or no. The quality, robustness, and usefulness of these features can vary significantly between LRSs. Overall performance and speed, services offered, and support are other factors that vary between LRSs.
If your goal of implementing an LRS is to use learning analytics, there are a few things to keep in mind when getting started. To learn more, follow our insights blog or check out the resource center.