Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
SCORM Objectives support #181
N.B. this functionality is being introduced into the legacy version of spoor first. If successful it will be introduced into master.
Objectives are implemented as being completion-based or event-based. A list of one or more Adapt models is given for a completion-based objective. As these models are completed the status of the objective changes. The functionality for completion-based objectives is built into spoor. Event-based objectives allow the state of the objective to be controlled externally (e.g. by a third party plugin). For event-based objectives it is the responsibility of the implementer to trigger a given event to request that the objective state should change.
Objectives can be completion-based or event-based. A completion-based objective changes state as the given content models (components, blocks, articles, content objects) are completed. State changes for event-based objectives are handled externally; allowing the behaviour of the objective to be implemented arbitrarily. Specify a completion-based objective using the property
Objective IDs can be given directly in
Example objective ID paths
On first run of a course an objective can be optionally initialised with the state
Storage of interactions by the offline API was removed by this change. To allow objectives (and interactions) to be stored by the offline API for testing purposes there are two new configuration options in spoor: