Share data with your project
Data you upload starts out private to you. Making it available to a project team is a deliberate step, with conditions attached - and sharing it does not hand over control of it.
Your data has to be valid BIDS-iEEG, and the principal investigator has to approve it entering the project. Once shared, it stays yours: your agreement is needed for anything published from it, and you can withdraw it at any time.
The two places data can be
Your personal workspace is private to you. Nobody else on the platform can see what is in it, including your own colleagues.
A collaborative workspace belongs to a project and is shared with its team. The project's principal investigator is responsible for it - who the members are, what role each one holds, and closing it when the project ends.
For how workspaces work in general - isolation, roles, permissions - see Workspaces in the CHORUS tab.
Before you can share
Three things have to be true:
- The data is valid BIDS-iEEG. Validation is a gate on the collaborative workspace, not a suggestion. See Working with BIDS-iEEG.
- The project accepts it. The principal investigator approves what enters the workspace.
- Your transfer agreement covers this use. Sharing data for a purpose it was not collected or transferred for is not something the platform can put right for you.
Moving the data
Confirm you are a member of the project
The principal investigator adds you to the collaborative workspace. Until then it is not visible to you.
Check the data validates
Run the BIDS validation on the dataset in your personal workspace and fix anything it reports.
Transfer it into the project workspace
Use the platform's own transfer tools.
Wait for approval
The principal investigator approves the transfer before the data becomes available to the rest of the team.
Data moves between workspaces through the platform, so that every transfer is approved and recorded. Extracting it and putting it back by hand defeats the controls that make the project auditable - and taking anything out is an export, which is reviewed. See Exporting results.
What you keep control of
Sharing data with a project does not transfer authority over it. As its data controller, you keep two rights that matter:
- Publication needs your agreement. Anything published from a project has to be approved by every data controller whose data it draws on - not by the project alone.
- You can withdraw your data. If the terms it was provided under no longer hold, you can remove it from the project at any time.
The old documentation described three spaces - private, collaborative and public. There are now two workspaces, personal and collaborative, and "public" describes a project being discoverable rather than a place data is published to. The governance has not changed: data controllers still decide how their data is used.
What's next
With your data in the project, you are ready for the analysis workflows - the tutorials walk through them end to end.