Skip to content

Getting started on the web

NEMAR (Neuroelectromagnetic Data Archive and Resource) is where neuroscience teams archive, share, and process EEG, MEG, and iEEG datasets. This page walks you through the everyday flow: signing in, getting an account, and uploading your first dataset.

Creating a NEMAR account asks for your email, an ORCID, a GitHub handle, and a couple of consent confirmations. The CLI runs the full flow in about two minutes:

bun install -g @nemar/cli
nemar auth signup

The CLI opens a browser tab for ORCID authorization, collects the rest, and submits your account for a short admin review (typically same-day). See the sign-up page for the field-by-field breakdown.

A web sign-up flow is on the way. Until then, returning users sign in here with their existing email; the web and CLI share the same backend account.

Once web sign-in launches, you’ll sign in at the login page: enter your email, NEMAR sends a 6-digit code, and you land on your dashboard. No password.

Uploads and publication requests unlock when your account is in the active state. The dashboard tells you which state you’re in.

Once signed in, the dashboard at /dashboard lists every dataset you own. Each card shows:

  • The dataset name, modalities, and last-updated time
  • A status badge: Draft, Awaiting review, Published, Denied, or Validation failed
  • Quick actions: view detail, manage collaborators, request publication, or delete (drafts only)

Click Upload dataset in the top navigation. Drop your BIDS-formatted folder onto the page or use the file picker. NEMAR runs a quick pre-check, walks you through any issues it finds, and creates the dataset entry while your files transfer to S3 in the background. See Uploading a dataset for the full walkthrough.

Each dataset has a collaborators page at /dataset/<id>/collaborators. The owner (and any admin) can invite NEMAR users by username. Invited collaborators can push to the dataset’s git repo and view it on the dashboard. See Managing your datasets for details.

Datasets start private and stay that way until you click Request publication. An admin reviews the BIDS validation, checks the metadata, and either approves (which mints a DOI and makes the dataset public) or sends a denial with feedback you can address. See Publication review for what to expect.

Both work; most people use the web. The CLI is a power-user tool for scripted publishes, git-annex parallel uploads, and server-side workflows. See CLI vs the web if you’re weighing one against the other.