-
Notifications
You must be signed in to change notification settings - Fork 0
Learner Events and xAPI
To connect the editor to your LRS you need to provide a custom handleLearnerEvent
function.
Since there are many different standards and implementations we decided to allow integrations to provide their own handler.
We provide an xAPI example below.
The handleLearnersEvent
function will be called when a learner is interacting with the editor with the following data:
export interface LearnerEventData {
verb: 'opened' | 'attempted' | 'interacted' | 'answered'
contentType: // plugins that currently send learner events
| 'input-exercise'
| 'sc-exercise'
| 'mc-exercise'
| 'blanks-exercise'
| 'h5p-exercise'
| 'spoiler'
| 'solution'
correct?: boolean
value?: object | string | number
pluginId?: string // editor id of the plugin that triggered the event
}
Additionally this data is also dispatched as a custom event that you can listen to if that is more convenient:
document.addEventListener(editorLearnerEventName, handleExerciseEvents)
As of now handleLearnersEvent
supports a basic set of interactions that might be enough for many use cases.
If you have specific requirements please get in contact or open a PR.
Here you can find a simple example of how to use this system with xAPI:
handleLearnerEvent for xAPI with watershed LRS
- Home
- Serlo Infrastructure
- Serlo Infrastructure for Non programmers
- Resources for new programmers
- Setup of the toolchain
- Best Practices
- Data Privacy for Devs
- How Tos
- Single Sign On
- Integration with the Data Wallet
- User Journey
- Integration of "Datenraum" into the Serlo Editor
- Introduction to the Serlo editor
- Core concepts of the Serlo editor
- Packages of the Serlo editor
- Creating a new plugin (outdated)
- Redux process in the Serlo editor
- The content format of the Serlo editor
- Serlo Editor Plugin Initial State
- How the Serlo Editor is integrated into edu-sharing via LTI
- Learner Events and xAPI