Break down #7 into implementable work units — Phase 2: Automatic summarization #24

Closed
opened 2026-05-28 07:16:54 +00:00 by Mark · 1 comment
Owner

Phase 2: Automatic summarization

Add an LLM-based summarization step that generates a short summary for each notebook entry on creation/update. Store summary alongside entry content.

Changes needed:

  • New method summarizeTranscript() on LLMTopicExtractor (or separate TranscriptSummarizer) with different prompt, reusing existing LLMConfig infrastructure
  • Add summary TEXT column to RecordingSession entity via new migration
  • UI: show summary in session detail, regenerate button

Decomposed from transcriber#22

## Phase 2: Automatic summarization Add an LLM-based summarization step that generates a short summary for each notebook entry on creation/update. Store summary alongside entry content. **Changes needed:** - New method `summarizeTranscript()` on `LLMTopicExtractor` (or separate `TranscriptSummarizer`) with different prompt, reusing existing `LLMConfig` infrastructure - Add `summary TEXT` column to `RecordingSession` entity via new migration - UI: show summary in session detail, regenerate button --- _Decomposed from [transcriber#22](https://forgejo.tail018ac4.ts.net/Mark/transcriber/issues/22)_
Author
Owner

This issue has been decomposed into the following sub-issues:

# Title Phase Scope
#125 Break down #7 into implementable work units — Phase 2: Autom Add an LLM-based summarization step that generates a short summary for each note

Each sub-issue has been labeled with needs-triage and will be evaluated by the triage pipeline before queue routing.

This issue has been decomposed into the following sub-issues: | # | Title | Phase Scope | |---|-------|-------------| | #125 | Break down #7 into implementable work units — Phase 2: Autom | Add an LLM-based summarization step that generates a short summary for each note | Each sub-issue has been labeled with `needs-triage` and will be evaluated by the triage pipeline before queue routing.
Mark closed this issue 2026-05-28 15:37:23 +00:00
Sign in to join this conversation.
No description provided.