Inconsistency in labelling data downloads as identifiable
@becky-gilbert is already working on this.
Since Jan 22, 2025.
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
Summary
On the 'All responses' page (Study -> Study Responses -> All Responses tab), downloading 'all response data' with the default checkbox options for 'participant data to include responses' results in a file that is labelled 'identifiable'.
On the 'Individual responses' page, downloading a single response with the same checkbox options results in a file that is NOT labelled as 'identifiable'.
AFAIK, these downloads contain the same types of data, it's just that the 'all responses' option is a concatenated list of each of the individual responses.
Description
According to the help text on the All Responses page:
Files with names, global IDs, birthdates, exact ages at participation, or "additional info" fields are marked as identifiable in the filename.
For both types of response downloads, the 'Child additional information' checkbox is selected by default. This is why the 'all responses' file is labelled as 'identifiable'. Out of all of the data options that are selected by default, removing "Child additional information" is the only one that results in the absence of the "identifiable" label.
For the individual response download, downloading the response with the default settings (i.e. including "Child additional information") does NOT result in the file being labelled "identifiable". In fact, that file is never tagged as being identifiable, even when all of the PII data options are included.
Questions
- Should the "child additional information" data be included by default, given that it is considered PII?
- Do we want to add an "identifiable" label to individual response downloads, so that the labelling system is consistent with "all response" downloads?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.