VibeThemes

alexhal

<p>Use H5P components in WPLMS ( <a href="https://wplms.io" rel="nofollow ugc">the wordpress learning management system </a>) courses, quizzes and assignments.</p>
<ol>
<li>Works with WPLMS Course ajax mode</li>
<li>Works with WPLMS Units and Quizzes</li>
</ol>
<ul>
<li>Requires H5P for WordPress plugin :  <a href="https://wordpress.org/plugins/h5p/" rel="ugc">https://wordpress.org/plugins/h5p/</a></li>
</ul>
<p>Refer Documentation : <a href="https://wplms.io/support/knowledge-base/wplms-h5p-addon/" rel="nofollow ugc">WPLMS</a><br />
Refer WPLMS : <a href="https://wplms.io/" rel="nofollow ugc">WordPress LMS</a></p>


WPLMS H5P

otacke

<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.

WPLMS H5P vs SNORDIAN's H5PxAPIkatchu