Dear @stephanealoo, dear @Kal_Lam,
Allow us to come back to this discussion, after European Data Security regulations have been restricted again.
The data security department asked us to NOT store any person-references. So, we are looking for a solution to control this. We followed the approach from Stephane from the beginning, we only use first names (or pseudo-names) in the interview process (and in monitoring) during field work.
As we have a comprehensive Household and Individual questionnaire, we need to reference a person during the interview. Having bigger and heterogenous households, things like “my third oldest child” or the “younger brother of my wife” would become confusing for the (main) respondent and the interviewer and create severe data quality issues if a reference gets mixed up.
To use a first name seems a smarter solution, but then we need to remove this “name” BEFORE (or during) data transmission to the OCHA server. To let the interviewer do this manually at the whole end of each interview, i.e. before transmission (or finalisation) doesn’t seem a practicable solution, as this would need moving back with complex navigation in repeat groups, esp. in bigger households.
So, we are urgently looking for a possibility to create an automatic solution to remove the “names” (delete, set to “xxx” …) or find another approach. Is there any option or trick (like using bind and setvalue, or getting a script to intervene before transmission)?
Side-note: We know a way to remove the “names” later before data export from the server for analysis (making a new version of the form without the “name” variable and exporting with it), but this is too late for EU demands.
Encryption & Briefcase is not a solution for us, as sensitive data will even be exported locally.
Maybe also @Xiphware can help?
Thanks in advance and kind regards
Wolfgang
