Dev/final touches

[xenoblade246]

Summary

Enabled multiple features for the transcription web-app, mainly:

• Transcript timestamping
• Speaker tagging to change speaker names to something more recognizable
• Transcript export to .txt format (for data management)
• User-defined prompts for summarization feature

---

FastAPI Application Checklist (Delete if PR is not relevant)

• API follows RESTful principles (nouns in routes, proper use of verbs)
• All endpoints are async and use non-blocking I/O
• /health endpoint is implemented and returns 200 OK
• Long-running operations support both job polling (e.g., via /status/{job_id} or /progress/{job_id}) and optional webhooks (if a callback_url is provided).
  • If callback_url is present in the request payload, the service will POST job results to the specified URL upon completion.
  • If callback_url is not provided, the client can retrieve status and results via polling endpoints.
• Job results are persisted or recoverable if needed
• API schema (OpenAPI) is exposed and browsable at /docs or /redoc
• Branch name follows conventions (e.g., feature/*, bugfix/*) — do not use dev directly

---

General Checklist

• I have tested these changes locally
• I have updated relevant documentation or added comments where needed
• I have linked relevant issues and tagged reviewers
• I have followed coding conventions and naming standards

[gemini-code-assist]

Summary of Changes

Hello @ThePrunerator, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces several key features and improvements to the transcription web application, focusing on enhancing user control over transcripts and summaries. It enables timestamping, speaker renaming, and custom summarization prompts, alongside new export options and a comprehensive documentation update, all while refining the user interface.

Highlights

• Transcript Timestamping: The backend's format_result function now includes start and end timestamps for each transcribed segment, and the frontend displays these timestamps alongside each transcript entry.
• Speaker Tagging and Renaming: New API endpoints (PATCH /jobs/{uuid}/speakers) and frontend functionality allow users to rename speakers within a transcript, making speaker identification more recognizable. The frontend also assigns unique IDs and colors to speakers.
• Transcript Export to .txt: A new feature has been added to the frontend, enabling users to export the full diarized transcript into a .txt file for data management purposes.
• User-Defined Prompts for Summarization: The summarization feature now supports custom user and system prompts, allowing for more tailored AI-generated summaries. The frontend provides input fields for these prompts.
• Meeting and Speaker Renaming: Users can now rename entire meetings via a new PATCH /jobs/{uuid}/rename endpoint, which updates the job metadata, audio file, and transcript file names. Speaker names can also be edited directly in the transcript view.
• Enhanced Documentation: A comprehensive detailed_doc.md file has been added, providing in-depth information on features, architecture, prerequisites, installation, usage, API reference, configuration, troubleshooting, and development guidelines.
• UI/UX Improvements: The frontend has undergone significant styling updates with new color themes, improved layout (transcript and summary in tabs), and visual enhancements like a particles.js background and updated fonts.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This is a substantial pull request that adds several great features and a major UI refresh. The new capabilities for timestamping, speaker renaming, and custom summarization prompts are excellent additions. The backend code, particularly for the new endpoints, is well-structured and uses robust patterns for file I/O.

I've identified a few issues, including a critical one in the .gitignore configuration and a high-severity bug in the backend's file path logic. I've also provided some suggestions to improve code quality and documentation. Once these points are addressed, this PR will be in great shape. Fantastic work!