Overview
St. Augustine records can move across Spanish, English, church, military, civil, and newspaper contexts. This guide keeps translation notes and name variants visible so readers do not mistake one spelling or one translated phrase for complete proof.
What this helps you learn
- Translation notes can clarify record creator, language, uncertainty, and alternate readings.
- Name variants may reflect spelling practice, language shifts, clerical choices, family usage, or OCR error.
- A careful source table distinguishes what the source says from what the researcher infers.
Careful claims
- Do not treat one translated phrase or one name variant as ancestry, descent, legal-status, tribe, DNA, identity, or membership certification.
- Do not hide uncertainty when the record language, transcription, or translation is contested.
- Do not convert colonial church or civil categories into modern identity claims without review.
Research path
- Record the original wording, translation, uncertainty note, name variant, and claim limit in separate columns.
- Compare parish, military, cemetery, newspaper, and map records before strengthening public copy.
- Route contested translation or identity-adjacent wording through Source Review and Fact Check.
Source trail
- FOBA Source Table Template – Keep wording, translation, and inference separate.
- FOBA St. Augustine Fort Mose Service Ledger Method – Use service lanes before family claims.
- FOBA Evidence Gates – Label translation-sensitive claims carefully.
Evidence note: This starter entry is educational. Add sources, dates, maps, Community Notes, and Fact Checks as research develops.