-
Notifications
You must be signed in to change notification settings - Fork 5
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
change anonymization to occur on export #187
Comments
does the command_line.py code have access to the database? If so this is nice and easy. When the export command is called, it can check if anonymization is on and if it is replaces the participant_uuid of every Node with it's hash. Then it exports the tables as per usual. This would remove a query from Rogers as well so would bring a small speed boost when running. |
@thomasmorgan Do you know the status of this? |
no, you were going to handle removal of the relevant columns from the csvs On 26 July 2016 at 14:52, Jordan Suchow notifications@github.com wrote:
|
This issue was moved to Dallinger/Dallinger#87 |
we can allow the databases to include workerIDs whilst running, however, to protect identities we can replace them all with indexes upon export. This way Wallace can use worker ids while running
The text was updated successfully, but these errors were encountered: