# HG changeset patch # User Nicholas Jillings # Date 1429893724 -3600 # Node ID 439e78153e0fce231333d073ed4206cb9baaedc7 # Parent 7fd87356497a6be40d56926e7e11c5bf249186a5 Paper: Removed redundant tag example diff -r 7fd87356497a -r 439e78153e0f docs/SMC15/smc2015template.tex --- a/docs/SMC15/smc2015template.tex Fri Apr 24 17:28:28 2015 +0100 +++ b/docs/SMC15/smc2015template.tex Fri Apr 24 17:42:04 2015 +0100 @@ -283,9 +283,7 @@ \end{center} \end{figure} -The results also contain information collected by any defined pre/post questions. These are referenced against the set up XML by using the same ID so readable responses can be obtained. Taking from the earlier example of setting up a pre-test question, an example reponse would be shown as the following. - -\texttt{ Queen Mary \\University of London } +The results also contain information collected by any defined pre/post questions. These are referenced against the set up XML by using the same ID so readable responses can be obtained. Taking from the earlier example of setting up a pre-test question, an example response can be seen in Figure \label{fig:xmlOut}. Each page of testing is returned with the results of the entire page included in the structure. One `audioElement' node is created per audio fragment per page, along with its ID. This includes several child nodes including the value holding the rating between 0 and 1, the comment, and any other collected metrics. The latter include how long the element was listened for, the initial position, boolean flags if the element was listened to, if the element was moved and if the element comment box had any comment. Furthermore, each user action (manipulation of any interface element, such as playback or moving a marker) is logged along with a the corresponding time code and stored or sent along with the results. Furthermore, we also store session data such as the browser the tool was used in.