Data: Save conditional result in the database.

[samuel-duhaime]

Issue

Justification

Currently, when we need to perform data analysis, we have to implement a lot of logic for each conditional to determine if the respondent could see the question or not.

Description

Ensure that the results of the question conditions are easily accessible for the data analyst.

Possible Implementation

There are several possibilities:

• Saving the value as "undefined"
• Storing the result of each conditional for the user
• Using logs for this purpose

There might be better solutions than these, but I'm not sure.

[tahini]

You touch one core issue in Evolution currently: how can we know exactly what the user saw during survey. We found a few cases where the conditional threw errors, so the question was just not seen by the participant, totally silently. There are cases also where some questions are only visible in the participant version, but not in the interviewer, but if the participant already had this question, then it should be shown.

This also gets close to the issue with had in validation where, when changing an answer that can optentially be invalid, it erases the participant original responses because the question became momentarily invisible...

We need to review this whole flow and the relation of the conditional wrt the survey and the context. Not at all trivial and more than just saving conditional result in the database, which would solve only part of the issue.