Who Dat Stats

About & Methodology

Who Dat Stats is a fan-built project focused on transparent, rigorous New Orleans Saints analytics and a curated news experience.

Read the dedicated methodology page for model-status, confidence, and limitations notes.

Data sources

  • Play-by-play metrics: Current-season team and player efficiency aggregates are computed from the public nflfastR/nflverse schedule and play-by-play release files when ingestion runs succeed. The archived 2025 snapshot remains available and labeled when current rows are missing or partial.
  • Model outputs: Season outlook, game probabilities, and drive/route breakdowns are pre-calculated and packaged with each release so production deployments always ship with a reproducible snapshot.
  • Glossary: Definitions for on-page terms such as EPA, success rate, and aDOT are curated in a shared reference module and surfaced inline for quick access.

Live ingestion

  • Current roster, schedule, and depth chart: ESPN team APIs are ingested by scheduled Netlify Functions into Supabase. Failed runs are logged and do not delete the last good snapshot.
  • Current analytics: Schedule rows update through a lightweight Netlify job. EPA/play, success rate, pass/rush splits, and conservative player aggregates are batch-computed from nflfastR play-by-play. CPOE is only shown when the source column is present; YPRR and pressure rate remain pending because nflfastR play-by-play does not provide route or pressure data.
  • Reports: Weekly reports are deterministic status summaries from ingested data, not AI-generated scouting claims.

News aggregation

  • RSS feeds from NOLA.com, WWL, ESPN, Saints Wire, Canal Street Chronicles, and The Athletic are fetched server-side.
  • Headlines, summaries, timestamps, and optional tags are cached in Supabase/Postgres.
  • Only metadata is stored—full articles remain on the publishers' sites. We respect robots.txt guidance and remove sources on request.

Operations

Production builds rely on secured environment variables for Supabase connectivity, ingestion run logging, ESPN-based roster/schedule/depth jobs, and the news ingestion automation uses authenticated requests. Specific keys, paths, and trigger endpoints stay private to protect the infrastructure.

Questions, corrections, or data source requests? Reach out and we'll review quickly—accuracy is the priority.