Skip to content

🤖 Generate Structured AI Meeting Summaries #75

Description

@imuniqueshiv

Description

The current AI meeting summary provides only a basic overview of the meeting. To make MeetOnMemory a true AI-powered institutional memory platform, summaries should be transformed into structured, actionable insights that are easier to read, search, and revisit.

The goal of this issue is to redesign the AI summary generation process to produce a consistent, well-structured meeting report while preserving the existing transcription and upload workflow.

Important: This issue focuses on improving the AI-generated meeting summary format and related UI. Do not modify authentication, meeting uploads, or unrelated application features.


Objective

Generate a structured AI summary that highlights the most important outcomes of every meeting instead of returning only a plain summary.

The output should be professional, easy to scan, and useful for future reference.


Suggested Files

Backend

server/controllers/
server/routes/
server/utils/
server/prompts/ (if applicable)

Frontend

client/src/pages/MeetingDetails.jsx

client/src/components/meeting-details/
├── MeetingSummary.jsx
├── SummarySection.jsx
├── DecisionCard.jsx
├── ActionItemCard.jsx
└── MeetingStats.jsx

Supporting files may be updated if necessary while keeping the implementation focused on this feature.


Features to Implement

Generate structured AI summaries containing sections such as:

Executive Summary

A concise overview of the meeting.


Key Discussion Points

Highlight the primary topics discussed during the meeting.


Decisions Made

Automatically extract important decisions and resolutions.


Action Items

Identify tasks assigned during the meeting.

Where possible include:

  • Task
  • Assignee
  • Status (if available)

Questions Raised

List important unanswered questions or follow-up discussions.


Keywords

Extract relevant keywords and topics discussed during the meeting.


Meeting Statistics

Display useful metrics such as:

  • Meeting duration
  • Participant count (if available)
  • Transcript length
  • AI processing time (optional)

UI Requirements

Display each section using reusable cards with:

  • Clear headings
  • Proper spacing
  • Consistent typography
  • Responsive layout
  • Accessible color contrast

If a section has no data, hide it or display a helpful placeholder instead of leaving empty containers.


Functional Requirements

The following functionality must remain unchanged:

  • Meeting uploads
  • AI transcription
  • Existing AI summary generation workflow
  • Authentication
  • Organizations
  • Existing APIs
  • Navigation
  • Responsive behavior

Out of Scope

Please do not:

  • Rewrite the transcription pipeline
  • Implement live meeting summaries
  • Modify authentication
  • Refactor unrelated modules
  • Change routing unnecessarily

Testing Requirements

Before submitting a Pull Request, verify:

Functionality

  • ✅ Structured summary is generated successfully
  • ✅ All available sections display correctly
  • ✅ Missing sections are handled gracefully
  • ✅ Existing meeting workflow remains unaffected

UI

  • ✅ Responsive on desktop, tablet, and mobile
  • ✅ No layout overflow
  • ✅ No console errors

Before Opening a Pull Request

Run:

npm run format:check

npm run lint

npx prettier . --check

npm run build

Ensure:

  • No formatting issues
  • No lint errors
  • Successful production build

Pull Request Requirements

Please include:

  • Summary of the implementation
  • Sample AI summary output
  • Before & After screenshots
  • Short screen recording demonstrating the new summary layout
  • Confirmation that all testing requirements were completed

Acceptance Criteria

  • AI summaries are generated in a structured format.
  • Executive Summary section is displayed.
  • Key Discussion Points are extracted.
  • Decisions Made are identified.
  • Action Items are generated where applicable.
  • Questions Raised are extracted when available.
  • Keywords are generated.
  • Meeting Statistics are displayed.
  • Existing meeting workflow remains unchanged.
  • Responsive across supported devices.
  • No console, lint, or build errors.

Notes

  • Keep this Pull Request focused only on structured AI meeting summaries.
  • The implementation should be modular so future features (participant-wise summaries, decision timelines, cross-meeting insights, etc.) can be added easily.
  • Follow the project's CONTRIBUTING.md guidelines before opening a Pull Request.

Difficulty: Medium–Advanced

Estimated PR Size: Medium (≈200–500 LOC)

Metadata

Metadata

Labels

ECSoC26Eligible for Elite Coders Summer of Code 2026 automated scoring.UI/UXadvancedenhancementNew feature or requestgood-ui+25 XP

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions