8b6184ecc5
Enterprise Meeting Knowledge Management System with: Backend (FastAPI): - Authentication proxy with JWT (pj-auth-api integration) - MySQL database with 4 tables (users, meetings, conclusions, actions) - Meeting CRUD with system code generation (C-YYYYMMDD-XX, A-YYYYMMDD-XX) - Dify LLM integration for AI summarization - Excel export with openpyxl - 20 unit tests (all passing) Client (Electron): - Login page with company auth - Meeting list with create/delete - Meeting detail with real-time transcription - Editable transcript textarea (single block, easy editing) - AI summarization with conclusions/action items - 5-second segment recording (efficient for long meetings) Sidecar (Python): - faster-whisper medium model with int8 quantization - ONNX Runtime VAD (lightweight, ~20MB vs PyTorch ~2GB) - Chinese punctuation processing - OpenCC for Traditional Chinese conversion - Anti-hallucination parameters - Auto-cleanup of temp audio files OpenSpec: - add-meeting-assistant-mvp (47 tasks, archived) - add-realtime-transcription (29 tasks, archived) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
50 lines
1.8 KiB
Markdown
50 lines
1.8 KiB
Markdown
# excel-export Specification
|
|
|
|
## Purpose
|
|
TBD - created by archiving change add-meeting-assistant-mvp. Update Purpose after archive.
|
|
## Requirements
|
|
### Requirement: Excel Report Generation
|
|
The middleware server SHALL generate Excel reports from meeting data using templates.
|
|
|
|
#### Scenario: Successful export
|
|
- **WHEN** user requests GET /api/meetings/:id/export
|
|
- **THEN** server SHALL generate Excel file and return as downloadable stream
|
|
|
|
#### Scenario: Export non-existent meeting
|
|
- **WHEN** user requests export for non-existent meeting ID
|
|
- **THEN** server SHALL return HTTP 404
|
|
|
|
### Requirement: Template-based Generation
|
|
The Excel export SHALL use openpyxl with template files.
|
|
|
|
#### Scenario: Placeholder replacement
|
|
- **WHEN** Excel is generated
|
|
- **THEN** placeholders ({{subject}}, {{time}}, {{chair}}, etc.) SHALL be replaced with actual meeting data
|
|
|
|
#### Scenario: Dynamic row insertion
|
|
- **WHEN** meeting has multiple conclusions or action items
|
|
- **THEN** rows SHALL be dynamically inserted to accommodate all items
|
|
|
|
### Requirement: Complete Data Inclusion
|
|
The exported Excel SHALL include all meeting metadata and AI-generated content.
|
|
|
|
#### Scenario: Full metadata export
|
|
- **WHEN** Excel is generated
|
|
- **THEN** it SHALL include subject, meeting_time, location, chairperson, recorder, and attendees
|
|
|
|
#### Scenario: Conclusions export
|
|
- **WHEN** Excel is generated
|
|
- **THEN** all conclusions SHALL be listed with their system codes
|
|
|
|
#### Scenario: Action items export
|
|
- **WHEN** Excel is generated
|
|
- **THEN** all action items SHALL be listed with content, owner, due_date, status, and system code
|
|
|
|
### Requirement: Template Management
|
|
Admin users SHALL be able to manage Excel templates.
|
|
|
|
#### Scenario: Admin template access
|
|
- **WHEN** admin user accesses template management
|
|
- **THEN** they SHALL be able to upload, view, and update Excel templates
|
|
|