Contributors keep VerseDB accurate. This covers the standards for accuracy, conflicting sources, writing tone, spoilers, and mature content.
For field-by-field guidance (formatting, character limits, which fields each content type has), see Content Edit Guidelines.
Accuracy#
Every submission must be based on facts you can check.
If you can't verify something, leave it blank. Incomplete data is better than incorrect data.
Different edits need different amounts of proof:
| Edit type | Sources | Examples |
|---|---|---|
| Simple | 1 | Typo fixes, formatting |
| Standard | 2 | Descriptions, dates, credits |
| Complex | 3+ | Relationship changes, major additions |
When sources conflict#
Before picking a side, check the context. Is one source newer and correcting an error? Are they describing different editions (original or reprint)? Is a retcon involved?
If a printed comic credits Writer A but a website lists Writer B, trust the printed comic.
If there's no clear answer, record both versions in the field or notes: "Sources conflict on [detail]. [Source 1] states [X]; [Source 2] indicates [Y]."
Writing tone#
Write descriptions in your own words. Keep them clear, neutral, and factual.
An issue's solicitation, the publisher's own text about the book, has its own field: Publisher Solicitation. Copy it there exactly as published. Description is for your own summary.
- Write in third person ("Batman is…" not "You play as…")
- State claims you can check ("Won the Eisner Award")
- Use present tense for current facts, past tense for history
- Add personal opinions ("the best run ever")
- Use promotional language ("Don't miss this epic saga!")
- Sensationalize or write in first or second person
- Paste a publisher's solicitation, or text from any other source, into Description
Spoilers#
- Series and character descriptions: the premise and setup are fine; avoid major plot reveals. Past events are fine for completed series.
- Issue descriptions: spoilers are allowed but should be marked. Start with
[SPOILERS] This issue reveals…and keep to the setup rather than the outcome when you can.
Mature content#
VerseDB uses one numeric age scale for every publisher, not each publisher's own letter codes. Pick the closest band:
| Value | Label |
|---|---|
| 0 | All Ages |
| 9 | 9+ |
| 12 | 12+ |
| 15 | 15+ |
| 18 | 18+ |
Publishers label the same content differently (DC's "T" is 12+ where Marvel's is 13+), so map their rating onto the nearest band instead of copying their label. Leave the field blank if the rating is unknown.
The NSFW cover flag is a separate call, and it applies to the cover artwork only. Set it when the cover itself shows nudity or explicit imagery, so the site can blur it. A book with violent or adult interior content but a tame cover gets a high age rating and no cover flag.
For mature content, add a short factual note in the description: "Content Warning: Contains graphic violence and strong language." Keep it plain and don't sensationalize.
Never submit or link to unauthorized scans, pirated comics, leaked previews, fan-made explicit content, or illegal download sites. Official publisher previews and solicitation images are fine.
Enforcement#
Moderators check each submission against these standards. Can the information be verified? Are sources named? Does the writing meet the bar? Are ratings and flags correct? Repeated problems lead to rejections with feedback, slower reviews, and possibly limits on contributing.
Careful edits count for more than many edits. A strong approval rate is the best signal you can send.