Glasgow Surname Project

Individual research record

John Glasgow

1869-12-11 – 1931-08-20

Glasgow-683 · 1 mapped association

Coffee County, Tennessee, United StatesBedford, Tennessee, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
1Close relations
4Evidence items
7Candidate leads
Birth
1869-12-11 · Coffee County, Tennessee, United States
Death
1931-08-20 · Bedford, Tennessee, United States
Parents
John Glasgowunmarked
Spouses
Not recorded
Children
Not recorded
Gender
Male
WikiTree
Glasgow-683
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
0

Comparison context

These child positions and checks are the subject details used to rank possible parents below.

Naming sequence used by the parentage model

Paternal grandfather positionNot identifiable from dated child profiles
Maternal grandfather positionNot identifiable from dated child profiles
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 0 support · 0 conflict. Ordinals retain unnamed children and recognise reused names.

Relationship comparison

Potential parents or duplicates

Compare scored leads with the subject details above—not proof.

Higher-signal leadReview carefullyWeak lead

No named children are recoverable, so child-naming analysis cannot be run.

How parent leads are calculated

Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.

Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage.

Automated fit43/100
Similar Person
Dates1869–1919PlacesUlverston, Lancashire, England, United Kingdom → Burnley, Lancashire, England, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)

unassessed father attachments differ (−5)

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)

Conflicts: unassessed father attachments differ (−5)

Same-name candidate

John GlassgoGlassgo-7

Automated fit43/100
Similar Person
Dates1869–?PlacesNorth Carolina, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)

unassessed father attachments differ (−5)

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)

Conflicts: unassessed father attachments differ (−5)

How duplicate leads are calculated

Dates are eligibility gates, not merely deductions: chronologically impossible people are excluded. Dates, places, spouses, parent certainty and children's profiles and names are then compared. A high score is a prompt to inspect records, not a merge recommendation.

Open only what you need

Research & records

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1869

Profile-stated birthplace: Coffee County, Tennessee, USA

Coffee County, Tennessee, USA

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.

One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Glasgow-683

No sufficiently specific citation match found.

Precision: Country-centre fallback for profile locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.10 claims
2Unknown
1Derivative
1Tree Only

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

No claims in this category have been formally assessed.

Research questionsOpen problems, missing bridges and the next records to inspect.0 open

No formal open question is recorded for this person.

Sources and provenanceStructured citations and source-quality classifications.4 sources

Source or provenance: quality describes the record layer, not every conclusion drawn from it.

  1. unknown Source: #S1654364993
  2. derivative Source: S1654364993 Repository: #R1650254164 Tennessee, Deaths and Burials Index, 1874-1955 Ancestry.com Publication: Ancestry.com Operations, Inc.
  3. unknown Repository: R1650254164 Ancestry.com
  4. tree_only WikiTree profile export for Glasgow-683
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier

WikiTree biography, citations and relationship snapshot

Glasgow-683 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2017-07-18.

Profile location claims

EventDateLocationStatus
birthCoffee County, Tennessee, USAWikiTree profile field
deathBedford, TennesseeWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ParentsJohn GlasgowGlasgow-6901819-00-00 · 1899-07-15
SiblingsMaria GlasgowGlasgow-6891848-00-00 · Tennessee, United States · 0000-00-00
SiblingsLucy JerniganGlasgow-6881852-00-00 · Tennessee, USA · 0000-00-00
SiblingsMay GlasgowGlasgow-6871856-00-00 · Tennessee · 0000-00-00
SiblingsMargaret GlasgowGlasgow-6861859-00-00 · Tennessee · 0000-00-00
SiblingsAmanda GlasgowGlasgow-6851860-00-00 · Tennessee · 0000-00-00
SiblingsEliza GlasgowGlasgow-6841860-00-00 · Tennessee · 0000-00-00
SiblingsSallie Morgan GlasgowGlasgow-6811864-06-06 · Manchester, Coffee, Tennessee, USA · 1930-01-01
SiblingsRachel GlasgowGlasgow-6821869-10-00 · Coffee County, Tennessee, USA · 0000-00-00

Record-bearing passages

  • Biography John Glasgow. Wesley Glasgow. Source: #S1654364993 Found multiple versions of name. Using John Glasgow.
  • Born 11 Dec 1869. Coffee County, Tennessee, USA. 11 Dec 1869. Tennessee Source: #S1654364993 Found multiple copies of birth date. Using 11 Dec 1869
  • Died 20 Aug 1931. Bedford, Tennessee. Source: #S1654364993
  • Residence Marital Status: Married. Normandy, Tennessee. Source: #S1654364993
  • Buried 21 Aug 1931. United States. Source: #S1654364993 Sources

    • Source: S1654364993 Repository: #R1650254164 Tennessee, Deaths and Burials Index, 1874-1955 Ancestry.com Publication: Ancestry.com Operations, Inc.
    • Repository: R1650254164 Ancestry.com

Profile source citations

  1. Source: #S1654364993
  2. Source: S1654364993 Repository: #R1650254164 Tennessee, Deaths and Burials Index, 1874-1955 Ancestry.com Publication: Ancestry.com Operations, Inc.
  3. Repository: R1650254164 Ancestry.com
Full captured biography text
Biography
John Glasgow. 
Wesley Glasgow. Source: #S1654364993 
Found multiple versions of name. Using John Glasgow. 

Born 
11 Dec 1869. 
Coffee County, Tennessee, USA. 
11 Dec 1869. 
Tennessee Source: #S1654364993 
Found multiple copies of birth date. Using 11 Dec 1869 

Died 
20 Aug 1931. 
Bedford, Tennessee. Source: #S1654364993 

Residence Marital Status: Married. 
Normandy, Tennessee. Source: #S1654364993 

Buried 
21 Aug 1931. 
United States. Source: #S1654364993 
Sources
* Source: S1654364993 Repository: #R1650254164 Tennessee, Deaths and Burials Index, 1874-1955 Ancestry.com Publication: Ancestry.com Operations, Inc. 
* Repository: R1650254164 Ancestry.com
Raw WikiTree biography markup
== Biography ==

'''John''' Glasgow. 
Wesley Glasgow. <ref>Source: [[#S1654364993]]   </ref>
''Found multiple versions of name. Using John  Glasgow.'' 

'''Born''' 
11 Dec 1869. 
Coffee County, Tennessee, USA. 
11 Dec 1869. 
Tennessee<ref>Source: [[#S1654364993]]   </ref>
''Found multiple copies of birth date. Using 11 Dec 1869'' 

'''Died''' 
20 Aug 1931. 
Bedford, Tennessee. <ref>Source: [[#S1654364993]]   </ref>

'''Residence''' Marital Status: Married. 
Normandy, Tennessee. <ref>Source: [[#S1654364993]]   </ref>

'''Buried''' 
21 Aug 1931. 
United States. <ref>Source: [[#S1654364993]]   </ref>

== Sources ==

<references />

* Source: <span id='S1654364993'>S1654364993</span> Repository: [[#R1650254164]] Tennessee, Deaths and Burials Index, 1874-1955 Ancestry.com Publication: Ancestry.com Operations, Inc.    
* Repository: <span id='R1650254164'>R1650254164</span> Ancestry.com