Skip to content

Transcription Button Does Not Reflect Existing Transcription State

Description:

Currently, the audio transcription interface displays a static "Transcribe" button for all audio files, regardless of whether the file has already been transcribed. This creates ambiguity for users, as there is no clear distinction between newly uploaded and previously transcribed audio files.

To improve user experience, the button label should dynamically reflect the transcription status of each audio file.

Expected Behavior:

  • Audio files not yet transcribed → show "Transcribe"
  • Audio files already transcribed → show "Transcribe Again"
  • While transcription is in progress → show "Transcribing..." and disable the button

Current Behavior:

  • All audio files display a static "Transcribe" button
  • No indication of previous transcription status

Proposed Solution:

  • Add a transcription status field (e.g., isTranscribed, hasTranscript, or transcriptionText) to each audio object
  • Conditionally render the button label based on this field
  • Update the state/UI after successful transcription API response
  • Ensure re-rendering reflects updated transcription status

Acceptance Criteria:

  • Button label changes based on transcription status
  • "Transcribe Again" appears for already transcribed files
  • Button shows "Transcribing..." during processing
  • Button is disabled while transcription is in progress
  • UI updates immediately after transcription completes
  • No regression in existing transcription functionality

Checklist:

  • Identify audio list rendering component
  • Add/verify transcription status field in data model
  • Implement conditional button rendering
  • Handle loading state during transcription
  • Update UI after API response
  • Test with both new and previously transcribed audio files
  • Verify edge cases and error handling