I need to get xAPI statements which contain data on how long a user has interacted with a particular element within a slide.
\n
I have an instructions slide which describes elements on an application page. So there are hot-spots or in my case, rectangles which, when hovered over, change the state of text box. This then acts like a tooltip on a website. (See attached for a screenshot of what this looks like).
\n
I want to record if a user has accessed this tooltip but also how long for because just getting data on when a user hovers over an element does not provide useful information (as they may do so accidentally for a small fraction of time for example).
\n
The obstacles I'm facing are:
\n
1. The built-in elapsed time variables are limited to project, scene and slide level.
\n
2. There is no mouse-out (or similar) trigger which would enable me to use a Javascript interval counter to trigger on mouseover and trigger on mouseout to record a length of time the user may have been reading a particular element.
\n
I would be grateful for help on creating a robust solution for this. I really believe that the value for xAPI for our organisation is in getting a detailed picture of how users are interacting with content so we can improve our materials based on this and make predictions based on user behaviour.
\n
Many thanks
I need to get xAPI statements which contain data on how long a user has interacted with a particular element within a slide.
\n
I have an instructions slide which describes elements on an application page. So there are hot-spots or in my case, rectangles which, when hovered over, change the state of text box. This then acts like a tooltip on a website. (See attached for a screenshot of what this looks like).
\n
I want to record if a user has accessed this tooltip but also how long for because just getting data on when a user hovers over an element does not provide useful information (as they may do so accidentally for a small fraction of time for example).
\n
The obstacles I'm facing are:
\n
1. The built-in elapsed time variables are limited to project, scene and slide level.
\n
2. There is no mouse-out (or similar) trigger which would enable me to use a Javascript interval counter to trigger on mouseover and trigger on mouseout to record a length of time the user may have been reading a particular element.
\n
I would be grateful for help on creating a robust solution for this. I really believe that the value for xAPI for our organisation is in getting a detailed picture of how users are interacting with content so we can improve our materials based on this and make predictions based on user behaviour.
\n
Many thanks
My idea is that elements (text information etc) within a course are revealed by hovering or clicking. I could then measure the time people spend looking at these elements and hopefully get more information than (for example) just how long someone spent on on particular slide (as they may just have been off having a cup of tea).
But the immediate motivator is to see if people actually look at the information in slides pertaining to instructions for a given course. And then I could potentially link that to how people subsequently interact with the remainder of the material.
To do that I need quite granular information. Anyways, it's all in its early stages. And thanks once again for your help.
My idea is that elements (text information etc) within a course are revealed by hovering or clicking. I could then measure the time people spend looking at these elements and hopefully get more information than (for example) just how long someone spent on on particular slide (as they may just have been off having a cup of tea).
But the immediate motivator is to see if people actually look at the information in slides pertaining to instructions for a given course. And then I could potentially link that to how people subsequently interact with the remainder of the material.
To do that I need quite granular information. Anyways, it's all in its early stages. And thanks once again for your help.
Sounds interesting, Andrew. Once you deploy your project and gather your data, report back to us here to let us know if the metrics proved useful in refining the course.
