Log storage: Logstore xAPI
Ryan Smith, 
jerrett fowler, FOR NEW RELEASES PLEASE GO TO OUR GITHUB RELEASES.
Until Moodle provides a way to automatically create new versions from Github releases we will no longer be publishing new versions here sorry, please track their progress on this via the JIRA MDLSITE-1865 Ticket.
What does it do?
As stated on the Github repository, the plugin simply “emits events from the Moodle Logstore as xAPI or TinCan statements”. For those that don’t know, the Moodle Logstore is a log of activities in Moodle. When you view a course, complete a quiz, or grade a student a log of that activity is recorded in the Logstore. The plugin uses these logs to produce xAPI/TinCan statements and then sends (emits) them to an LRS (Learning Record Store).
How does it work?
The plugin is made up of three parts, an Expander, a Translator, and an Emitter. Every log entry goes through each of these parts in a six-step process before finally reaching the LRS (see below).
The plugin passes the log entry from the logstore_standard_log to the Expander.
The Expander expands the log entry with data from your Moodle database.
The plugin passes the expanded event from step 2 to the Translator.
The Translator translates the expanded event to xAPI/TinCan recipe options.
The plugin passes the translated event from step 4 to the Emitter.
The Emitter constructs the translated event as an xAPI/TinCan statement and emits it to the LRS.
Useful links
Screenshots
Contributors
But I add this remark to those who work behind a proxy server:
If you are using the Tincanlaunch Mod and you are behind a proxy server, consider changing the proxy configuration in
admin / tool / log / store / xapi / vendor / rusticisoftware / tincan / src / RemoteLRS.php
by removing the automatic configuration:
35 // protected $ proxy;
Add :
87 // this is here for some proxy handling
88 'proxy' => '192.168.xxx.xxx:8080',
and disable:
/ *
106 if (isset ($ this-> proxy)) {
107 $ http ['proxy'] = $ this-> proxy;
}
* /
In this way, xAPI will also work for Tincan content
Notice: Undefined offset: 0 in D:\WWP\wamp\www\NGT2\lms\admin\tool\log\store\xapi\classes\log\store.php on line 158
Might changing line 157 of store.php to this line of code remove the notice while not causing any issues with your plugin?
if (is_numeric($key) && isset($xapievents[$key]['context']['extensions'][Event::CONTEXT_EXT_KEY]['id'])) {
I'am trying to debug the source code of Logstore xAPI, in order to understand how this code works to be able to adapt it to my use case. For this, I wonder what is the entry point of this code? Thank you in advance for your reply
VENDOR folder is empty in the new zip file. Is old folder unchanged?
Thanks
Dey
For some reason my plugin is not sending ANYTHING (as far as I can tell) to the Watershed LRS. My Activity Provider is correct because Tin Can Launch works with it. Can you please help me debug, or what could be the issue? Thank you.
I am working behind institute proxy and trying to use this plugin in Moodle but no data is being transmitted to Learning Locker. I can see in the database that the table mdl_logstore_xapi_log is capturing events. I have also tried to send statements to Learning Locker directly which works. I followed the steps available in the website of h2tlabs. Please guide me.
Have you planned to emit events for badges issuing?
Thanks