glossaryPage.heroH1

An LMS manages learning — courses, lessons, assignments, quizzes, grades. A school management system (SMS) manages the school as an organization — admissions, attendance, timetables, fees, transport, HR. Many institutions run both: the SMS holds the official student record and master roster, and the LMS handles day-to-day teaching. OpenEduCat ships both modules on a shared database so the roster and gradebook stay synchronized without an external integration layer.

An LMS is instructor-led and course-centric: an admin or teacher assigns a learner to a course, and progress is tracked against that course's completion criteria. A learning experience platform (LXP) is learner-led and content-centric: it surfaces a personalized feed of lessons, articles, and videos drawn from many sources, and the learner self-directs. LXPs typically sit on top of an LMS rather than replacing it — the LMS still records the system of truth for compliance and credit.

A learning record store is a specialized database defined by the xAPI standard. It stores statements — 'actor did activity with result' — emitted by any learning tool. An LMS may include an embedded LRS, but a standalone LRS is just the data store; it does not deliver courses or run quizzes. Use an LRS when you want to aggregate learner activity across many LMSes, simulators, and informal sources into one analytics pipeline.

SCORM (Sharable Content Object Reference Model) is the older standard: it packages a course as a ZIP file that an LMS can launch, and tracks completion, score, and time inside that LMS only. xAPI is the modern successor: it tracks any learning activity — including outside the LMS — as statements sent to a learning record store, with no requirement that the activity happen inside a browser. Most enterprise LMSes support both; xAPI is the direction the IMS Global / 1EdTech community recommends for new content.