Privacy (GDPR) requests now include this plugin's data
The privacy provider previously declared that logstore_xapi_log and
logstore_xapi_failed_log hold personal data, but every export and deletion
method was an empty stub. In practice this meant:

a subject access (export) request returned nothing from these tables, and
a right-to-erasure request, or an ordinary user deletion, did not remove
the user's rows.
Both are now implemented. Export and deletion cover both tables and run
through Moodle's standard log privacy handling in tool_log, the same path
logstore_standard uses.

If your site has processed erasure requests while running an earlier
version, rows for those users may still be present in these two tables.
They are not removed retroactively by upgrading. Re-running the deletion for
the affected users, or clearing the tables, is the way to reconcile that.

The declared metadata has also been corrected: it now lists the fields that
actually exist (userid, relateduserid, realuserid, ip, other) and
no longer names a moodleuserid field, which was never a column in either
table.
https://github.com/davidpesce/moodle-logstore_xapi/releases/tag/v5.1.0

This is a security release. All sites should upgrade. There are no database
changes and no configuration is required after upgrading.

https://github.com/davidpesce/moodle-logstore_xapi/releases/tag/v5.0.3

Removed
JISC support has been removed (#889). The Adds JISC data to statements
(send_jisc_data) setting, the JISC statement extension, and its tests are
gone. The JISC platform has been discontinued, so this was dead code. No
action is required.

Fixed

• Settings page could take over 10 minutes to load on sites with many
  cohorts (#842, #887). The cohort notification setting is now an AJAX
  search selector rather than a checkbox list rendering every cohort.


• Null and empty responses in matching questions no longer cause errors
  (#891, #893). Affects the match, gapselect and randomsamatch question
  transformers, with tests added.

Changed

• Admin settings UX improvements: settings are grouped under headings with
  clearer descriptions (#888).


• Added SECURITY.md and GitHub issue templates for bug reports and feature
  requests.


• Added plugin directory listing metadata, screenshots, and canonical
  repository links.

Moodle Logstore xAPI

Emits xAPI statements using the Moodle Logstore.

• Install the plugin using our zip installation guide.


• Process events before the plugin was installed using our historical events guide.


• Ask questions via the Github issue tracker.


• Report bugs and suggest features with the Github issue tracker.


• View the supported events in our get_event_function_map function.


• Change existing statements for the supported events using our change statements guide.


• Create statements using our new statements guide.

Moodle Logstore xAPI

Emits xAPI statements using the Moodle Logstore.

• Install the plugin using our zip installation guide.


• Process events before the plugin was installed using our historical events guide.


• Ask questions via the Github issue tracker.


• Report bugs and suggest features with the Github issue tracker.


• View the supported events in our get_event_function_map function.


• Change existing statements for the supported events using our change statements guide.


• Create statements using our new statements guide.

Moodle Logstore xAPI

Emits xAPI statements using the Moodle Logstore.

• Install the plugin using our zip installation guide.


• Process events before the plugin was installed using our historical events guide.


• Ask questions via the Github issue tracker.


• Report bugs and suggest features with the Github issue tracker.


• View the supported events in our get_event_function_map function.


• Change existing statements for the supported events using our change statements guide.


• Create statements using our new statements guide.

Moodle Logstore xAPI

Emits xAPI statements using the Moodle Logstore.

• Install the plugin using our zip installation guide.


• Process events before the plugin was installed using our historical events guide.


• Ask questions via the Github issue tracker.


• Report bugs and suggest features with the Github issue tracker.


• View the supported events in our get_event_function_map function.


• Change existing statements for the supported events using our change statements guide.


• Create statements using our new statements guide.