Responses to letters, and tracing an issue through to legislation

Open
#46 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data

Research direction

This is a design-level feature that cannot start until #41 (multi-member letters) and #40 (subject vocabulary) land, since matching signers and subjects is the core mechanism. Read the harvest pipeline and explorer code first to see how a letter and its members/subjects are stored, then sketch how a letter record would link to a response, a congress.gov bill and its actions. Done means an issue page renders that chain from stored data, with a documented path from letter to legislation.

Written by the indexing model from the issue text.

Description

enhancement

Letters are one step in a chain. It would be useful to show the whole chain for an issue:

  • the letter;
  • the response to it, from the agency or company it was sent to;
  • legislation introduced on the floor about the same issue;
  • actions that followed: hearings, votes, rules.

The aim is to make it easy to trace an issue and what was done about it.

Sources to look at:

  • Responses: members sometimes post the reply next to the letter. Agencies publish some in FOIA reading rooms. Some are in the Congressional Record.
  • Legislation and actions: the congress.gov API (bills, actions, cosponsors) and govinfo.

This depends on:

  • multi-member letters (#41), so a letter's signers can be matched to a bill's sponsors and cosponsors;
  • the subject vocabulary (#40), so a letter and a bill can be matched on subject.

🤖 Generated with Claude Code

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.