meeting-request-parsing

Meeting Request Parsing Skill

Overview

This skill covers parsing JSON-formatted meeting request emails to extract key scheduling information: meeting duration, date constraints, time window constraints, and sender email.

Key Concepts

Meeting Request Structure

Typical meeting request contains:

• Duration: stated explicitly (e.g., "one-hour", "1.5 hour")
• Date: specific date requested
• Time Window: earliest and latest times when person is available
• Time Zone: explicitly stated or inferred
• Sender: email address for reply

Email Text Parsing Patterns

Common patterns in email bodies:

• Duration: "one-hour meeting", "1.5 hour", "45-minute", "30 min"
• Date: "March 9th, 2026", "March 9, 2026", "on March 9"
• Availability: "available from 10am to 2pm", "between 1:00 PM and 5:00 PM"
• Time zone: "PST", "EST", "UTC-8", etc.

Code Examples

JSON Loading and Basic Parsing

import json
import re

# Load email requests
with open('/root/test_input.json') as f:
    requests = json.load(f)

for request in requests:
    email_text = request['email_text']
    sender = request['from_email']
    print(f"From: {sender}")
    print(f"Body: {email_text}")

Extracting Duration

def extract_duration(email_text):
    """Extract meeting duration in hours"""
    # Match patterns: "one-hour", "1 hour", "1.5 hours", "45 minute", "30 min"
    patterns = [
        r'(\d+\.?\d*)\s*hour',
        r'(\d+)\s*minute',
        r'(\d+)\s*min(?!ute)',
    ]

    for pattern in patterns:
        match = re.search(pattern, email_text, re.IGNORECASE)
        if match:
            duration_str = match.group(1)
            if 'minute' in pattern:
                return float(duration_str) / 60  # Convert minutes to hours
            else:
                return float(duration_str)

    # Handle written-out numbers
    if 'one hour' in email_text.lower():
        return 1.0
    if 'one and a half' in email_text.lower() or '1.5 hour' in email_text.lower():
        return 1.5

    return None