Feature Request: Versioning of edited transcriptions #5
Description
Background
As users edit their own transcriptions—whether to correct errors, rephrase, or restructure—they need the ability to undo changes, track revisions, and recover earlier versions. This is especially important in research and teaching contexts, where users may want to review or restore earlier stages of their own work.
Requested functionality (MVP-level):
• Store each saved version of a transcription (instead of overwriting)
• Each version should be timestamped and linked to the user who made the change
• Limit to the most recent N versions per transcription (e.g. 5) for storage efficiency
• Backend API endpoints to:
• Retrieve version history for a specific transcription
• Retrieve a specific version for viewing or download
• Restore a previous version as the current active one
UI requirements (initial):
• In the editor view, add a “version history” button
• Show previous save points with timestamp and version number
• Allow user to restore an earlier version with one click
Future expansions (optional):
• Inline diffing between versions
• Tagging or labeling versions (e.g. “cleaned”, “ready for export”)
• Optional download of historical versions
Technical notes:
• Store edited transcriptions in a structured format (e.g. JSON or Markdown)
• Each version should preserve speaker/timestamp metadata
Priority:
Medium. Not required for first launch, but important for usability and data integrity.