Dementia Atlas

Suggest an edit

Every record has a form. Propose a change with a source, say who you are, declare any conflict, and it becomes a GitHub issue that a maintainer safety-checks, validates and turns into a merged edit. Organisations can update their own records the same way. Nothing on Dementia Atlas is edited directly.

One gate

  1. The form on any page. Open “Suggest an edit” in the sidebar, name the field, paste the proposed value and a source URL, add your name and a way to verify you. It opens a prefilled GitHub issue; you submit it with a free GitHub account.
  2. No direct edits, by design. There is no link that edits a record in place, and pull requests that change data must reference a triaged issue. Every change passes through the same gate so it can be checked for sourcing, safety (no patient data, no medical advice, no promotional claims) and validity (the build fails on a bad id or a missing source) before anyone sees it. Contributors who can code say so in the issue and are pointed at the file.
  3. Discussion is separate from change. Questions, interpretations and “is anyone working on this” belong in the Discussions thread that the Discuss link on each page finds or starts. A discussion that ends in a fact becomes an issue.
  4. Email is not a channel. Everything goes through the public issue tracker so the discussion and the source are visible.

Which form

The page's sidebar offers the forms that fit its kind; all of them are here.

  • Suggest an edit: A field on a record is wrong or missing and you have a source.
  • Fact correction: Text on a page states something false; quote it and say what it should say.
  • Stale fact: It was true, and events have overtaken it (a readout, a withdrawal, a new guideline).
  • Trial readout: A trial has reported, been updated or been stopped.
  • Regional approval: A product was approved, filed, rejected or withdrawn in a region we do not show.
  • New object: A diagnosis, product, target, trial, company, institution, person or idea is missing.
  • Translation fix: A translated TL;DR is wrong or reads badly in your language.
  • Translation review: You speak the language and want to sign off a batch of translations.
  • Review this page: You are a clinician, scientist, regulatory specialist or patient advocate and have checked a page against its sources.
  • Accessibility: Something does not work with a screen reader, keyboard, zoom or high contrast.
  • Bug report: Something on the site is broken (not a factual error).

For companies and institutions

You may update your own record: website, headquarters, products and their stage, programmes, links. Facts only; no promotional language, no unsourced superlatives, no removing negative trials or withdrawals (those belong in the record and in the Failure museum). Identity is verified by a message from your official domain or an official account. The merged record names your organisation in its provenance line so readers know who wrote it.

What happens next

  • Triage within a week. If a source is missing we ask for one; unsourced changes are not merged.
  • The issue is assigned a review track (clinical, scientific, regulatory, patient advocate, organisation self-edit). Tracks are listed in REVIEWERS.md; the pages most in need of review are at /review/.
  • A maintainer makes the edit, runs the checks, and merges. Merged changes appear on the site at the next deploy, in the changelog and in the weekly issue. Factual corrections are also logged in CORRECTIONS.md.
  • Conflicts of interest are displayed next to review badges and in provenance lines. Contributors are credited at /contributors/.

Licence

Contributions are published as part of the Dementia Atlas corpus under CC BY-NC 4.0 (data, free for non-commercial use) and MIT (code). Submitting the form confirms you agree.