search

openedx / platform-roadmap

Tracking the maintenance, enhancement, and advancement of the Open edX project.
11 stars 1 forks source link

xAPI/Caliper Support #35

Closed e0d closed 2 years ago

e0d commented 3 years ago

Opportunity Objective Make Open edX an xAPI-compatible LMS. This should include two flavors: xAPI-compliant LMS (as an event emitter) and xAPI-compliant LRS (as a learning record store).

Market Evidence More and more LMSes are claiming xAPI support and customers treat xAPI-compliancy as one of the decision points which is not in favor of Open edX as of now. Besides popular authoring tools like Storyline/Captivate produce content in xAPI-form, customers perceive these as "next level SCORMs" and desire the ability to upload these as units to their LMSes of choice.

Proposal Specifics this could be implemented either as an ad-hoc solution or "in a correct way":

ad-hoc means that we can add some sort tracking-logs to xAPI statements converter which was demonstrated by Raccoon Gang already.

"the way it should be" approach requires reengineering of the grading sub-systems: each unit should emit xAPI statements, these statements should be aggregated in LRS (local or remote), based on the stream of these statements the platform should conclude the grades, completions, etc. This way we open up the possibility to use 3rd-party xAPI units in the grading policies, gamification rules, adaptivity features, etc.

Either way, the platform should have a configurable LRS destination (either local or 3rd-party) to which all events will be sent.

Success Measures Open edX supports xAPI content (via scorm_xblock?) and provides LRS to capture emitted events

Open edX emits xAPI statements to a configured LRS (local or 3rd-party)

Open edX local LRS can be exposed to various analytical software like

Open edX is listed on https://xapi.com/adopters/ in LMS and LRS categories.

[Source: https://openedx.atlassian.net/browse/OEROADMAP-51]

This work is being completed by edly as a community contribution.

It is targeting fulfilling the use cases and requirements described in OEP-26.

e0d commented 2 years ago

The current work is being committed here, https://github.com/openedx/event-routing-backends

e0d commented 2 years ago

Per conversation with Zia, this was completed for Maple, correcting the status. @jmakowski1123