SCORM, xAPI, and LTI
How Nucleus OS works with other learning platforms through SCORM 1.2 and 2004, xAPI, and LTI 1.3.
Nucleus OS supports the learning standards that let content and data move between platforms.
Which standard to use
| You want to | Use |
|---|---|
| Run a Nucleus OS course in another LMS as a static package | SCORM export |
| Bring existing courses into Nucleus OS | SCORM import |
| Send detailed learning activity to a Learning Record Store | xAPI |
| Launch live Nucleus OS content (with the AI tutor and adaptive paths) from another platform | LTI 1.3 |
| Launch a tool from another platform inside Nucleus OS | LTI 1.3 |
SCORM
Nucleus OS imports and exports SCORM 1.2 and SCORM 2004 packages. Imported packages can be placed in learning paths, assigned by enrollment rules, and reported on like native courses. See SCORM export for exporting.
xAPI
Nucleus OS emits xAPI statements for learning activity, such as launches, completions, answers, practice attempts, and certifications, and can forward them to your LRS.
To forward statements, configure your LRS endpoint and credentials in the integrations settings. Statements use the learner's email as the actor identifier so they match records in your other systems.
LTI 1.3
LTI 1.3 lets platforms launch each other's content securely, with single sign-on and results passed back.
- Nucleus OS as the tool: launch Nucleus OS courses from your LMS. Learners get the full experience, including the AI tutor, adaptive paths, and role-play, and results are reported back to the LMS gradebook.
- Nucleus OS as the platform: launch an external LTI tool as a step in a Nucleus OS path.
Exchange configuration
LTI 1.3 setup exchanges a few values between the two platforms: client ID, deployment ID, issuer, and key set URL. Have an admin from each platform available when you configure it.