Responses to letters, and tracing an issue through to legislation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Robin-IA/Congressional-Letters-Dev
-
OCR
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Robin-IA/Congressional-Letters-Dev#852 ·
Maintainers usually reply within 1 day
-
vocabulary
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Robin-IA/Congressional-Letters-Dev#849 ·
Maintainers usually reply within 1 day
-
vocabulary
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Robin-IA/Congressional-Letters-Dev#848 ·
Maintainers usually reply within 1 day
-
vocabulary
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Robin-IA/Congressional-Letters-Dev#847 ·
Maintainers usually reply within 1 day
-
vocabulary
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Robin-IA/Congressional-Letters-Dev#846 ·
Maintainers usually reply within 1 day
All issues in Robin-IA/Congressional-Letters-Dev
Similar issues
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
[Train] An elastic ScalingConfig(num_workers=(0, 0)) is accepted and the run waits foreverPossibly taken @wguo7 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ray-project/ray#68217 ·
Maintainers usually reply within 2 days
-
PairwiseComparisonEvaluator records A when a judge's final verdict is B or C after mentioning [[A]]Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
run-llama/llama_index#24279 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
googleapis/google-cloud-python#19099 ·
Maintainers usually reply within 2 days
-
area:docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100