largeTranscriptDemo.ts

import type { TranscriptData } from '@transcript-parser/types'

/**
 * Large demo transcript with 60 entries for testing virtualization and performance
 * Simulates a 15-minute team meeting with 3 speakers
 */
export const largeTranscriptDemo: TranscriptData = {
  id: 'transcript-demo-large-001',
  speakers: [
    { id: 1, name: 'Alice (Product Manager)', color: 'blue' },
    { id: 2, name: 'Bob (Engineer)', color: 'emerald' },
    { id: 3, name: 'Carol (Designer)', color: 'purple' },
  ],
  entries: [
    {
      id: '1',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 0,
      endTime: 5,
      text: 'Good morning everyone! Thanks for joining our Sprint 4 planning meeting.',
      confidence: 0.96,
    },
    {
      id: '2',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 5,
      endTime: 8,
      text: 'Morning Alice! Ready to dive in.',
      confidence: 0.94,
    },
    {
      id: '3',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 8,
      endTime: 11,
      text: 'Hi team, excited to see what we have planned.',
      confidence: 0.95,
    },
    {
      id: '4',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 11,
      endTime: 18,
      text: 'Perfect. Our main goal for Sprint 4 is to enhance the transcript viewer with virtualization and speaker analytics.',
      confidence: 0.97,
    },
    {
      id: '5',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 18,
      endTime: 23,
      text: 'I saw the spec. The virtual scrolling component looks interesting. Are we using TanStack Virtual?',
      confidence: 0.93,
    },
    {
      id: '6',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 23,
      endTime: 27,
      text: 'Exactly! TanStack React Virtual will handle our large transcript lists efficiently.',
      confidence: 0.96,
    },
    {
      id: '7',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 27,
      endTime: 32,
      text: 'What about the speaker summary panel? I have some mockups prepared.',
      confidence: 0.94,
    },
    {
      id: '8',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 32,
      endTime: 38,
      text: 'Great! The speaker summary will show statistics like segment count, duration, and percentage of total speaking time.',
      confidence: 0.95,
    },
    {
      id: '9',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 38,
      endTime: 44,
      text: 'Should we memoize those calculations? Speaker stats could get expensive with large transcripts.',
      confidence: 0.92,
    },
    {
      id: '10',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 44,
      endTime: 48,
      text: 'Definitely. Phase 4 covers performance optimization with React.memo and useMemo.',
      confidence: 0.97,
    },
    {
      id: '11',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 48,
      endTime: 54,
      text: 'I noticed the design calls for a two-column layout on desktop. Should the summary be collapsible?',
      confidence: 0.93,
    },
    {
      id: '12',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 54,
      endTime: 59,
      text: "Good question. Let's keep it always visible on desktop but stack it above the transcript on mobile.",
      confidence: 0.96,
    },
    {
      id: '13',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 59,
      endTime: 65,
      text: "The responsive breakpoint is at lg (1024px), right? I'll use Tailwind's lg: prefix for that.",
      confidence: 0.94,
    },
    {
      id: '14',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 65,
      endTime: 68,
      text: "Perfect. Now let's talk about Phase 3 - real-time updates.",
      confidence: 0.95,
    },
    {
      id: '15',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 68,
      endTime: 73,
      text: 'Will users see entries streaming in as the AI processes the video?',
      confidence: 0.96,
    },
    {
      id: '16',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 73,
      endTime: 80,
      text: "Currently Gemini returns all entries at once, but we're adding the infrastructure for streaming. The useStreamingTranscript hook will handle that.",
      confidence: 0.91,
    },
    {
      id: '17',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 80,
      endTime: 85,
      text: "Right. It's a foundation for future enhancements when we have true streaming support.",
      confidence: 0.97,
    },
    {
      id: '18',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 85,
      endTime: 91,
      text: 'Makes sense. What about the color scheme for speakers? Are we sticking with the current palette?',
      confidence: 0.93,
    },
    {
      id: '19',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 91,
      endTime: 97,
      text: 'Yes, we have six colors: blue, emerald, purple, orange, pink, and cyan. They rotate for multiple speakers.',
      confidence: 0.95,
    },
    {
      id: '20',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 97,
      endTime: 103,
      text: "I'll centralize those in a speakerColors utility file to avoid duplication across components.",
      confidence: 0.94,
    },
    {
      id: '21',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 103,
      endTime: 107,
      text: 'Excellent thinking. That ties into our Phase 4 optimization goals.',
      confidence: 0.96,
    },
    {
      id: '22',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 107,
      endTime: 113,
      text: 'For the virtualized list, how many entries should we target for smooth performance?',
      confidence: 0.92,
    },
    {
      id: '23',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 113,
      endTime: 119,
      text: "The spec calls for 1000+ entries without performance degradation. We'll only render what's visible plus an overscan of 5 items.",
      confidence: 0.93,
    },
    {
      id: '24',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 119,
      endTime: 123,
      text: 'And each entry is estimated at 120px height for the virtualizer calculations.',
      confidence: 0.95,
    },
    {
      id: '25',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 123,
      endTime: 128,
      text: 'That matches my designs. The entry cards have consistent padding and spacing.',
      confidence: 0.94,
    },
    {
      id: '26',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 128,
      endTime: 134,
      text: 'One concern - what if entries have varying heights due to long text? Should we measure actual heights?',
      confidence: 0.91,
    },
    {
      id: '27',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 134,
      endTime: 140,
      text: '120px is an estimate. TanStack Virtual will handle dynamic sizing automatically. We might refine this in Phase 4.',
      confidence: 0.96,
    },
    {
      id: '28',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 140,
      endTime: 146,
      text: 'Speaking of Phase 4, are we creating a performance benchmarking tool?',
      confidence: 0.93,
    },
    {
      id: '29',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 146,
      endTime: 152,
      text: "Yes! We'll track render times, FPS during scrolling, and memory usage. Very important for proving our optimizations work.",
      confidence: 0.94,
    },
    {
      id: '30',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 152,
      endTime: 157,
      text: 'The target is sub-100ms initial render and 60 FPS scrolling performance.',
      confidence: 0.97,
    },
    {
      id: '31',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 157,
      endTime: 162,
      text: 'What about accessibility? Should the virtualized list work with screen readers?',
      confidence: 0.95,
    },
    {
      id: '32',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 162,
      endTime: 168,
      text: 'Good catch. TanStack Virtual maintains proper ARIA attributes, but we should test with actual screen readers in Phase 5.',
      confidence: 0.92,
    },
    {
      id: '33',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 168,
      endTime: 173,
      text: "Agreed. Add that to our testing checklist. Now, let's discuss the speaker summary calculations.",
      confidence: 0.96,
    },
    {
      id: '34',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 173,
      endTime: 179,
      text: 'The mockup shows three stats per speaker: segment count, total duration, and percentage. How are those computed?',
      confidence: 0.94,
    },
    {
      id: '35',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 179,
      endTime: 186,
      text: "We'll create a calculateSpeakerStats function that iterates through entries, groups by speaker, sums durations, and calculates percentages.",
      confidence: 0.93,
    },
    {
      id: '36',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 186,
      endTime: 191,
      text: 'And we memoize those calculations with useMemo to avoid recalculating on every render.',
      confidence: 0.97,
    },
    {
      id: '37',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 191,
      endTime: 196,
      text: 'Perfect. Should speakers be sorted in the summary? By speaking time maybe?',
      confidence: 0.95,
    },
    {
      id: '38',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 196,
      endTime: 201,
      text: 'Yes, descending order by total duration. The most talkative speaker appears first.',
      confidence: 0.94,
    },
    {
      id: '39',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 201,
      endTime: 206,
      text: 'That makes sense from a UX perspective. You want to see who dominated the conversation.',
      confidence: 0.96,
    },
    {
      id: '40',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 206,
      endTime: 212,
      text: 'What about the time format? I see both MM:SS and HH:MM:SS in the spec.',
      confidence: 0.93,
    },
    {
      id: '41',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 212,
      endTime: 218,
      text: 'We use formatDuration for consistency. It shows hours only when needed, otherwise minutes and seconds.',
      confidence: 0.92,
    },
    {
      id: '42',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 218,
      endTime: 222,
      text: 'Good. Consistency across the app is important. Any questions about the export feature?',
      confidence: 0.95,
    },
    {
      id: '43',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 222,
      endTime: 227,
      text: 'The export button is in the header, correct? Does it download as plain text?',
      confidence: 0.94,
    },
    {
      id: '44',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 227,
      endTime: 234,
      text: 'Yes, plain text with timestamps and speaker labels. Format is: [MM:SS - MM:SS] Speaker: text.',
      confidence: 0.93,
    },
    {
      id: '45',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 234,
      endTime: 239,
      text: 'We could add more export formats later, but plain text is MVP for Sprint 4.',
      confidence: 0.97,
    },
    {
      id: '46',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 239,
      endTime: 245,
      text: "Makes sense. What about the empty state? When there's no transcript loaded?",
      confidence: 0.94,
    },
    {
      id: '47',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 245,
      endTime: 251,
      text: 'We show a centered message: "No transcript yet. Upload a video to generate a transcript."',
      confidence: 0.95,
    },
    {
      id: '48',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 251,
      endTime: 256,
      text: "Perfect. That guides users on what to do next. Let's move to testing strategy.",
      confidence: 0.96,
    },
    {
      id: '49',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 256,
      endTime: 261,
      text: 'Are we aiming for 80% code coverage in Phase 5?',
      confidence: 0.93,
    },
    {
      id: '50',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 261,
      endTime: 267,
      text: "Yes, at minimum. We'll have unit tests for all components, hooks, and utilities.",
      confidence: 0.92,
    },
    {
      id: '51',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 267,
      endTime: 273,
      text: 'Plus E2E tests with Playwright to verify the full user journey with large transcripts.',
      confidence: 0.97,
    },
    {
      id: '52',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 273,
      endTime: 279,
      text: 'Will we test the 1000+ entry scenario in E2E or just unit tests?',
      confidence: 0.94,
    },
    {
      id: '53',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 279,
      endTime: 285,
      text: 'Both. Unit tests verify the virtualizer logic, E2E tests verify actual scroll performance in a browser.',
      confidence: 0.93,
    },
    {
      id: '54',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 285,
      endTime: 290,
      text: 'Excellent coverage strategy. What about the demo for Sprint review?',
      confidence: 0.96,
    },
    {
      id: '55',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 290,
      endTime: 296,
      text: 'We should create a large sample transcript with 50-60 entries to really showcase the virtualization.',
      confidence: 0.95,
    },
    {
      id: '56',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 296,
      endTime: 302,
      text: 'I can generate a largeTranscriptDemo file with realistic meeting content. Good for manual testing too.',
      confidence: 0.94,
    },
    {
      id: '57',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 302,
      endTime: 307,
      text: 'Perfect. Make sure it has varied speaker distribution so the summary stats look interesting.',
      confidence: 0.97,
    },
    {
      id: '58',
      speaker: 'Carol (Designer)',
      speakerNumber: 3,
      startTime: 307,
      endTime: 313,
      text: 'Should we add any animations? Like fade-in for new entries or smooth scroll to highlighted items?',
      confidence: 0.92,
    },
    {
      id: '59',
      speaker: 'Bob (Engineer)',
      speakerNumber: 2,
      startTime: 313,
      endTime: 319,
      text: "Let's keep it simple for Sprint 4. We can add polish animations in a future sprint if needed.",
      confidence: 0.93,
    },
    {
      id: '60',
      speaker: 'Alice (Product Manager)',
      speakerNumber: 1,
      startTime: 319,
      endTime: 325,
      text: "Agreed. Our focus is performance and functionality first. Great discussion everyone! Let's make Sprint 4 a success.",
      confidence: 0.98,
    },
  ],
  metadata: {
    fileName: 'sprint-4-planning-meeting.mp4',
    fileSize: 45678901, // ~43.5 MB
    duration: 325, // 5 minutes 25 seconds
    createdAt: new Date().toISOString(),
    processedAt: new Date().toISOString(),
    videoFormat: 'video/mp4',
    model: 'gemini-2.5-flash',
  },
}