Caucus letters are found only by subdomain: one on a member's own site names its caucus in the text
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with address_holders.CAUCUSES to see the subdomain-only test, then locate the stored text for PAGCPCCCSLZL from #149 and search letters with text for phrases like 'we write as the ... Caucus'. Compare the hits with the CAUCUSES subdomain list and the Caucuses branch in hierarchy.csv. Done means a counted gap list, a recorded decision on whether text-identified letters follow the #24/#76 policy, and each hit tagged with its caucus plus how it was identified.
Written by the indexing model from the issue text.
Description
address_holders.CAUCUSES identifies a caucus letter by its subdomain — cpc.grijalva.house.gov, rsc.jordan.house.gov. A caucus letter posted on a member's ordinary site is invisible to that test, and at least one is.
The case found while reviewing
PAGCPCCCSLZL, reviewed in #149. Its own text says what it is:
As the House and Committee considers the extension of the Children's Health Insurance Program, we write as the Congressional Caucus for Women's Issues to express our continued support for this vital program.
It is addressed to Speaker Boehner, Democratic Leader Pelosi, Chairman Upton and Ranking Member Pallone, dated 17 March 2015, and signed by Tsongas, Titus, Adams, Bustos and others.
It arrives on a member's own site, so nothing identifies it as a caucus letter. It is not held back by #24, not counted among #76's 310, and not tagged with its caucus. The title written in #149 records it; the data does not.
Why there are probably more
Caucus letters reach us two ways and we only test for one:
- On a caucus subdomain — found today, by
CAUCUSES. - On a member's ordinary site, saying in the text which caucus wrote it — found today only if a person reads it.
The second route is the normal one for a caucus without its own subdomain, and most caucuses do not have one. #76 lists ten caucuses with named subdomains covering 124 letter rows; the Congressional Caucus for Women's Issues is not among them, and it plainly writes letters.
What to do
- Search the text for caucus self-identification — "we write as the X Caucus", "on behalf of the X Caucus", "the members of the X Caucus" — across every letter with text, and count what turns up.
- Compare that list against
address_holders.CAUCUSES, which holds the subdomain-known ones. The difference is the gap. - Decide how a text-identified caucus letter is treated. #24 holds subdomain caucus letters back pending review and #76 publishes ten of them credited to the chair. A letter found by its text is the same kind of thing and should land in the same policy, not a different one.
- Tag the caucus as a topic where one exists.
hierarchy.csvalready has aCaucusesbranch underTopics. - Record how each caucus letter was identified — subdomain or text — so the two routes stay distinguishable.
Why it matters
A caucus letter credited only to the member whose site hosted it loses the fact that a group of members wrote it together. That is the same loss as #41, by a different mechanism: #41 is about cosigners not being read from the signature block, this is about the author not being read from the first paragraph.
Related: #24 (caucus letters held back), #76 (310 caucus letters with no home), #41 (multi-member letters), #149 (where this was found).
- 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