Suggest a resource, send a correction, or join the editors.
The registry is shaped by working scientists. If a database you depend on is missing — or an entry doesn't match how the resource is used in practice — we want to hear from you.
Suggest a resource
We're particularly interested in resources that are widely used in a specific domain but under-represented in general meta-registries. If you find yourself recommending a database to colleagues repeatedly, it probably belongs here.
A useful suggestion includes:
- The resource name, URL and maintaining organisation
- One paragraph on what it is and what it's used for
- Two or three resources already in the registry it pairs with
- A canonical reference (paper, documentation, release note)
- Whether access is free, registration-gated, controlled, or paid
Send to editors@diseasedb.example with subject line Resource suggestion.
Send a correction
Found an error — a wrong figure, an outdated URL, a maintainer that has changed, a cross-reference that no longer makes sense? Corrections are the most valuable contribution we receive.
For each correction please include:
- The resource page (or category page) where the error appears
- What's currently published and what it should say
- A source we can cite — primary documentation, a release note, or a published reference
Time-sensitive corrections (a resource has been retired, a URL has moved, a major release supersedes our description) are prioritised.
Become a section editor
Each of the 9 categories in the registry is maintained by a section editor with working knowledge of the domain. If you'd like to take responsibility for one — or for a sub-area within one — write to the editors with a short note on your background and what you'd want to change.
Section editors review submissions in their area, propose new entries, and ensure the 63-resource registry reflects current practice.
What we don't publish
- Commercial products without a substantial research user-base. We cover them where they are the practical standard (UpToDate, Embase, DrugBank Pro) and note the access tier honestly.
- Pre-release resources without published documentation or a production endpoint.
- One-off datasets without an ongoing maintenance commitment. Long-lived projects only.
Other ways to help
Share the registry with colleagues, link to specific resource pages in your group's onboarding documents, or cite an entry in a methods section. The registry exists to be useful, and the most useful thing for it is to be in front of the right people.