Overview
Montezuma source trails can include newspaper misspellings, OCR errors, flood-related archive gaps, and local memory that fills in context. This guide turns those problems into a correction workflow instead of a stronger-than-supported public claim.
What this helps you learn
- Newspapers can provide dates, institutions, addresses, event leads, and name variants that should be checked against other records.
- OCR and spelling errors can explain why a source trail looks broken even when the local context is continuous.
- Community notes can improve the public page when they point to specific records and preserve privacy.
Careful claims
- Do not use a newspaper correction or memory gap as origin, ancestry, identity, descent, legal-status, or membership proof.
- Do not publish private family explanations for archive gaps without review.
- Do not silently correct a public claim without noting what changed and why.
Research path
- Save the original clipping or citation, the corrected reading, the reason for correction, and the claim limit.
- Pair newspaper leads with court, church, cemetery, directory, map, river, rail, and flood-record lanes.
- Submit contested or sensitive changes through Community Notes, Corrections, and Source Review.
Source trail
- FOBA Corrections Log – Public correction pathway for tightened claims.
- FOBA Community Notes – Submit source-backed additions without exposing private details.
- FOBA Montezuma River-Rail-Flood Ledger Checklist – Keep memory gaps and records in separate lanes.
Evidence note: This starter entry is educational. Add sources, dates, maps, Community Notes, and Fact Checks as research develops.