historyblog
Shawn Graham
More in humanities
- John H Boyerphilosophy, 20 Nov 2026
- Lawrence Evalynliterary studies, 18 Sep 2026
- Simon Goldsteinphilosophy, 13 Aug 2026
- Gus Skorburgphilosophy, 11 Aug 2026
- Joshua Sternfeldhistory, 20 Apr 2026
What they did
Graham followed course materials from Anastasia Salter's agentic-coding-for-humanities session (MLA, January 2026) to prompt Claude Code with a question he and his child had: did the local paper, the Shawville Equity, print anything about the Whitechapel murders? Claude Code produced the one-page visualisation from the OCR analysis easily; the hard part was the OCR of a scanned, skewed newspaper with a poor machine-made text layer. He wanted to stay local, so he compared pytesseract, PaddleOCR and Surya, and ended up splitting pages along the paper's five-column layout and horizontal spacers before OCR, then stitching coordinates back together. The paper did publish stories about the Ripper.
In their words
"Claude was great and making a nice one-page html visualization from the eventual analysis of the OCR."
"But the tricky bit – 'twas ever thus – was the bloody OCR."
"I spent way too much time trying to solve what has been solved by vision models more or less but the more things we can do locally, the better."
Lessons they draw
- Source quality, not the agent, was the bottleneck: OCR and page segmentation took the effort (Graham).
- Local-only tools cost time that hosted vision models would save; he chose locality anyway (Graham).
- Bad newspaper OCR has consequences for research; he points to Ian Milligan's work on this (Graham).
Limits of this account
Short exploratory post. No model version, no accuracy figures for OCR or for the retrieved stories, and no description of how the finding about the Ripper stories was checked. The original is on Graham's own blog; Digital Humanities Now carries an editors' summary at https://digitalhumanitiesnow.org/2026/01/futzing-with-newspaper-ocr/.