| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:results:variables [17.03.2020 20:24] – admin | en:results:variables [26.05.2025 13:55] (current) – [Quality Indicators] cjohannes |
|---|
| ===== Completion Times ===== | ===== Completion Times ===== |
| |
| * **TIMEnnn** The variables ''TIME001'' etc. store the time (in seconds) that a participant stayed on a questionnaire page. If the participant visits the page multiple times (e.g., using the back button) these times are summed up. Generally, dwell times are rather imprecise, because they contain loading times. | * **TIMEnnn** The variables ''TIME001'' etc. store how long (in seconds) a participant has spent on a page in the questionnaire. The time from loading the page to submitting it by clicking "Next" is specified. |
| | * These times are only imprecise, as they also include loading times. The typical inaccuracy is in the range of 1-2 seconds, but can be higher in individual cases (e.g. with an unstable internet connection). More precise measurements are possible using [[:en:create:javascript|JavaScript]]: [[:en:create:javascript:latencytimer]] |
| | * The number in the name of the variable refers to the page number when "compiling the questionnaire", ''TIME007'' always refers to page 07 - regardless of where the page was displayed during the interview (e.g. because pages were skipped or presented in a different order due to rotation). |
| | * If a participant sees a page several times (e.g. by using the back button in the questionnaire), the times are added together. |
| | * If the ''loopPage()'' or ''loopToPage()'' functions are used, then the variable indicates the cumulative dwell time for all repetitions of the page. |
| | * If a respondent leaves the browser window with page 5 of the questionnaire open overnight and fills in page 5 the next day and then clicks on "Next", a dwell time >20,000 seconds (several hours) may be shown in ''TIME005''. |
| | * If several pages of the questionnaire are displayed at the same time (e.g. because one page shows no content or because ''goToPage()'' is used), the dwell time is saved for the first page that shows content. Example: Page 8 only contains a PHP code with ''setPageOrder()'', followed by page 9 with a question and a ''goToPage()'' to page 10, where a question is also shown, then the participant sees the questionnaire pages 8+9+10 all together on one page (i.e. 2 questions one below the other) and the dwell time is saved in ''TIME009''. |
| | |
| | Translated with DeepL.com (free version) |
| * **TIME_SUM** The sum of dwell times (in seconds) after correction for breaks. If the participant suspends the interview and returns later, this seems like he or she stayed on the page for a long time (hours or even days). Such times are replaced by the other participants' page median. Dwell times are identified as break if | * **TIME_SUM** The sum of dwell times (in seconds) after correction for breaks. If the participant suspends the interview and returns later, this seems like he or she stayed on the page for a long time (hours or even days). Such times are replaced by the other participants' page median. Dwell times are identified as break if |
| * they are longer than 2 hours or | * they are longer than 2 hours or |
| * When using [[:en:create:selection-textinput|Free text inputs within a selection]] (single or multiple choice selection), a option's void text input (e.g., "Other: %%___%%") is only counted as invalid data, if the appropriate option in the selection was selected. | * When using [[:en:create:selection-textinput|Free text inputs within a selection]] (single or multiple choice selection), a option's void text input (e.g., "Other: %%___%%") is only counted as invalid data, if the appropriate option in the selection was selected. |
| * **MISSREL** Percentage of missing answers weighted by the other participants answering behavior. Questions that are rarely answered (e.g., voluntary text questions) are mostly irrelevant for this value, questions that most participants have answered weight worse. The linear weighting factor for a question/item is the number of answers given to this question/item divided by how often the question/item has been asked.\\ **Note:** This value may vary, depeding on the subset of data retreived. | * **MISSREL** Percentage of missing answers weighted by the other participants answering behavior. Questions that are rarely answered (e.g., voluntary text questions) are mostly irrelevant for this value, questions that most participants have answered weight worse. The linear weighting factor for a question/item is the number of answers given to this question/item divided by how often the question/item has been asked.\\ **Note:** This value may vary, depeding on the subset of data retreived. |
| * **DEG_TIME** Negative points for extremely fast completion. This value is normed in such way that values of more than 100 points indicate low-quality data. Data quality, however, is no dichotomous attribute. If you prefer a more strict filtering, a threshold of 75 or even 50 points may as well be useful as a threshold of 200 for more liberal filtering. Note, that //TIME_RSI// is a more elaborate indicator for fast responding. | * **TIME_RSI** This parameter is documented in detail in the article [[https://ojs.ub.uni-konstanz.de/srm/article/view/7403|Too Fast, too Straight, too Weird]] (named "relative speed index"). Records with a value in the range of 2.0 and above should be considered critically. However, knowledge questions that the participant may need to research may distort the value (participants with good prior knowledge are faster). |
| * **TIME_RSI** This parameter is documented in detail in the article [[https://ojs.ub.uni-konstanz.de/srm/article/view/7403|Too Fast, too Straight, too Weird]] (named "relative speed index"). Records with a value in the range of 2.0 and above should be considered critically. However, knowledge questions that the participant may need to research may distort the value (participants with good prior knowledge are faster). | |
| * **Q_VIEWER** In the questionnaire you can enable the option "Option to view the questionnaire without answering mandatory questions". When the function is active, this variable indicates whether a participant has checked the corresponding box ("I only want to view the questionnaire"). | * **Q_VIEWER** In the questionnaire you can enable the option "Option to view the questionnaire without answering mandatory questions". When the function is active, this variable indicates whether a participant has checked the corresponding box ("I only want to view the questionnaire"). |
| |
| Whether a questionnaire has been completed in its entirety can be determined using the variables //LASTPAGE// and //FINISHED// (see above). //MISSREL// is a valuable indicator of the participant's diligence and for data records that originate from "just looking at". The time invested for completion is not a direct indicator of data quality, but very short response times (//TIME_SUM// and //TIME_RSI//) indicate that the questions were not even read. | |
| |
| |
| |
| | The variables //LASTPAGE// and //FINISHED// can be used to determine whether a questionnaire has been completed in full (see above). The proportion of missing information (//MISSREL//) is a valuable indicator of the diligence of the participant or for data sets that originate from "just having a look". Although the time invested in completing the questionnaire is not a direct indicator of data quality, very low response times (low //TIME_SUM// and high //TIME_RSI//) indicate that the questions were not even read. |
