otacke

<p>The “SNORDIAN’s Local User Data for H5P” plugin for WordPress amends the H5P plugin for WordPress. The latter saves the previous state of H5P content in the server’s database for users who are logged in. This plugin will, when activated, also store the previous state in the user’s browser and retrieve it from there. This enables to resume H5P content without having to be logged in.</p>
<h3>Install</h3>
<h3>Install via WordPress plugin repository</h3>
<p>Install just like any other plugin.</p>
<h3>Upload ZIP file</h3>
<ol>
<li>Go to https://github.com/otacke/snordians-local-user-data-for-h5p/releases.</li>
<li>Pick the latest release (or the one that you want to use) and download the <code>snordians-local-user-data-for-h5p.zip</code> file.</li>
<li>Log in to your WordPress site as an admin and go to <em>Plugins > Add New Plugin</em>.</li>
<li>Click on the <em>Upload Plugin</em> button.</li>
<li>Upload the ZIP file with the plugin code.</li>
<li>Activate the plugin.</li>
</ol>
<h3>Configure</h3>
<p>The “SNORDIAN’s Local User Data for H5P” plugin for WordPress does not need to be configured. In order to become active, you will go to the H5P plugin settings:<br />
1. Find “Save Content State”<br />
2. Check the option “Allow logged-in users to resume tasks”. This is required for being able to restore the previous state of H5P content in general.<br />
3. Set “Auto-save frequency (in seconds)” to the time interval that should be used. The “SNORDIAN’s Local User Data for H5P” plugin will use the same value. It’s not advisable to set this too low, because even though the “SNORDIAN’s H5P Local User Data” plugin uses the browser’s local storage, H5P will store states inside the database and creating too many calls frequently may mean much load for your server.</p>
<h3>Limitations</h3>
<ul>
<li>The state will not be stored continuously, but be bound to H5P’s core triggering respective events, see <a href="https://snordian.de/2023/03/04/how-does-resuming-an-exercise-work-in-h5p" rel="nofollow ugc">How does resuming an exercise work in H5P?</a> for details.</li>
<li>It is not possible to only store the previous state in the browser’s local storage but not in the database without changes to the H5P core (or overloading it, which this plugin does not do). So, if users are logged into WordPress and do H5P exercises, the exercises’s state will be stored inside the database.</li>
<li>Browsers limit the amount of local storage available per domain to 5MB or 10MB. This means that if users access a lot of H5P content, if H5P content stores a lot of data, or if other parts of your site use the local storage, space may run out and data may be lost.</li>
<li>Similar to H5P itself, the plugin cannot store the state of content embedded with embed codes rather than WordPress shortcodes.</li>
</ul>
<h3>Privacy</h3>
<p>Beware that (in theory) the H5P user state could contain personal information of the user if the respective exercise demands to enter personal information. The “SNORDIAN’s Local User Data for H5P” plugin does not allow you to get hold of that information – in other words: you are not processing it. However, since the H5P plugin will send the very same information to your server, dealing with privacy implications of the H5P plugin may or may not be relevant for you depending on your local privacy laws.</p>
<h3>Sponsor note</h3>
<p>The plugin was developed by <a href="https://www.sustainum.de/" rel="nofollow ugc">Sustainum</a> within the <a href="https://xr-energy.eu/" rel="nofollow ugc">XR Energy project</a>. Development work was carried out by <a href="https://snordian.de" rel="nofollow ugc">SNORDIAN</a> as a contractor.</p>
<p>“Funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Education and Culture Executive Agency (EACEA). Neither the European Union nor EACEA can be held responsible for them.”</p>


SNORDIAN's Local User Data for H5P

Allows to additionally store the H5P content type state in LocalStorage.

<p>This WordPress plugin is a simple solution to catch ’em all, those xAPI statements that have been sent by H5P (https://h5p.org) content types. It allows you to store (the most relevant) xAPI properties in the database of WordPress. It also allows you to view, filter and export these data as a CSV file for further processing.</p>
<p>Please cmp. https://www.olivertacke.de/labs/2017/12/27/gotta-catch-em-all/ and https://www.olivertacke.de/labs/2018/03/25/collecting-and-analyzing-data-with-h5p-and-opening-up-education-maybe/ for the ideas behind the plugin.</p>
<p>This plugin is NOT intended to work as a replacement for a decent Learning Record Store. It will work well for smaller platforms, but if you are expecting to track many xAPI statements, you will probably run into trouble with displaying all the data at some point.</p>
<p>This plugin is NOT intended to forward xAPI statements sent by H5P to a Learning Record Store. Please use https://github.com/tunapanda/wp-h5p-xapi if you need that functionality.</p>
<p>This plugin is NOT intended to replace the H5P plugin’s reporting or provide functionality for analysis, etc. There is no point in recreating what is already available in Learning Record Stores or what you can do yourself with a spreadsheet software, scikit-learn, etc.</p>
<p>If you need more, you should give Learning Locker (https://learninglocker.net/) a shot. It’s open, free and shiny.</p>
<p>PLEASE NOTE: H5P IS A REGISTERED TRADEMARK OF JOUBEL. THIS PLUGIN WAS NEITHER CREATED BY JOUBEL NOR IS IT ENDORSED BY THEM.</p>
<h3>GDPR</h3>
<p>Please note that as of May 25, 2018 you may have to comply with the General Data Privacy Regulation (GDPR, http://gdpr-info.eu/).</p>
<p>H5PxAPIkatchu supports the functions that WordPress offers to</p>
<ul>
<li>use suggestion for your privacy statement text,</li>
<li>export personal data of a user, and</li>
<li>delete personal data of a user.</li>
</ul>
<p>Background: If you’re using H5PxAPIkachu, by processing the xAPI statements you’re processing at least these personal data items according to art. 4 GDPR:</p>
<ul>
<li>xAPI statement: Actor/name (Full name of the Agent)</li>
<li>xAPI statement:Actor/Inverse Functional Identifier (email address, openID or account data within the host system)</li>
<li>WordPress user id (ID given by the WordPress host system)</li>
</ul>
<p>Please make sure to account for these items in your GDPR processes and documentation.</p>
<h3>Customization</h3>
<h3>Capabilities</h3>
<p>Some capabilities can be set for WordPress user roles in order to specify who<br />
should be allowed to do what:</p>
<ul>
<li>manage_h5pxapikatchu_options: Capability to change the plugin’s options</li>
<li>view_h5pxapikatchu_results: Capability to view results of content types that have been created by current user and that were stored by H5PxAPIkachu</li>
<li>view_others_h5pxapikatchu_results: Capability to view results of all content types that were stored by H5PxAPIkachu</li>
<li>download_h5pxapikatchu_results: Capability to download the results stored by H5PxAPIkachu and accessible to current user</li>
<li>delete_h5pxapikatchu_results: Capability to delete ALL data stored by H5PxAPIkachu</li>
</ul>
<h3>Hooks and filters</h3>
<p>H5PxAPIkachu provides some hooks and filters that developers can use to customize the behavior or to use H5PxAPIkachu as the basis of their own plugin.</p>
<h3>Actions</h3>
<ul>
<li>h5pxapikatchu_on_activation: Triggered on activation of H5PxAPIkachu</li>
<li>h5pxapikatchu_on_deactivation: Triggered on deactivation of H5PxAPIkachu</li>
<li>h5pxapikatchu_on_uninstall: Triggered on uninstall of H5PxAPIkachu</li>
<li>h5pxapikatchu_insert_data: Triggered when data are supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_pre_database: Triggered right before data will be inserted into the database</li>
<li>h5pxapikatchu_insert_data_post_database: Triggered right after data was inserted into the database, contains the new row’s id that was inserted to the main table</li>
<li>h5pxapikatchu_delete_data: Triggered when data are supposed to be deleted from the database</li>
</ul>
<h3>Filters</h3>
<ul>
<li>h5pxapikatchu_insert_data_actor: Allows to filter/retrieve the xAPI actor object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_verb: Allows to filter/retrieve the xAPI verb object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_object: Allows to filter/retrieve the xAPI object object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_result: Allows to filter/retrieve the xAPI result object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_xapi: Allows to filter/retrieve the complete xAPI statement string when it is supposed to be inserted into the database</li>
</ul>


SNORDIAN's H5PxAPIkatchu

Simple solution to catch 'em all, those xAPI statements that have been sent by H5P content types.

SNORDIAN's Local User Data for H5P vs SNORDIAN's H5PxAPIkatchu