Identifying personally identifiable information in datasets upon upload/publish
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Some datasets uploaded to the Harvard Dataverse contain personally identifiable information (PII), particularly IP address and geolocation data (longitude and latitude). PII is included (as default) in survey data when researchers use internet survey software, such as Qualtrics. Researchers should delete this PII when they upload datasets to Harvard Dataverse. I did a quick search for "LocationLatitude" (the standard variable name for latitude data in Qualtrics) and it turned up 130 such datasets. Many of these datasets do not require geolocation data as part of their analysis. I suspect that researchers had uploaded the PII because they were not careful. @adam3smith suggested that Dataverse have an automated check and alert users when they are uploading datasets with PII.
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.
Research direction
The issue names no files, tests, or entry points. Begin by tracing the dataset upload and publish workflows, then determine where PII detection and user alerts would belong; done would require an agreed scope and a verified check covering the cited IP address and geolocation data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100