The Impact of using ‘Back’ button in Interviews
This How-To will explain what is the impact of using the ‘Back’ button in interviews.
Let’s say for example that we have a survey with 3 questions:
And that the first question has a jump rule saying:
“If my answer is 1, I need to jump to question 3”.
Now, think of a scenario where the respondent, has answered question 1 with answer 2, proceeding to question 2 and answering it – Then, clicking the back button and going back to question 1 and changing its answer to answer 1, causing it to jump over question 2 directly to question 3.
This is problematic, how would the system know if Question 2 was answered or not? Is relevant or not? Should it show as a missing value or not?
As although it was answered, it was also skipped.
Therefore, in such scenarios the system handles it with a thing called ‘Null Response’.
If I view the result through the operations console, I will notice it will show as 0, and not as the answer itself.
Further more, if I export the data, it will be missing.
Basically ‘Null Response’ is a status given to questions that are being skipped, so that the system will know how it handle them when exporting.
This impact of the back button, might cause sometimes, a lot of inconvenience if mistakenly used by surveyors, causing big amount of data to appear as missing.
However, if you double-click on the result, and click the ‘Internal Data’ button, you would be able to see the real value of this question.
*Answers of question 2 are: (1)Test1, (2)Test2
And in order to fix that, if needed, you would need to manually change the result to a Read\Write mode such as ‘Requires Approval’, take off the ‘Null Response’ check box and update the answer in the text box.
If you wish to hide the ‘Back’ button and not to allow surveyors to go back, you can do it through the survey properties:
*Advanced note: Instead of checking all questions, you can view the interview’s log and see that behavior that caused the Null Responses.
Visit us at: http://www.dooblo.net