Help us make the archive better

Report the problem where it lives.

NEMAR is built in public across dataset repositories, the CLI and backend, the website, and the documentation. The fastest support is a specific issue or pull request in the repository responsible for the thing you are looking at.

Email [email protected]

Choose a route

One clear report is better than four vague ones.

If you are unsure, email us. Otherwise, choose the route that matches the object or behavior you want changed.

01

A specific dataset

Dataset content, metadata, quality, or citation

Use the dataset's GitHub repository in nemarDatasets. The repository link is available from the dataset detail page. This is the best place to report a wrong description, missing file, metadata correction, quality concern, DOI detail, or a concrete improvement to that dataset.

Find the dataset →

Issue or pull request?

Both are useful; they do different jobs.

Open an issue when…

  • you found a problem and want the maintainers to investigate;
  • you have an improvement idea but not a finished implementation;
  • the impact or correct solution still needs discussion.

Open a pull request when…

  • you can make a small, reviewable change yourself;
  • you are correcting documentation or a reproducible website issue;
  • the dataset owner or platform maintainer can review the proposed fix.

For dataset-specific changes, use the dataset repository even when the website is where you noticed the problem. That keeps the correction beside the data, its owners, and its version history.

Make the report actionable

Tell us what happened and what you expected.

A short, reproducible report helps a maintainer understand whether a problem belongs to one dataset, one client, or the platform as a whole.

Useful details

  • dataset ID, version, or DOI, when relevant;
  • page URL, API route, command, or BIDS file path;
  • what you expected and what actually happened;
  • small reproduction steps and the error message;
  • browser, operating system, CLI version, or other relevant environment details;
  • a screenshot or log excerpt with sensitive values removed.

Do not include

  • participant-level data or identifying information;
  • access tokens, passwords, private keys, or presigned URLs;
  • private data that is not already part of the public issue context.

For privacy, takedown, or other sensitive concerns, start with [email protected] and review the NEMAR policies .

Still not sure?

Send us the context, and we will help route it.

Email [email protected]. For a public, dataset-specific problem, an issue or pull request is usually the fastest route because it keeps the discussion attached to the thing being improved.

Contact support Read how NEMAR works