Media Versioning & Change History

📋 Summary

Introduce versioning and change history for media entries, allowing moderators and contributors to track, review, and revert changes to assets over time.

❗ Problem

Media changes are currently difficult to track:

• Images are frequently deleted and reuploaded

• No visibility into who changed what and why

• Ongoing “edit wars” between contributors and moderators

• Lost assets can be difficult or impossible to recover

• Moderation decisions lack historical context

This leads to frustration and instability in the database.

💡 Proposal

Add versioning and history tracking for media:

• Track all changes to media entries:

  • Uploads

  • Deletions

  • Edits (type, region, etc)

• Provide a visible change history log per asset

• Allow moderators to:

  • View previous versions

  • Restore or revert changes

• Optionally show reason for change where applicable

🧩 Use Cases

• A deleted image can be restored without needing reupload

• Moderators review past changes before making decisions

• Repeated disputes over the same asset are easier to resolve

• Contributors understand why an image was changed or removed

📦 Benefits

• Reduces moderation conflicts and repeated work

• Prevents loss of valuable media

• Increases transparency and accountability

• Improves overall stability of the database

⚠️ Considerations

• Storage implications for version history

• UI needs to remain simple and readable

• Access to revert functionality may need restrictions

✅ Outcome

Media versioning provides transparency and control, reducing conflicts while protecting valuable contributions within the database.