Completion events are standard, openedx events, so supporting them should be part of the Aspects core, cf #88.
OpenCraft maintains the completion aggregator plugin app which currently lacks support for tracking events.
Contribution open-craft/openedx-completion-aggregator#173 adds tracking events for the aggregated completion states, and openedx/event-routing-backends#377 proposed pulling them into the ERB. But since these events aren't openedx events, we'd rather keep the event routing logic with the aggregator app.
Completion events are standard, openedx events, so supporting them should be part of the Aspects core, cf #88.
OpenCraft maintains the completion aggregator plugin app which currently lacks support for tracking events.
Contribution open-craft/openedx-completion-aggregator#173 adds tracking events for the aggregated completion states, and openedx/event-routing-backends#377 proposed pulling them into the ERB. But since these events aren't
openedxevents, we'd rather keep the event routing logic with the aggregator app.May require some refactoring of feat: add aggregator events event-routing-backends#377 to support sharing event routing and testing logic.
https://docs.openedx.org/projects/openedx-aspects/en/latest/technical_documentation/how-tos/xapi_transforms.html
https://docs.openedx.org/projects/openedx-aspects/en/latest/technical_documentation/how-tos/dbt_extensions.html
Ensure caveats of the aggregator are noted (cf sync vs async) if providing installation instructions.