Which members publish no letters? Confirm each zero rather than assuming it

Open
#68 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data

Research direction

Start from the harvest pipeline that builds 119th/payload/member/ and the index.json counts, and read data/members.json to reproduce the 25-member gap against the directory names. Then, for each listed bioguide, check the live site and a direct Wayback query for that host, recording one of the four outcomes as structured data the explorer can read. Done means every one of the 26 has a recorded, checked outcome and the non-true-negative cases are split out into their own fix issues; the same count still needs producing for the other thirteen explorers.

Written by the indexing model from the issue text.

Description

enhancement

Some members publish no letters at all. We should know who they are, and we should know it because we checked rather than because nothing turned up.

What the data says now

The 119th explorer's index.json (built 2026-11-06) reports members_with_letters: 529 of members_total: 555, and 119th/payload/member/ holds exactly 529 files. So 26 members have no letters in that explorer.

Comparing data/members.json against the payload directory names 25 of them (the gap between 539 and 555 is separate — see the numbers-reconciliation issue). Every one of the 25 has a website recorded, so this is not the "no site" case:

bioguide name chamber state
B001299 Jim Banks sen IN
M001212 Barry Moore rep AL
M000317 Nicole Malliotakis rep NY
L000596 Anna Paulina Luna rep FL
M001217 Jared Moskowitz rep FL
B001315 Nikki Budzinski rep IL
I000058 Glenn Ivey rep MD
L000601 Greg Landsman rep OH
M001222 Max L. Miller rep OH
S001224 Keith Self rep TX
G000600 Marie Gluesenkamp Perez rep WA
F000110 Cleo Fields rep LA
S001232 Tim Sheehy sen MT
H001099 Mike Haridopolos rep FL
H001101 Pat Harrigan rep NC
R000622 Josh Riley rep NY
B001325 Sheri Biggs rep SC
G000601 Craig A. Goldman rep TX
K000403 Mike Kennedy rep UT
B001322 Michael Baumgartner rep WA
M001245 Christian D. Menefee rep TX
F000485 Clay Fuller rep GA
G000608 Darline Graham sen SC
B001328 Everton Blair Jr. rep GA
W000832 Aisha Wahab rep CA

Why this needs confirming, not assuming

A good share of that list are newly seated in the 119th. "No letters" for a freshman may simply mean little published output yet — a true negative. But the same empty result is produced by several faults we already know about:

  • a hostname resolved to the wrong member (#7, #8)
  • a site that exists but was never captured, or captured without its letters
  • letters that exist but failed our criteria (see the letter-criteria issue)
  • letters that exist under a path the harvest did not reach

Those are not distinguishable from a genuine non-publisher by looking at a zero.

What to do

  1. For each of the 26, check the member's live site for anything letter-shaped.
  2. Check the Wayback Machine for that host directly, independent of our harvest.
  3. Record the outcome per member as one of: publishes none, publishes but not captured, captured but our harvest missed them, harvest found them but criteria rejected them.
  4. Keep that as data, not prose, so the explorer can say which it is.

Only (1) is a true negative. The other three are our faults and should become their own fixes.

Scope

The table above is the 119th only. The same count should be produced for each of the fourteen explorers; the earlier Congresses will have far more, and overlap heavily with the no-website case tracked separately.

Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 11m
Merged PRs (30d)
413

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Robin-IA/Congressional-Letters-Dev

All issues in Robin-IA/Congressional-Letters-Dev

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.