comparison docs/SMC15/smc2015template.tex @ 983:652d4c865ac8

Paper: Removed redundant tag example
author Nicholas Jillings <nicholas.jillings@eecs.qmul.ac.uk>
date Fri, 24 Apr 2015 17:42:04 +0100
parents f502f8928e9d
children 9f51f5c015a3
comparison
equal deleted inserted replaced
982:f502f8928e9d 983:652d4c865ac8
281 \caption{An Example Output XML File} 281 \caption{An Example Output XML File}
282 \label{fig:xmlOut} 282 \label{fig:xmlOut}
283 \end{center} 283 \end{center}
284 \end{figure} 284 \end{figure}
285 285
286 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. 286 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}.
287
288 \texttt{<comment id="location"> Queen Mary \\University of London </comment>}
289 287
290 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. 288 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.
291 Furthermore, we also store session data such as the browser the tool was used in. 289 Furthermore, we also store session data such as the browser the tool was used in.
292 290
293 We provide the option to store the results locally, and/or to have them sent to a server. 291 We provide the option to store the results locally, and/or to have them sent to a server.