Difference between revisions of "Relevance Condition to Multiple Fields"
Kbjarkefur (talk | contribs) |
Kbjarkefur (talk | contribs) |
||
| Line 1: | Line 1: | ||
== Best Practice == | |||
If you want to apply the same relevance code to multiple fields you should not copy your code. Copying the same code to a couple of fields could be OK depending on personal preference, but copying to 5 or more fields should always be avoided. | If you want to apply the same relevance code to multiple fields you should not copy your code. Copying the same code to a couple of fields could be OK depending on personal preference, but copying to 5 or more fields should always be avoided. | ||
A questionnaire coded like this will be much easier to be updated during the development phase or during the field work where there is little time as many other tasks are keeping the project team pre-occupied. | |||
== Code example == | == Code example == | ||
Revision as of 23:56, 12 February 2017
Best Practice
If you want to apply the same relevance code to multiple fields you should not copy your code. Copying the same code to a couple of fields could be OK depending on personal preference, but copying to 5 or more fields should always be avoided.
A questionnaire coded like this will be much easier to be updated during the development phase or during the field work where there is little time as many other tasks are keeping the project team pre-occupied.
Code example
Here is a code example that shows how a group is used so that the relevance condition does not have to be applied to each field inside the group.
Not that there is no problem to have a field to be required that is not always shown. Required mean that if the field is displayed then data needs to be recorded for this field before the enumerator is allowed to swipe pass this question.