Two MS within a half-mile: one screens, one zones. Same neighborhood, different futures.
A reproducibility log: the data this analysis touched, the queries it ran, the outside sources it leaned on, and the steps a third party would follow to re-run it.
Summary
Paired geographically-adjacent middle schools where one is SCREENED and one is ZONED; pulled their outcome comparisons.
Data sources
- Database tableschools
One row per New York City public school (DBN, name, district, borough, school_type, grade_band, latest_enrollment, proclivity_decile, proclivity_score, closed_at, admission_category).
- Database tableschool_year_metrics
Long-format per-school per-year metric facts (school_dbn, year, metric_key, subgroup, value, suppressed). Loaded from DOE/NYSED public files via scripts/loaders/*.
Steps
Identify MS pairs within the same district where one is SCREENED and one is ZONED.
For each pair, compare academic composite, FRL %, ELL %, attendance.
Caveats
Spatial adjacency doesn't equalize sorting — screened schools draw from a wider catchment by design.
Reproduce
Clone the repo, set DATABASE_URL to a Postgres with the project schema loaded, run `npx tsx scripts/loaders/<source>.ts` for any not-yet-loaded data, then issue the queries in the Steps section. The story page also lists the exact `metric_key`/`subgroup`/`year` filters used. Searchable by the answer's headline number — every figure is recomputable from the queries shown.
The recipe lives at data/stories/recipes.ts in the repo. Corrections welcome.