-
Notifications
You must be signed in to change notification settings - Fork 249
Tracking in the Framework xAPI and SCORM and others
David Pesce edited this page Jan 11, 2016
·
3 revisions
We need to start using xAPI for tracking our learning in Adapt (because it's the future!).
Some work has been done already (see ABU-1116)
- review current progress and plan of attack
- Maintain existing spoor plugin for backwards compatibility?
- Port event capture code from spoor to core framework?
- Review events fired by components/extensions/framework -
- Are we triggering what we need to?
- Are events consistent?
- xAPI extension? (new Scorm one too?)
- Additional tracking types - in addition to SCORM/xAPI?
- Serialization should stay within the protocol (SCORM, xAPI, etc.)
- Stateful session will move to adapt core
- Possibility of implementing one tracking query that each protocol can query to determine the tracking status (rather than a lot of individual tracking calls to core)
- Framework in Five Minutes
- Setting up Your Development Environment
- Manual Installation of the Adapt Framework
- Adapt Command Line Interface
- Common Issues
- Reporting Bugs
- Requesting Features
- Creating Your First Course
- Styling Your Course
- Configuring Your Project with config.json
- Content starts with course.json
- Course Localisation
- Compiling, testing and deploying your Adapt course
- Core Plugins in the Adapt Learning Framework
- Converting a Course from Framework Version 1 to Version 2
- Contributing to the Adapt Project
- Git Flow
- Adapt API
- Adapt Command Line Interface
- Core Events
- Core Model Attributes
- Core Modules
- Web Security Audit
- Peer Code Review
- Plugins
- Developing Plugins
- Developer's Guide: Components
- Developer's Guide: Theme
- Making a theme editable
- Developer's Guide: Menu
- Registering a Plugin
- Semantic Version Numbers
- Core Model Attributes
- Adapt Command Line Interface
- Accessibility v3
- Adapt Framework Right to Left (RTL) Support