Make PDFs of the non-PDF letters, then read, date and file them
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- content, data-engineering
Research direction
Start with #242 to get the confirmed list of .doc/.docx/HTML letters, then read the existing PDF letter-text pipeline to see where extraction, dating and filing happen for captured PDFs — the new generated PDFs must reuse that path. The explorer's build and labeling code is the second place to read, since the open questions (where generated PDFs live, how to flag them as generated vs captured) sit there. Done means each letter from #242 has a PDF built from its Wayback capture with source URL and timestamp, its text dated and filed, and the explorer showing a clear "generated" marker.
Written by the indexing model from the issue text.
Description
Raised by Robin. Follows #242, which lists the .doc/.docx/HTML letters.
For each letter confirmed in #242:
- Generate a PDF from the Wayback capture (Word → PDF; HTML → PDF of the letter content). Keep the original capture URL and timestamp as the source and link to it, so the archived original stays the record.
- Get the text (from the document itself, OCR only if needed) into the letter-text pipeline.
- Read it the same way as the PDFs: title in the "subject — to whom, D Month YYYY" form, date (letterhead first, then file name, then metadata, then review), topics, holder/Congress member, filing.
- Publish through the normal build, flagging in the explorer that the PDF was generated from a .doc/.docx/HTML original.
Open questions: where generated PDFs are stored (not in Wayback; possibly an archive.org item); and how the explorer labels a generated PDF versus a captured one.
🤖 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