annotate docs/ProjectSpecificationDocument.tex @ 1618:ff21abb06a37

Bug #1206: Question title more pronounced and with greater spacing.
author Nicholas Jillings <nickjillings@users.noreply.github.com>
date Sun, 24 May 2015 11:45:35 +0100
parents e5f1caa513d8
children 06fbaccf3b58
rev   line source
b@1607 1 \documentclass{article}
b@1607 2
b@1607 3 \usepackage[margin=2cm]{geometry}
b@1607 4 \usepackage{listings}
b@1607 5
b@1607 6 \begin{document}
b@1607 7
b@1607 8 \large APE Browser Tool - Project Specification Document
b@1607 9
b@1607 10 \section{Document}
b@1607 11
b@1607 12 An XML file containing all project information to load and execute the project on the client. Certain interfaces are optional, however others are mandatory. This guide should reflect the changes in the XML project and keep track of the versions. Hopwfully this can remain simple!
b@1607 13
b@1607 14 \section{Root}
b@1607 15
b@1607 16 The XML root must be \texttt{<BrowserEvalProjectDocument>}. This should be sufficiently identifiable in both itself and in the JavaScript decoding as it will create an object called the root name.
b@1607 17
b@1607 18 There must also be a \texttt{<version>} tag which has the attribute \texttt{id} containing a numerical representation of the version. Currently everything in this document can be assumed to be version 1. If future updates or corrections are made post delivery this should give the flexibility to ensure past projects still work.
b@1607 19
b@1607 20 The root will also contain the following tags: setup and tracks.
b@1607 21
b@1607 22 \section{Setup tag}
b@1607 23
b@1607 24 The setup tag specifies certain global test settings including: the interface type to use, the project return location and any other setup instructions.
b@1607 25 Any general pre/post test questions must be specified in the relevant children tag. Any enabled metrics must also be specified in the metric child node.
b@1607 26
b@1607 27 \subsection{Attributes}
b@1607 28 \begin{itemize}
b@1607 29 \item \texttt{interface} - Mandatory, String. Defaults to APE, otherwise use to load any of the available interfaces. Currently only valid string is APE.
b@1607 30 \item \texttt{projectReturn} - Mandatory, String. Specify the URL to return the test results. If null client will generate XML locally and prompt user to return the file.
b@1607 31 \item \texttt{randomiseOrder} - Optional, default to false. Specify if the order of the tests can be randomised.
b@1607 32 \item \texttt{collectMetrics} - Optional, Boolean. Default to false. Determine if the test metrics should be collected. These include how long each test session took etc. The full metrics list can be modified in the 'metrics' tag.
b@1607 33 \end{itemize}
b@1607 34
b@1607 35 \subsection{Elements}
b@1607 36 None
b@1607 37
b@1607 38 \section{AudioHolder tag}
b@1607 39
b@1607 40 There should be one audioHolder tag per test session, inside which each audioElement is specified as children. The audioHolder tag can help to generalise certain objects. Each audioHolder instance specifies a separate listening test to be paged, each with their own specific requirements.
b@1607 41
b@1607 42 \subsection{Attributes}
b@1607 43 \begin{itemize}
b@1607 44 \item \texttt{id} - Mandatory, String. Give an ID string or number to identify the test in the result.
b@1607 45 \item \texttt{hostURL} - Optional, String. If all tracks are hosted from the same folder on a server, you can put in the lead here. For instance, if loading http://test.com/tracks/track1.wav and http://test.com/tracks/track2.wav, this could equal http://test.com/tracks/ and the url attribute in the track tag can be track1.wav or track2.wav. Equally http://test.com/ and then using tracks/track1.wav and tracks/track2.wav is valid.
b@1607 46 \item \texttt{sampleRate} - Optional, Number. If your test requires a specific sample rate, this should be set to the desired sample rate in Hertz. This does not set the browser to the correct sample rate, but forces the browser to check the sample rate matches. If this is undefined, no sample rate matching will occur.
b@1607 47 \item \texttt{randomiseOrder} - Optional, Boolean String. Defaults to false. Determine if the track order should be randomised. Must be true or false.
b@1607 48 \item \texttt{repeatCount} - Optional, Number. Defaults to 0 (ie: no repeats). The number of times a test should be repeated.
b@1607 49 \item \texttt{loop} - Optional, Boolean String. Defaults to false. Enable if audioElements should loop their playback or not.
b@1607 50 \end{itemize}
b@1607 51
b@1607 52 \subsection{Elements}
b@1607 53 Contain the audioElements tags and the interfaceSetup tag.
b@1607 54
b@1607 55 \section{audioElements tag}
b@1607 56
b@1607 57 This must reside as children in the audioHolder tag. There must be one audioElement tag per sound sample to load into the test.
b@1607 58
b@1607 59 \subsection{Attributes}
b@1607 60 \begin{itemize}
b@1607 61 \item \texttt{id} - Mandatory, String. Must give a string or number to identify each audio element. This id is used in the output to identify each track once randomised.
b@1607 62 \item \texttt{url} - Mandatory, String. Contain the full URL to the track. If the Tracks tag hostURL is set, concatenate this tag with the hostURL attribute to obtain the full URL.
b@1607 63 \end{itemize}
b@1607 64
b@1607 65 \section{interface tag}
b@1607 66
b@1607 67 This is contained within the audioHolder tag and outlines test instance specific requirements. These include the following children tags:
b@1607 68 \begin{itemize}
b@1607 69 \item 'title' - Contains the test title to be shown at the top of the page. Can only be one title node per interface.
b@1607 70 \item 'scale' - Takes the attribute position to be a value between 0 and 100 indicating where on the scale to place the text contained inside. Can be multiple scale tags per interface.
b@1607 71 \end{itemize}
b@1607 72
b@1607 73 \section {CommentQuestion tag}
b@1607 74
b@1607 75 This is a 1st level tag (same level as AudioHolder and setup). This allows another question and comment box to be presented on the page. The results of these are passed back in the results XML with both the comment and the question. The id attribute is set to keep track at the results XML.
b@1607 76
b@1607 77 \section {PreTest tag and PostTest tag}
b@1607 78
b@1607 79 These are 1st level tags. The PreTest tag allows for the specifying of pre test instructions and questions. These appear as a pop-up style window with next buttons and other automatic GUI. The postTest tag allows for specifying post test instructions, questions and resources. These appear as a pop-up style window after the submit button is pressed.
b@1607 80
b@1607 81 \subsection{Attributes}
b@1607 82 None.
b@1607 83
b@1607 84 \subsection{Elements}
b@1607 85 Takes the \texttt{statement} and \texttt{question} tags. The order these are presented in the XML define the order they appear on the screen.
b@1607 86
b@1607 87 \subsubsection{Statement}
b@1607 88
b@1607 89 The statement tag simply prints the included string verbatim on a 'pop-up' window with a next button.
b@1607 90
b@1607 91 \subsubsection{Question}
b@1607 92
b@1607 93 This allows for a question to be asked pre/post the test. This is added to the response XML in the same location as the other common/global questions. The response includes both the question asked and the response. This takes two attributes, id and mandatory. ID is a mandatory field. The same ID will be used in the results so it is important it is properly entered. Mandatory is optional. True means the field must be entered before continuing.
b@1607 94
b@1607 95 \subsubsection{Resource}
b@1607 96
b@1607 97 The resource tag is only available in the postTest tag. This allows for the linking to some external resource via the href attribute.
b@1607 98
b@1607 99 \section{Metric tag}
b@1607 100 A 1st level tag, metrics must be declared in the setup tag. This takes a set of children 'metricEnable' to define which metrics to collect and present.
b@1607 101
b@1607 102 \subsection{metricEnable tag}
b@1607 103 This takes a single attribute to determine which metric to enable for collection. Some of these are a global, per track or per test instance.
b@1607 104 \begin{itemize}
b@1607 105 \item testTimer - Return the global test timer and test instance timers. Measures the time between the first start and final submit.
b@1607 106 \item elementTimer - Return the total time each audioElement in each test was listened too. Measures time between successive clicks on the track changer
b@1607 107 \item elementTracker - Return the initial position of each track
b@1607 108 \item elementTrackerFull - Return an enumerated pair of time and position. Track the entire movement of each element position. NOTE: Will override the elementTracker option above and throw an error into the browser console.
b@1607 109 \item elementFlagListenedTo - Return a boolean per elementck to see if the element was listened to
b@1607 110 \item elementFlagMoved - Return a boolean per element to see if the element slider was moved.
b@1607 111 \item elementFlagComments - Return a boolean per element to see if the element has comments.
b@1607 112 \end{itemize}
b@1607 113
b@1607 114 \section{Feature List}
b@1607 115 \begin{itemize}
b@1607 116 \item Paging listening tests - eg. Ask multiple questions in each experiment
b@1607 117 \item Labels on X axis - scale
b@1607 118 \item Input questions/comment at top to guide towards the question being asked.
b@1607 119 \item Randomise track numbers -(inc. comment boxes and relate back to correct reference track)
b@1607 120 \item Randomise order of individual tests
b@1607 121 \item Save output XML file to remote server
b@1607 122 \item Tests Metrics
b@1607 123 \begin{itemize}
b@1607 124 \item Duration of listening to each track
b@1607 125 \item Time spent on each individual test
b@1607 126 \item Start and end position of every track
b@1607 127 \item Flags on each track, to ensure each track (but may not restrict users from submitting)
b@1607 128 \begin{itemize}
b@1607 129 \item Has been listened to
b@1607 130 \item Has been moved
b@1607 131 \item Has comments about it
b@1607 132 \end{itemize}
b@1607 133 \end{itemize}
b@1607 134 \end{itemize}
b@1607 135
b@1607 136 \subsection{Advanced feature list}
b@1607 137 \begin{itemize}
b@1607 138 \item Repeat each tests number of times (2 or 3?) to remove learning / experience bias and ensure that the order is consistent
b@1607 139 \item Perform Loudness equalisation on all tracks
b@1607 140 \item Selection of test type
b@1607 141 \item Pre-test of some basic hearing test
b@1607 142 \begin{itemize}
b@1607 143 \item MUSHRA (with vertical slider per track)
b@1607 144 \item APE (Single horizontal slider)
b@1607 145 \item AB Test
b@1607 146 \end{itemize}
b@1607 147 \end{itemize}
b@1607 148
b@1607 149
b@1607 150
b@1607 151 \section{Example}
b@1607 152
b@1607 153 Here is an example XML structure
b@1607 154
b@1607 155 \begin{lstlisting}
b@1607 156 <?xml version="1.0" encoding="utf-8"?>
b@1607 157 <BrowserEvalProjectDocument>
b@1607 158 <setup interface="APE" projectReturn="null" randomiseOrder='true' collectMetrics='true'>
b@1607 159 <PreTest>
b@1607 160 <statement>Please listen to all mixes</statement>
b@1607 161 <question id="location" mandatory="true">Please enter your listening location</question>
b@1607 162 </PreTest>
b@1607 163 <PostTest>
b@1607 164 <statement>Thank you for taking this listening test.</statement>
b@1607 165 <question id="SessionID">Please enter your name.</question>
b@1607 166 </PostTest>
b@1607 167 <Metric>
b@1607 168 <metricEnable>testTimer</metricEnable>
b@1607 169 <metricEnable>elementTimer</metricEnable>
b@1607 170 <metricEnable>elementTracker</metricEnable>
b@1607 171 <metricEnable>elementFlagListenedTo</metricEnable>
b@1607 172 <metricEnable>elementFlagMoved</metricEnable>
b@1607 173 </Metric>
b@1607 174 </setup>
b@1607 175 <audioHolder id='0' hostURL="example_eval/" sampleRate="44100" randomiseOrder='true' repeatCount='1'>
b@1607 176 <interface>
b@1607 177 <title>Example Test Question</title>
b@1607 178 <scale position="0">Min</scale>
b@1607 179 <scale position="100">Max</scale>
b@1607 180 <scale position="50">Middle</scale>
b@1607 181 <scale position="20">20</scale>
b@1607 182 </interface>
b@1607 183 <audioElements url="0.wav" id="0"/>
b@1607 184 <audioElements url="1.wav" id="1"/>
b@1607 185 <audioElements url="2.wav" id="2"/>
b@1607 186 <audioElements url="3.wav" id="3"/>
b@1607 187 <audioElements url="4.wav" id="4"/>
b@1607 188 <audioElements url="5.wav" id="5"/>
b@1607 189 <audioElements url="6.wav" id="6"/>
b@1607 190 <audioElements url="7.wav" id="7"/>
b@1607 191 <audioElements url="8.wav" id="8"/>
b@1607 192 <audioElements url="9.wav" id="9"/>
b@1607 193 <audioElements url="10.wav" id="10"/>
b@1607 194 <CommentQuestion id='mixingExperiance'>What is your mixing experiance</CommentQuestion>
b@1607 195 <PreTest>
b@1607 196 <statement>Start the Test 3</statement>
b@1607 197 </PreTest>
b@1607 198 <PostTest>
b@1607 199 <statement>Please take a break before the next test</statement>
b@1607 200 <question id="testComment">How did you find the test</question>
b@1607 201 </PostTest>
b@1607 202 </audioHolder>
b@1607 203 </BrowserEvalProjectDocument>
b@1607 204 \end{lstlisting}
b@1607 205
b@1607 206
b@1607 207
b@1607 208 \end{document}