Where else does each letter live on the internet?

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
content

Research direction

Start from data/letter-text.jsonl, which already records a sha256 per letter; pick a single letter and its hash, then search the listed sources (agency site, Congressional Record, govinfo.gov, news coverage, other signers' sites) for an exact match. Open one candidate PDF or page, compare the hash or the visible text against the stored entry, and record the URL next to that letter. Done looks like a verified external link for a letter, with the same procedure repeated across the set; the issue does not say where the links should be written, so confirm the target file before starting.

Written by the indexing model from the issue text.

Description

enhancement

For each letter, find other copies online and link to them.

Places to look:

  • the recipient agency's own site;
  • the Congressional Record;
  • govinfo.gov;
  • news coverage;
  • the other signers' sites;
  • the member's current site, if the letter is still live there.

Why it matters:

  • A copy elsewhere can give a firmer date, the full signer list, or a better scan.
  • The archived copy is evidence that a letter existed after its original page went away.

Matching can use the PDF's sha256, which is already recorded in data/letter-text.jsonl, for exact copies. Text similarity, once the OCR is done, would catch re-scans.

🤖 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.