-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xapi - add additional context activity representing the CMS page that the content exists on #3
Comments
I can see how this might be useful. I'm not sure if that is something H5P core should do. Is this something everyone will want? You might do this prior to sending the statements to the LRS in your own code instead? Then you can probably use CMS specific functions for the url too. A generic approach would probably have to be based on window.location, or rely on something that all CMSs that implements H5P will have to implement. |
It's the kind of thing that nobody will want until they realise after 6 months of data collection that they need it for reporting :-) There probably does need to be some CMS specific code to determine the variable and then perhaps core code to add the property? I couldn't see anything in the Wordpress plugin that does anything with xAPI. Perhaps I'm looking at the wrong plugin and the code should go here or here? In that case, maybe the core doesn't need to change. Are there equivalent plugins for the other CMSs? |
Yeah, it probably belongs in that plugin :) There is a similar one for Drupal: |
Ok. I will close this issue here then. |
JI-2706 Fix allow to submit feedback for all content types
It would be helpful to group H5P interactions that occur on a single page together with a context activity grouping. Is there any way we can fetch the id (or url) of the current CMS page and use that as a grouping context activity?
I'm guessing it would go in this function.
The text was updated successfully, but these errors were encountered: