New Blog Post - We're Just Getting Started - A Message from the VerseDB Team Read Now
We're in Beta! - We'd love your feedback! Share your thoughts
Back to Community Guidelines

Approval Process and Moderation on VerseDB

Understanding how content edits are reviewed ensures your contributions are processed quickly and accurately. This guide explains the moderation workflow, review timelines, and what happens after submission.

Overview of the Approval System

Who Reviews Edits?

VerseDB edits are reviewed by:

  • Moderators – Trusted community members with approval permissions
  • Admins – VerseDB staff with full moderation access
  • Automated System – Auto-approval for high-level users (Level 50+)

Review Criteria

Moderators evaluate submissions based on:

  • ✅ Accuracy – Information is correct and verifiable
  • ✅ Sources – Changes are supported by reliable sources
  • ✅ Formatting – Follows VerseDB style guidelines
  • ✅ Neutrality – Content is factual, not opinion-based
  • ✅ Completeness – Fields are properly filled

The Moderation Workflow

Step 1: Submission

What happens:

  • User submits a content edit
  • Edit status changes to "Pending"
  • Content lock converts to submission lock
  • Moderators are notified

For you:

  • Submission XP awarded immediately (+10 XP base)
  • You cannot edit the same field while pending
  • View submission status in your profile

Step 2: Moderator Review

What moderators see:

  • Your proposed changes (old value vs. new value)
  • Content type and field being edited
  • Your user level and trust score
  • Any notes you provided

What moderators check:

  • Is the information accurate?
  • Is it properly sourced?
  • Does it follow formatting standards?
  • Is the language neutral and factual?

Review options:

  • ✅ Approve – Accept the edit and apply changes
  • ❌ Reject – Decline the edit with feedback
  • 📝 Request Changes – Ask for revisions (via notes)

Step 3: Decision

If Approved:

  • Edit status changes to "Approved"
  • Changes go live in the database
  • Approval XP awarded (+25 XP base)
  • Content lock released
  • Confirmation email sent

If Rejected:

  • Edit status changes to "Rejected"
  • Changes are NOT applied
  • Moderator notes explain why
  • Content lock released
  • Notification email sent

Review Timelines

Standard Review Time

  • Most edits: Reviewed within 24-72 hours
  • Simple edits: Often within 24 hours
  • Complex edits: May take up to 5-7 days

Factors Affecting Review Speed

Faster reviews:

  • Simple typo fixes
  • Formatting corrections
  • High-trust users
  • Clear, well-sourced changes

Slower reviews:

  • Complex relationship changes
  • Controversial edits
  • New users with low trust scores
  • Edits requiring additional verification

Priority Consideration

While all edits are reviewed fairly, some may get faster attention:

  • ✅ Error corrections (marked errors)
  • ✅ Missing critical information
  • ✅ High-quality submissions from trusted users
  • ✅ Time-sensitive updates (new releases)

Auto-Approval System

What is Auto-Approval?

High-level users can bypass the moderation queue:

  • Level 50+: Auto-approve basic edits
  • Level 75+: Auto-approve all edits

How It Works

When you submit an edit with auto-approval:

  1. Edit is automatically approved
  2. Changes go live immediately
  3. Both submission + approval XP awarded instantly
  4. No moderator review needed

Benefits of Auto-Approval

  • ⚡ Instant updates – Changes appear immediately
  • 📈 Faster progression – Earn XP faster
  • 🎯 More efficiency – Help database faster
  • 🏆 Trusted contributor status – Recognition of quality

📌 Learn more in the Trust Scores and Auto-Approval guide.

Understanding Rejection Reasons

Common Rejection Reasons

1. Inaccurate Information

Why rejected:

  • Information contradicts official sources
  • Details are incorrect or outdated
  • No verifiable source provided

How to fix:

  • Double-check facts against official sources
  • Provide source links or references
  • Verify publication dates and details

2. Poor Formatting

Why rejected:

  • Doesn't follow VerseDB style guidelines
  • Inconsistent capitalization or punctuation
  • Improper use of fields

How to fix:

  • Review formatting guidelines
  • Match existing content style
  • Use proper capitalization and grammar

3. Subjective or Biased Content

Why rejected:

  • Contains opinions rather than facts
  • Uses promotional or biased language
  • Includes spoilers without warnings

How to fix:

  • Remove subjective phrases ("best," "worst," "amazing")
  • Keep descriptions neutral and factual
  • Separate opinions from facts

4. Incomplete Edit

Why rejected:

  • Missing required information
  • Partial fix that creates inconsistencies
  • Relationship edits without proper roles

How to fix:

  • Complete all related fields
  • Ensure consistency across related content
  • Include all necessary details

5. Plagiarism or Copyright Issues

Why rejected:

  • Copied directly from other sources
  • Uses copyrighted material improperly
  • Doesn't paraphrase source material

How to fix:

  • Paraphrase information in your own words
  • Don't copy text verbatim from other sites
  • Follow fair use guidelines

After Rejection: What to Do

1. Read the Rejection Notes

Moderators provide feedback explaining:

  • Why the edit was rejected
  • What needs to be fixed
  • Suggestions for improvement

2. Learn from Feedback

Use rejection as a learning opportunity:

  • Understand what went wrong
  • Apply lessons to future edits
  • Improve your editing skills

3. Revise and Resubmit

If you can fix the issues:

  1. Make the necessary corrections
  2. Address moderator concerns
  3. Provide additional sources if needed
  4. Submit a revised edit

4. Ask for Clarification

If rejection reasons are unclear:

  • Contact support for clarification
  • Ask in community forums
  • Request more specific feedback

📌 Repeated rejections may lower your trust score, so focus on quality over quantity.

Moderator Notes and Communication

Understanding Notes

Moderators may add notes to:

  • Explain approval decisions
  • Provide constructive feedback
  • Suggest improvements for future edits
  • Thank you for quality contributions

Types of Notes

Approval Notes:

  • "Great edit! Well-sourced."
  • "Thank you for fixing this error."
  • "Excellent addition to the database."

Rejection Notes:

  • "Please provide source for this information."
  • "Description is too opinion-based. Keep it factual."
  • "This contradicts official publisher data."

Revision Requests:

  • "Can you provide more detail?"
  • "Please fix formatting to match style guide."
  • "Add source link for verification."

Content History and Audit Trail

What is Content History?

Every approved edit is logged in the content history:

  • Field edited
  • Old value and new value
  • Who edited (user and editor IDs)
  • When edited (timestamp)
  • Edit submission ID (reference)

Viewing Content History

See the complete edit history for any content:

  1. Go to a content page (character, series, etc.)
  2. Click "View Edit History"
  3. See all approved changes chronologically

Why Content History Matters

  • 📜 Transparency – See who changed what and when
  • 🔍 Verification – Trace information back to sources
  • ⏮️ Reversibility – Admins can revert bad edits
  • 📊 Accountability – Track contributor accuracy

Special Case: Story Arc Proposals

What are Story Arc Proposals?

Creating a new story arc follows a different workflow than editing existing content.

Story Arc Approval Process

  1. Submit Proposal – Fill out complete story arc details
  2. Enhanced Review – Moderators verify all relationships
  3. Create on Approval – New story arc is created from scratch
  4. High XP Reward – Earn bonus XP for new entity creation

What's Different?

  • More thorough review – Creating new entities requires extra verification
  • Complete information required – All fields must be filled
  • Relationship validation – All related entities must exist
  • Higher standards – Proposals held to stricter criteria

📌 Story arc proposals are rewarded with higher XP due to increased effort and complexity.

Frequently Asked Questions

How can I speed up the review process?

  • ✅ Submit well-sourced, accurate edits
  • ✅ Follow formatting guidelines
  • ✅ Keep descriptions neutral and factual
  • ✅ Build trust by maintaining high approval rate
  • ✅ Level up to unlock auto-approval

Can I appeal a rejection?

Yes, you can:

  • Review the rejection notes
  • Fix the issues and resubmit
  • Contact support if you believe rejection was in error
  • Provide additional sources or clarification

What if my edit is stuck in "Pending"?

If your edit hasn't been reviewed after 7 days:

  • Check if there are special circumstances (holidays, high volume)
  • Contact support for status update
  • Ensure the edit wasn't accidentally overlooked

Do moderators see my user level?

Yes, moderators see your:

  • User level and trust score
  • Approval history and rate
  • Previous contributions
  • Specialization areas

This helps them assess edit quality and determine priority.

Can I become a moderator?

High-level contributors may be invited to become moderators based on:

  • Consistent high-quality contributions
  • Trust score and approval rate
  • Community engagement
  • Level 50+ (typically)

Next Steps

Your contributions make VerseDB better for everyone. Thank you for helping build the best comic book database!

Was this article helpful?

Please login to provide feedback

Related Articles

View All Articles

VerseDB Content Standards – Ensuring Accuracy & Quality in Comic Data

VerseDB is built on accuracy, consistency, and respect for source material. Every contributor is responsible for submitting verifiable, well-formatted information that reflects what’s actually published — not guesses, personal opinion, or speculation. All edits must be based on reliable sources such as official publisher information, printed comic credits, and other established references. Contributors are expected to follow consistent formatting for names, dates, prices, issue numbers, and descriptions; keep language neutral and factual; avoid plagiarism by writing in their own words; and clearly mark any mature or age-restricted content using the publisher’s official rating. When sources conflict, editors should prioritize primary sources (printed credits and publisher records), document discrepancies, and avoid submitting uncertain details. Every submission should aim for clarity, completeness, and traceability. These standards protect the quality and credibility of VerseDB — helping ensure that character histories, issue data, creator credits, story arcs, and publisher information remain accurate, consistent, and trustworthy for the entire comics community.

Introduction to Contributing on VerseDB

VerseDB empowers comic book fans to collaboratively build the most complete comic database online. Through its Content Edit System, registered users can edit and expand information about characters, series, issues, creators, publishers, and more. Contributors earn experience points (XP) for their submissions and approvals, progressing through 100 levels that unlock new editing privileges—from basic edits at Level 5 to full auto-approval and AI management at Level 100. Participation not only improves VerseDB’s accuracy but also builds a trust score and community reputation. Users start by submitting edits, which are reviewed by moderators unless they’ve reached auto-approval status. XP rewards, bonuses, and clear contribution guidelines help new editors learn the system and grow their influence. VerseDB’s editing framework also includes content locking to prevent conflicts and AI-generated suggestions to fill in missing data—both designed to maintain data integrity. By contributing, fans help preserve comic book history, share knowledge, and level up within a thriving, collaborative community.

Content Edit Guidelines and Best Practices on VerseDB

Contributing to VerseDB means helping build the most accurate and comprehensive comic book database online. These guidelines outline the standards every contributor should follow to ensure edits are reliable, well-formatted, and quickly approved. The foundation of great contributions rests on four core principles: accuracy, neutrality, respect for copyright, and collaboration. Every submission should be fact-checked, clearly written, and presented without bias. Contributors are encouraged to use official sources, follow consistent formatting for names, dates, and numbers, and maintain factual, spoiler-free descriptions. The guide provides detailed standards for all content types—characters, series, issues, creators, publishers, story arcs, and teams—as well as tips for managing relationships, citing sources, and avoiding common mistakes such as guessing information or copying text. By mastering these best practices, contributors improve their approval rates, strengthen their trust scores, and set an example for the VerseDB community. Accurate, respectful, and well-crafted edits ensure that VerseDB remains the definitive resource for comic book information.