What is LRS (Learning Record Store)?
A Learning Record Store (LRS) is the data store defined by the xAPI specification. It accepts learning statements over a REST interface, checks that they are valid, stores them permanently, and lets authorised systems query them. An LRS can stand alone as a learning data warehouse or sit inside a learning management system or experience platform.
How Personal Academy handles it
Personal Academy has no built-in Learning Record Store and does not forward statements to an external one; it accepts inbound xAPI completion statements and records them as progress.
A worked example
Suppose a 300-person engineering consultancy wants one place to analyse simulator sessions, webinar attendance and course completions. They choose a standalone LRS as that store. Their simulator and webinar tool already send statements to it. Before choosing a learning platform, they check whether it can send its own completions outward to the LRS or only receive completions from outside content, because that decides whether they need extra integration work.
The xAPI specification defines two roles: activity providers, which generate statements, and the Learning Record Store, which receives them. The LRS is a web service with a defined set of endpoints. Its main one accepts statements by POST or PUT and returns them by GET with filters for actor, verb, activity, registration and time.
An LRS must validate every statement against the specification, reject malformed ones, and treat stored statements as immutable. Corrections are made by sending a new statement that voids the earlier one, which keeps a complete history. It also stores documents for state and profiles, which content uses to keep bookmarks or settings between sessions.
Access is controlled by credentials issued to each activity provider, usually HTTP Basic authentication or OAuth. In a well-run setup, each source has its own credential and can only write, while reporting tools have read-only credentials.
Organisations use a standalone LRS when they want to analyse learning data from many systems together, for example an LMS, a simulator, a mobile app and a virtual classroom. Statements can then be joined with business data in a warehouse or analytics tool.
When an LRS is built into a learning platform, the platform usually turns statements into its own progress and completion records. Whether the platform can also send its native events to a separate LRS is a different question. Buyers who plan a central learning data store should confirm both directions, inbound and outbound, before relying on either. Ask, too, how statements from each source are identified, because clean actor and activity identifiers decide whether the data can be joined later.