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

Suggestion: add some admonition text warning that sharing under sourcedata/ should be done carefully #1744

Closed
Remi-Gau opened this issue Mar 22, 2024 · 3 comments · Fixed by #1769
Labels
formatting Aesthetics and formatting of the spec

Comments

@Remi-Gau
Copy link
Collaborator

we want to include here some language that the specification is completely naive about whether those data can be shared. Along these lines, it would be a good place to mention that source files requiring anonymization can be stored here and still be considered "source data" (although there's been one processing step in between).

The point is, many students and young researchers may be unaware of the circumstances under which the data may or may not shared and not adding some sort of warning or language here to say: hey, discuss with your PI or your university or whoever this needs be discussed before dropping anything and using this as a means of releasing data public.

Originally posted by @oesteban in #1737 (comment)

@oesteban oesteban changed the title mention that non anonymised data can go in sourcedata Suggestion: add some admonition text warning that sharing under sourcedata/ should be done carefully Mar 22, 2024
@oesteban
Copy link
Collaborator

I've changed the title because it may be the case that data cannot be shared without anonymization and yet you want to share them after anonymization.

It's more about warning that sharing data under sourcedata/ must be done extra-carefully before any damage is done.

@Remi-Gau
Copy link
Collaborator Author

Thanks and my bad for the lack of clarity.

@PeerHerholz
Copy link
Member

Thanks for this folks!

That's something we discussed a lot in BIDSonym where we copy the OG, ie non-pseudonymized/anonymized data from the BIDS root into /sourcedata/, apply deidentification there and save the respectively pseudonymize/anonymize in BIDS root.
This might be another use case to bring up/discuss as there's not only "classic" sourcedata, ie dicoms or so, but also BIDS dataset(s) before pseudonymization/anonymization. I'm of course happy to adapt things given the outcomes of this discussion/new guidelines proposed here.

Thanks again.

@Remi-Gau Remi-Gau moved this to Todo in Easy, housekeeping Apr 11, 2024
@Remi-Gau Remi-Gau moved this from Todo to In Progress in Easy, housekeeping Apr 11, 2024
@Remi-Gau Remi-Gau added the formatting Aesthetics and formatting of the spec label Apr 16, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Easy, housekeeping Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
formatting Aesthetics and formatting of the spec
Projects
Development

Successfully merging a pull request may close this issue.

3 participants