Hey there 👋 so you want to process some events from the past 🕓, probably a time when this plugin wasn't installed on your Moodle. That's awesome and we really want to help with that. Unfortunately, we've [not built this into the plugin natively yet](https://github.com/xAPI-vle/moodle-logstore_xapi/issues/42), but luckily [@davidfkane](https://github.com/davidfkane) kindly posted the script below. 🎉 Before you run the script, you need to copy the events that you'd like to process from the `mdl_logstore_standard_log` into a new table called `mdl_logstore_subset_log`, the script will then process each event in that new table.
Hey there 👋 so you want to process some events from the past 🕓, probably a time when this plugin wasn't installed on your Moodle. That's awesome and we really want to help with that. Unfortunately, we've [not built this into the plugin natively yet](https://github.com/xAPI-vle/moodle-logstore_xapi/issues/42), but we do have a recommended process for inserting these events.
```php
<?php
/*
* Script designed to increment through old logs for export to LL
*
*
* author: David Kane, 10th November 2016
* dkane@wit.ie
*/
Our process leverages the plugin's existing "background mode" (which is enabled by default in the plugin settings). In background mode, the plugin receives events from Moodle as they happen and stores them into the "mdl_logstore_xapi_log" table to be processed later by the [Moodle Cron](https://docs.moodle.org/35/en/Cron)(which you should have setup already on your server). When the Moodle Cron script is executed, the plugin extracts, transforms, and loads the events from the "mdl_logstore_xapi_log" table into the Learning Record Store and then deletes the events from the "mdl_logstore_xapi_log" table.
To leverage this for events that happened before the plugin was installed, you'll need to move events from the "mdl_logstore_standard_log" table into the "mdl_logstore_xapi_log" table. This can be done by running an SQL query like the one below.
```SQL
INSERT INTO mdl_logstore_xapi_log
SELECT * FROM mdl_logstore_standard_log
```
// INITIAL VARIABLES //
$logfile="./LogstoreLegacyMigrate.log";//stores only the last as JSON.
$moodlepath="/var/www/moodle/";
$increment=7;
$lastValue=0;// the last value of the database
$count=10;// the number of queries that we want to execute in the loop (a value of zero means that there is no limit);
<h1>Legacy xAPI Load <small>This is normally run at the command line. Currently running in debug mode.</small></h1>
</div>
<divclass="row">
<divclass="col-md-8">
<divclass="panel panel-primary">
<divclass="panel-heading">
About this script
</div>
<divclass="panel-body">
<divclass="alert alert-warning"role="alert"><strong>! NOTE:</strong><br/>This HTML guff disappears when the debug variable is set to false. However, the script works the same with or without the debug variable being set. It is up to you to delete the records from the LRS yourself, maybe use a tool like <ahref="https://robomongo.org/"target="_blank">Robomongo</a>, if you have exported them in error. Otherwise you might like to modify this script.</div>
<p>New users of xAPI, who have just installed the Moodle Logstore xAPI plugin are faced with the problem of extracting old data and converting it to xAPI statements in the learning record store.</p>
<p>This script is designed to take existing log data from a moodle installation, and import it — via the Logstore xAPI Moodle plugin — to the learning record store.</p>
<p>It does this by paging the <em>logstore_standard_log</em>, transferring the records to a temporary database table (of the same structure) and running export commands on the data stored there. This is what it does normally, except the <em>logstore_standard_log</em> is only parsed for the last <em>n</em> records, where <em>n</em> is set in the settngs.</p>
<p>The data is also logged to a file called<em><?phpecho($logfile);?></em>. This file is overwritten with the data from each loop and is never very long. It is also stored as JSON, which struck me as a good idea at the time.</p>
if($DEBUGGING){echo"\t</tr>\n\t<tr>\n\t\t<td colspan='5'><em>Breaking out of loop at \$count = $i.</em></td>\n\t</tr>\n";}
break;
}
}
if($DEBUGGING){echo"\t</tr>\n";}
}
if($DEBUGGING){
?>
</table>
</div><!-- end panel body -->
<divclass="panel-footer">End of Loop</div>
</div><!-- end panel -->
</div>
</div>
Note that you may want to add a `WHERE` clause to this SQL query if you only want to process some past events. For example, if you only wanted to process past events between `2018-01-01T00:00Z` and `2018-01-02T00:00Z` you would use the `WHERE` clause below, where the dates have been [converted to Unix timestamp integers](http://www.4webhelp.net/us/timestamp.php?action=date&day=01&month=01&year=2018&hour=00&minute=00&second=00&timezone=0).
</div>
</body>
</html>
<?php
}
exit;
```sql
WHEREtimecreatedBETWEEN1514764800AND1514851200
```
If you have a quick question about this script, please ask in [our Gitter chat room](https://gitter.im/LearningLocker/learninglocker) 💬, if you think there's a problem with this guide, please create a new issue in [our Github issue tracker](https://github.com/xAPI-vle/moodle-logstore_xapi/issues).
Once this SQL query has been executed, the plugin will start processing the events each time the Moodle Cron script is executed. Note that you can [run the Moodle Cron script manually](https://docs.moodle.org/20/en/Cron#Testing_cron_and_manual_trigger) if you want to and you can change the "Maximum batch size" in the plugin settings (which defaults to 30) in order to speed things up.
If you have a quick question about this process, please ask in [our Gitter chat room](https://gitter.im/LearningLocker/learninglocker) 💬, if you think there's a problem with this guide, please create a new issue in [our Github issue tracker](https://github.com/xAPI-vle/moodle-logstore_xapi/issues).
