Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create development dataset by removal of PII from production data #2345

Open
Jongmassey opened this issue Feb 14, 2025 · 0 comments · May be fixed by #2329
Open

Create development dataset by removal of PII from production data #2345

Jongmassey opened this issue Feb 14, 2025 · 0 comments · May be fixed by #2329
Assignees

Comments

@Jongmassey
Copy link
Contributor

#2117 Investigated options for development datasets to reduce the need for developers to use the full prod database for local development (due to the risks of doing so).

One option is to "sanitise" or remove PII from a copy of the prod database for development (and debugging/user support) purposes.

The advantage of such an approach over generating dummy data (e.g. #2313 ) is that it is inherently a realistic representation of the prod data. This provides a greater deal of assurance that any changes made are compatible with the production data, and allows for debugging of issues with specific codelists.

#2329 is a proof of concept for doing such a thing, which has raised questions about the use of a natural (and PII-containing) key rather than surrogate for the user table.

There are also ongoing discussions about possible presence of PII in freetext fields, which should be considered.

@Jongmassey Jongmassey linked a pull request Feb 14, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant