In Flow's survey editor you can define variable names for each question. This means that besides the question text that the enumerator sees in the app, data has a name that should make analysis simpler because Salim does not have to deal with long question text.
This variable name is exported when the user selects the Data analysis export. If no variable names are defined, the export holds the question text
Opportunity
In some discussions the idea popped up to create default variable names for each question for the user.
To consider
What value would this bring to the user?
What value would this bring to the technical implementation?
How would this simplify the work users do?
What about users who do not care for variable names?
Context
In Flow's survey editor you can define variable names for each question. This means that besides the question text that the enumerator sees in the app, data has a name that should make analysis simpler because Salim does not have to deal with long question text.
This variable name is exported when the user selects the Data analysis export. If no variable names are defined, the export holds the question text
Opportunity
In some discussions the idea popped up to create default variable names for each question for the user.
To consider
Issues where the topic was mentioned
https://github.com/akvo/akvo-flow/issues/2315#issuecomment-356503377 https://github.com/akvo/akvo-flow/issues/2170