Upload iEEG data
Getting your recordings into the platform is a secure transfer into your own workspace. Once they are in, you convert them into BIDS-iEEG yourself. Here is what you may bring, how to transfer it, and how to convert it.
De-identify your data at your institution first, then transfer it into your personal workspace. From there you convert it into BIDS-iEEG using the platform's importer - a step you carry out, not an automatic one. Sharing it with a project comes afterwards.
Before you upload
Recordings must be de-identified at your institution before they are transferred. The platform protects data once it is inside, but removing direct identifiers is the contributing centre's responsibility, done first - and whether pseudonymisation is enough or full anonymisation is required depends on your transfer agreement.
Two things have to be true before any data moves:
- A Data Transfer Agreement is in place between your institution and CHUV. Nothing may be transferred without one - see How it works.
- Your recordings are de-identified, and you have the metadata that describes them.
Uploading data makes you its data controller. That responsibility is yours from the moment it arrives.
What you may upload
CHORUS.HIP is dedicated to human intracerebral EEG, and what belongs on it is iEEG data together with what is needed to make sense of it:
- iEEG recordings, and the neuroimaging that goes with them - the scans used to localize electrodes.
- Health-related clinical data that the research depends on: participant demographics, MRI findings, localization of the epileptogenic zone.
- Research data collected during iEEG studies - task descriptions, behavioural responses, derived results.
Data with no connection to an approved iEEG project does not belong on the platform, whatever its format. Uploading it goes against platform policy and may be reported.
Where uploads land
Data you upload goes into your own personal workspace first. It is private to you there, and nobody else on the platform can reach it.
Making it available to a project is a separate, deliberate step with its own conditions - covered in Share data with your project.
Upload into your workspace
Open your personal workspace
Sign in and go to the workspace the data will live in to begin with.
Open Data
From the workspace, open Data.
Start a secure transfer
Drag your de-identified files into the browser, or use the upload button. Keep the tab open until the transfer finishes - closing the browser interrupts it.
Confirm the transfer
Your files are now stored in the workspace, ready to be converted.
Browser uploads are fine for ordinary transfers but are interrupted if the tab closes. For large datasets or many files at once, use a desktop sync client instead - it resumes where it left off.
Convert to BIDS-iEEG
Uploading puts your raw files in the workspace; it does not convert them. Converting is a separate step you carry out, running the platform's integrated BIDS importer to organize and annotate your data into the standard.
The importer accepts a limited set of input formats, so check yours is among them before you plan around it. If you are not yet sure what the standard involves, read Working with BIDS-iEEG first.
What's next
If the data is for a shared project, the next step is Share data with your project - it has to pass BIDS validation to get there.
If it is for your own work, you are ready for the tutorials.