Creating an experiment

Click New Experiment in the navigation bar. Pick your storage provider at the top of the form and give the experiment a Title. The title is what names the thing DataPipe creates in your storage account — the Drive folder, the Dataverse dataset, or the Zenodo deposition — so pick something you will recognise there. It is set once, at creation: renaming the experiment on its dashboard later changes what DataPipe calls it, not what your storage account calls it.

The rest of the form changes with the provider. Every field DataPipe asks for is one the provider needs, and each says underneath it what the provider does with the value:

• Google Drive — nothing else is required. To keep the data somewhere specific, click Choose Drive folder and pick a parent folder. Otherwise DataPipe creates the folder in My Drive/DataPipe.
• Dataverse — the collection alias, which is the short name from your collection's URL, plus the author name, contact email, and description that Dataverse requires in the citation metadata of every dataset — it refuses to create one without them. The contact email starts filled in from your DataPipe account; change it if the address you want published on the dataset is a different one. Subject is optional, and defaults to Social Sciences.
• Zenodo — the author name and a description for the deposition. Zenodo would accept a draft without these, but it will not let you publish one, so DataPipe asks now rather than leaving you to find out at the end of data collection. Affiliation is optional.

Click Create. DataPipe makes the Drive folder, Dataverse dataset, or Zenodo deposition for you and opens the experiment dashboard, which links straight to it.

A new DataPipe experiment is not accepting data yet. It starts with data collection off, validation on, and no session limit, so nothing can be submitted until you enable data collection on the dashboard.

You pick the provider once per experiment, and it is where every file from that experiment lands. Choosing a provider

The dashboard is where you get the experiment ID your code needs, watch sessions arrive, and change any setting later. Open it from My Experiments.

• The heading shows the experiment's name, whether it is accepting data, and how many sessions have been completed.
• The details block below it holds the experiment ID — the value your code sends with every request — and a link that opens the Drive folder, Dataverse dataset, or Zenodo deposition in your own storage account.
• Data collection, Validation, Metadata and Finalize are the settings for this experiment. Every one of them can be changed while a study is running, except finalizing, which is permanent.
• Integration code has ready-to-paste snippets with your experiment ID already filled in.
• The queued files panel appears only when a submission DataPipe accepted has not reached your storage provider yet. Not seeing it is the normal state.

The completed-session count is the number of submissions DataPipe accepted, including any that are still queued for your provider. It is not a count of the files sitting in your storage, and it does not include rejected submissions or base64 file uploads.

A queued upload is retried automatically, and can be downloaded straight from the dashboard in the meantime. When an upload fails

You can rename an experiment at any time from the pencil icon beside its title, and nothing about data collection changes: the experiment ID stays the same, so your code keeps working. The new name is used inside DataPipe only. Your Drive folder, Dataverse dataset, or Zenodo deposition took its name from the title when the experiment was created, and keeps that name — rename it there yourself if you want the two to match.

The Data collection section holds four switches. Each takes effect immediately, and none of them affects data you have already collected.

• Accept new data — while this is on, your experiment ID accepts submissions from participants. Turn it off and every submission is rejected with DATA_COLLECTION_NOT_ACTIVE, so leave it off until you are ready to recruit.
• Accept base64 file uploads — a separate switch, needed only if your experiment sends binary files such as audio, video or images. Media and binary files
• Assign conditions in sequence — hands each participant the next condition number in order. Set how many conditions you have when you turn it on. Condition assignment
• Stop after a set number of sessions — refuses submissions once the count reaches the limit you set, so a study cannot overrun its recruitment target. Session limits

Two more settings sit below them, each with its own page: Validation, which is on for every new experiment and checks submissions before they reach your provider, and Metadata, which describes your data in a standard format as it arrives.

Every switch you turn on widens the path into your storage provider, so turn each one off again when collection ends. Security posture