codeforboston / codeforboston/maple
Transcription Summaries
- Dominant language
- TypeScript
- Stars
- 56
- Forks
- 175
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 13
Description
## Problem
Now that we have transcriptions of hearings, we want to help users better understand those transcriptions (which can be quite long, as one might imagine given hearings can last hours).
To that end, we should generate summaries of transcriptions so users can quickly understand key facts about the hearings.
For now, we should assume that we will generate fixed summaries of transcriptions once per hearing - potential future work along these lines may delve into interactive summaries driven by user questions.
## Success Criteria
- [ ] Take transcripts from hearings and generate a fixed summary
- [ ] Should be a one (or a few) paragraph summary of what happened
## Future Work
Interactive Summaries that can answer questions like
- What are the most impactful statements?
- What are the statements of people who aligned along similar values?
- What bills received the most attention during the hearing?
## Open Questions
- Need to get input from stakeholders (e.g. via OEWG) about what should be in the summaries.
Contributor guide
Assessment
This issue has not been assessed yet.