Glasgow Surname Project

Individual research record

John Glasgow

1764-03-06 – 1833-08-29

Glasgow-3726 · 1 mapped association

Cumberland, PennsylvaniaMadison, Kentucky, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
12Candidate leads
Birth
1764-03-06 · Cumberland, Pennsylvania
Death
1833-08-29 · Madison, Kentucky, United States
Parents
Not recorded
Spouses
Roseanne Patterson
Children
Nancy (Glasgow) Goggin
Gender
Male
WikiTree
Glasgow-3726
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
1

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 positionNancy (Glasgow) Goggin (1800)
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

Possible fathers5 leads

Automated fit29/100
Weak Lead
Dates1730–?Generation34 years age gapRecorded placesKirknewton and East Calder, Midlothian, Scotland · Kirknewton — West LothianIndependent clue breadth · 4Age · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 34-year parent-child age gap (+18)
  • known spouse Christian (Meek) Glasgow had a plausible maternal age (34) at the subject's birth (+7)
  • candidate's birth is 70 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate already has another child named John Glasgow (Glasgow-3480) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • plausible 34-year parent-child age gap (+18)
  • candidate's birth is 70 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • known spouse Christian (Meek) Glasgow had a plausible maternal age (34) at the subject's birth (+7)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate already has another child named John Glasgow (Glasgow-3480) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Automated fit27/100
Weak Lead
Dates1740–?Generation24 years age gapRecorded placesIrvine, Ayrshire, Scotland · Irvine — AyrshireIndependent clue breadth · 6Age · Contemporaneous Household Conflict · Same-Sex Generational Naming · Spouse · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowMargaret (Mill) GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • known spouse Margaret (Mill) Glasgow had a plausible maternal age (24) at the subject's birth (+7)
  • candidate's birth is 60 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded Andrew Glasgow in West Calder, Midlothian, Scotland within 0 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 60 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • subject's birth fits between children attributed to the same parental couple (1762–1770) (+6; other parent Margaret (Mill) Glasgow)
  • known spouse Margaret (Mill) Glasgow had a plausible maternal age (24) at the subject's birth (+7)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded Andrew Glasgow in West Calder, Midlothian, Scotland within 0 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)

Show 3 lower-scoring possible fathers
Automated fit26/100
Weak Lead
Dates1738–?Generation26 years age gapRecorded placesIrvine, Ayrshire, Scotland · Irvine — AyrshireIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 26-year parent-child age gap (+18)
  • candidate's birth is 62 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 26-year parent-child age gap (+18)
  • candidate's birth is 62 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit26/100
Weak Lead
Dates1735–1785Generation29 years age gapRecorded placesCounty Londonderry, Ireland · County Londonderry — exact locality unprovedIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 29-year parent-child age gap (+18)
  • candidate's birth is 65 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 29-year parent-child age gap (+18)
  • candidate's birth is 65 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit26/100
Weak Lead
Dates1730–?Generation34 years age gapRecorded placesAyrshire, Scotland · Ayrshire — exact locality unprovedIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 34-year parent-child age gap (+18)
  • candidate's birth is 70 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 34-year parent-child age gap (+18)
  • candidate's birth is 70 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name John (+4; weak direct parent-child name recurrence, 278 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Possible mothers5 leads

Automated fit23/100
Chronology-Only Fallback
Dates1740–1811Generation24 years age gapRecorded placesIreland · Nelson, Kentucky, United States · Ireland — exact locality unprovedIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 60 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: kentucky (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 60 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: kentucky (+1; not a locality match)

Deductions and cautions: No indexed conflict; documentary proof still required

Automated fit22/100
Chronology-Only Fallback
Dates1745–?Generation19 years age gapRecorded placesWest Calder, Midlothian, Scotland · Midlothian — exact locality unprovedIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 19-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 19-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible mothers
Automated fit22/100
Chronology-Only Fallback
Dates1745–?Generation19 years age gapRecorded placesMidlothian, Scotland · Midlothian — exact locality unprovedIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 19-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 19-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit22/100
Chronology-Only Fallback
Dates1744–?Generation20 years age gapRecorded placesKilwinning — AyrshireIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit22/100
Chronology-Only Fallback
Dates1744–?Generation20 years age gapRecorded placesCounty Dublin, Ireland · County Dublin — exact locality unproved · Lanesborough / LanesboroIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

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.

Same-name candidate

John GlasgowGlasgow-1657

Automated fit48/100
Similar Person
Dates1766–1836PlacesCounty Antrim, Ireland → Cross, Ballymoney, County Antrim, Ireland, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 2 (+25)
  • death years within 3 (+5)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 2 (+25)
  • death years within 3 (+5)

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-2964

Automated fit43/100
Similar Person
Dates1766–?PlacesScotland → Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 2 (+25)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 2 (+25)

Conflicts: No indexed conflict

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. 1764

Profile-stated birthplace: Cumberland, Pennsylvania

Cumberland, Pennsylvania

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-3726

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.3 claims
1Tree Only
1Unknown

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.2 sources

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

  1. unknown John Glasgow died intestate. His lengthy probate is listed in Madison County, KY administrator bond filed 7 Oct 1833.
  2. tree_only WikiTree profile export for Glasgow-3726
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-3726 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-11-12.

Profile location claims

EventDateLocationStatus
birthCumberland, PennsylvaniaWikiTree profile field
deathMadison, Kentucky, United StatesWikiTree profile field
marriage1790-09-02Madison, Kentucky, United StatesWikiTree relationship field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenNancy GogginGlasgow-37251800-00-00 · Madison, Kentucky, United States · 1828-00-00
SpousesRoseannePatterson-312421769-12-09 · 1842-12-20 · Madison, Kentucky, United States · 1790-09-02

Record-bearing passages

  • Biography John was born in 1764. He passed away in 1833. Sources

    • John Glasgow died intestate. His lengthy probate is listed in Madison County, KY administrator bond filed 7 Oct 1833.
  • US Federal Census 1810, 1820, and 1830

Profile source citations

  1. John Glasgow died intestate. His lengthy probate is listed in Madison County, KY administrator bond filed 7 Oct 1833.
Full captured biography text
Biography
John was born in 1764. He passed away in 1833.
Sources
* John Glasgow died intestate. His lengthy probate is listed in Madison County, KY administrator bond filed 7 Oct 1833.

US Federal Census 1810, 1820, and 1830
Raw WikiTree biography markup
== Biography ==

John was born in 1764.  He passed away in 1833.
== Sources ==
<references />
* John Glasgow died intestate.  His lengthy probate is listed in Madison County, KY administrator bond filed 7 Oct 1833.

US Federal Census 1810, 1820, and 1830