Each finished interview has its own system log.
This system log basically show’s all the events that happened during the interview, making it easy to understand particular behavior that look suspicious.
This How-To will demonstrate how to view this log.
Go to the operations console of the survey, double click the specific result, and click on Advanced -> View Log:
2. You will than be able to view & search the interview field log.
Here you can view the exact route that happened in the interview in order to find internal system information you need, if there’s any suspicious behavior in an interview.
This is one of our main tools in order to de-bug and find problems in interviews, now you can use it too.
Common actions that can be reviewed in the Log tab:
- Action Time Stamp: Each action that occurred during the interview has its time stamp shown on the left, under the "Date" column, so you can know what happened at what time:
- View what answers were answered to what questions: The log will show a summary of each page that was displayed in the interview, showing what question was asked in that page and what answers were answered.
The question will be shown as "Q<shortID>[QuestionIndex][InternalSystemID]", like this:
An answered answer will be shown as "A[AnswerIndex] AID[InternalSystemID]", like this:
- Entrance Rules: If a question's page was not shown due to a 'false' entrance rule the question has, this will be shown as an action in the log. For example, in the following survey, Q6 has an entrance rule to be asked only if the answer to Q5 was 1:
And in the following interview, we can see that the answer to Q5 was NOT 1, thus Q6 was NOT shown:
- Answers / Topics Filtering: The log will track any answers / topics filtering that occurred in a question. For example, in this survey, Q8 had a filtering code to filter answers selected in Q7:
And in this interview, these were the answers selected in Q7:
In the next page where Q8 is displayed, we can see that filtering action, and what answers were eventually shown, which is the same answers that were selected in Q7:
- Next / Back navigation: The log captures each "Next" and "Back" navigation done by the surveyor after each displayed page:
"User Action: false" means the interview advanced to the next page automatically (not manually bu the user), as usually happens by default after answering a single choice question for example. "User Action: true" means the surveyor manually clicked on the "Next" / "Back" buttons.
- Interview Stopped and Continued in the middle: The log will show when an interview was stopped in the middle by the action "Subject Saved", as shown here:
When an interview is re-entered again, it will first show the app's details:
The page it continued from:
And an action indicating the subject was re-entered:
- Silent Recording: when there's a silent recording configuration, the log will show when a recording started and stopped, with additional details such as if the recording started successfully or not, and if there were any issues. For example, this is a recording that started successfully once page 8 was entered:
And here's where it indicates the recording was stopped, once advancing from that page:
- Attachments capturing: When an attachment is captured (such as silent recording or other media file that is dynamically captured during the interview), its capturing details will be shown in the log. For example, the following shows that a "JPG" attachment was added in Q10 (which is a multimedia question in this case), and it shows the file name and size:
- Location capturing: The automatic location, once captured by the system, will be shown in the log like this:
- Hide / Show Survey: While the interview is running, the surveyor can "hide" the SurveyToGo app, meaning, move it to the background (without actually closing it, thus without stopping the interview) while opening another app and / or doing other things with the device. When this action happens, it will be tracked in the log. Here we can see the app was hidden:
And here is where it was shown again:
- Device's clock changed: As the interview log timestamps are based on the device's clock, it will also show us if and when there might have been a clock change, while the interview was running or while it was stopped in the middle.
This is an example of an interview that was stopped in the middle and show an obvious clock change that occurred while it was saved on the device and before it continued:
This was the time when it was stopped:
And this was the time it continued (almost 9 hours later):
Although this doesn't indicate a definite clock change (maybe the surveyor did continue the interview 9 hours later...), there's another indication that make this action as suspected clock change, and that's the Upload time that can be shown in the observation:
It shows the survey ended at 6:25PM but was uploaded before it was ended, at 9:16AM, which doesn't make sense. So with this it seems that while the interview was stopped, the device's clock was indeed changed.
This is another example of a clock change, but this time it happened while the interview was running, possibly while it was hidden in the background. Here, on top of the difference in the timestamps, the system will also catch this as a Flag and indicate it in the Log:
- Interview submission: The "Submit" action will also be shown in the log, indicating the interview was completed:
Device Info tab:
The log tab the Device Info tab details information about the device itself used in the interview, for example information about the GPS settings can be found in this tab:
The vars tab hold information about the values that were set for all the global variables defined in the survey:
The Durations tab will show a detailed timeline of the interview, showing when it was hidden and shown again. The sum of the "CurrentDurationInSeconds" column indicates the interview's Net duration value. In the below screenshot for example, the total time that the interview was shown was 47 seconds (that is the Net duration was 47 seconds):
Visit us at: http://www.dooblo.net