Dear @tinok,
Thanks for your quick reply and the ideas.
- Deleting the name before submission
We already discussed this
Not a preferable option, as we have a long questionnaire with several household and individual parts and with repeats and groups to structure it. So, the enumerator would need to move back to each repeat case, move to the name field and set something like “xxx” (as it must be required). Finally navigate to the end and finalise. Maybe even have to navigate back again, if a name-remove was missed. You may imagine: For a 10-person-member household, the navigation alone will be about 50 extra clicks.
Your kf link didn’t work (login screen). Can you provide your XLSForm, please?.
- Use a device instead of names
Even more confusing and error-risky probably, as an additional association has to be managed mentally by the respondent and the interviewer. And we use ${Name} references in many dynamic labels (and group titles too).
- Register initials instead of names
We discussed to only use first names (or pseudo-names, like “younger son”).
Nice idea to abbreviate, but this is a systematic recode, so not really liked by data protection controllers. Furthermore. the interviewer would need to re-translate the abbreviated ${Name} references in the question labels during the interview.
So far, the best and most practical solution, we are looking for, is a way to use first name during interview and then automatically remove the name references on sent (or finalisation).
This is, as far as I know, an often used approach in Census and international household surveys also.
Still hopeful for a smart solution.
Kind regards
Wolfgang
