Content type
Wiki explainer
Primary use
Use this page to compare source lanes, place anchors, and wording limits before repeating a historical claim as settled.
What this page adds
It should add source-aware context, place anchors, wording limits, and a clearer next step than a raw claim or isolated source link can provide.
Evidence level
Starter
Claim status
Open
You should leave with a narrower question, a clearer place context, and a better sense of what the current source trail can support.
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 page adds
- It turns a topic, place, or naming question into a source-led learning page instead of leaving it as a vague claim or isolated citation.
- It separates what the current record can support from what still needs comparison, correction, or stronger evidence.
- It gives readers a next-step research path instead of pretending the page is the last word.
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.
Reader quality check
- Can you name the exact place, period, institution, or source type this page is using?
- Can you separate a direct source detail from an interpretation or community-memory reading?
- Can you identify which sentence would need a Source Table, Place Packet, or Claim Review Card before reuse?
- Can you explain what would change the wording: a new source, a contradiction, a boundary change, a name variant, or a privacy concern?
Before reusing this page
- Copy the claim only with its evidence label, place context, and uncertainty note.
- Check whether the page is explaining a source, a memory lane, an interpretation, or a working hypothesis.
- Use Source Review before turning the page into stronger identity, ancestry, legal-status, descent, DNA, membership, or Nation-language wording.
- Use Community Notes or Fact Check if a missing source, changed boundary, name variation, or contradiction would alter the public wording.
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.
What remains open
This starter should be treated as a working research surface. Dates, naming, family continuity, identity-adjacent conclusions, and disputed interpretation may still need Source Review, Fact Check, Community Notes, or stronger corroboration.
Evidence note: This starter entry is educational. Add sources, dates, maps, Community Notes, and Fact Checks as research develops.