Understanding how content edits are reviewed helps you get contributions approved faster. Here's how moderation works on VerseDB.
How Reviews Work
Most edits go through review before going live. Moderators (trusted community members) and admins evaluate submissions for accuracy, proper sourcing, and formatting.
Quick Summary
- Most edits reviewed within 24-72 hours
- Rejections include feedback to help you improve
- All approved edits are logged in content history
- Level 25+ users can auto-approve edits to empty fields
Auto-Approval for Empty Fields
Once you reach Level 25, edits that fill in empty or missing data go live immediately without waiting for review. This includes:
- Adding a character's birthplace when it was previously blank
- Filling in a missing creator bio
- Adding the first item to an empty relationship
Note
Edits to fields that already have values always go through moderation, regardless of your level. This ensures corrections and changes are reviewed for accuracy.
The Approval Workflow
1. You Submit an Edit
When you submit:
- Status changes to "Pending" (or auto-approved if Level 25+ and empty field)
- The field is locked while under review
- Moderators get notified
2. Moderator Review
Moderators see your proposed change (old vs. new value), your user level, and any notes you included. They check for accuracy, proper sourcing, neutral language, and correct formatting.
3. Decision
Approved: Changes go live, you earn XP, and the lock releases.
Rejected: Changes aren't applied, but you'll get feedback explaining why and how to fix it.
Review Timelines
| Edit Type | Typical Review Time |
|---|---|
| Simple fixes (typos, formatting) | Within 24 hours |
| Standard edits | 24-72 hours |
| Complex changes (relationships, new entities) | Up to 5-7 days |
Tip
Well-sourced edits get reviewed faster. Include references when possible.
Common Rejection Reasons
Inaccurate Information
The facts don't match official sources, or no verifiable source was provided.
Fix: Double-check against official sources and include references.
Poor Formatting
Doesn't follow VerseDB style, inconsistent capitalization, or improper field usage.
Fix: Match the formatting of existing content.
Subjective Content
Contains opinions ("best," "amazing"), promotional language, or unmarked spoilers.
Fix: Keep descriptions neutral and factual.
Incomplete Edit
Missing required info or creates inconsistencies with related content.
Fix: Fill in all related fields and check for consistency.
Plagiarism
Copied directly from Wikipedia, Marvel Database, or other sources.
Fix: Paraphrase in your own words. Never copy text verbatim.
After a Rejection
- Read the feedback - Moderators explain what needs fixing
- Make corrections - Address the specific issues raised
- Resubmit - Your revised edit goes back into the queue
Note
Rejection isn't punishment—it's feedback. Many top contributors had rejections early on. Learn from it and improve.
Content History
Every approved edit is permanently logged:
- What changed (old and new values)
- Who made the change
- When it happened
- Reference to the original submission
View edit history on any content page by clicking "View Edit History" in the sidebar. This transparency helps verify information and lets admins revert problematic changes if needed.
Story Arc Proposals
Creating new story arcs follows a stricter process since you're adding a new entity to the database:
- All fields must be complete
- Related entities (characters, issues) must already exist
- More thorough verification required
- Higher XP reward for the extra effort
FAQ
How do I speed up reviews? Submit accurate, well-sourced edits that follow formatting guidelines.
Can I appeal a rejection? Fix the issues and resubmit. If you believe the rejection was an error, contact support with additional sources.
My edit has been pending for over a week? Contact support for a status update. Delays can happen during holidays or high-volume periods.