Glasgow Surname Project

Individual research record

John Glasgow

c. 1756 – 1826-12-11

Glasgow-2291 · 1 mapped association

Birthplace unknownNewberry, South Carolina, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
0Close relations
1Evidence items
18Candidate leads
Birth
c. 1756 · Place not recorded
Death
1826-12-11 · Newberry, South Carolina, United States
Parents
Not recorded
Spouses
Not recorded
Children
Not recorded
Gender
Male
WikiTree
Glasgow-2291
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.

Same-name candidate

John GlasgowGlasgow-1146

Automated fit71/100
Possible Duplicate
Dates1756–1826PlacesCounty Antrim, Ireland → Gilder's Creek, Newberry Co., S CarolinaParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • same death year (+15)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • same death year (+15)
  • overlapping locality (+8)

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-1549

Automated fit53/100
Similar Person
Dates1758–1825PlacesGlasgow, Lanarkshire, Scotland → Sinking Valley, Blair, Pennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 2 (+25)
  • death years within 1 (+10)

No indexed conflict

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

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-3298

Automated fit43/100
Similar Person
Dates1755–?PlacesGlasgow, Lanarkshire, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 1 (+25)

No indexed conflict

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

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-3581

Automated fit43/100
Similar Person
Dates1755–?PlacesKirknewton, Linlithgowshire, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 1 (+25)

No indexed conflict

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

Conflicts: No indexed conflict

Show 4 lower-scoring duplicate lead(s)

Same-name candidate

John GlasgowGlasgow-3480

Automated fit36/100
Similar Person
Dates1751–?PlacesKirknewton And East Calder, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 5 (+18)

No indexed conflict

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

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-159

Automated fit36/100
Similar Person
Dates1761–?PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 5 (+18)

No indexed conflict

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

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-2846

Automated fit28/100
Similar Person
Dates1747–?PlacesWest Calder, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 9 (+10)

No indexed conflict

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

Conflicts: No indexed conflict

Same-name candidate

John GlasgowGlasgow-2980

Automated fit28/100
Similar Person
Dates1750–?PlacesMid Calder, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 6 (+10)

No indexed conflict

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

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

Latest case researchThe current conclusion from the durable research case file.Updated

Current conclusion

Glasgow-2291

This profile is a duplicate of John Glasgow (Glasgow-1146). Both represent the John Glasgow born about 1756 who died in Newberry on 11 December 1826. Glasgow-2291 cites the Gilders Creek memorial for that exact identity and has no parents, spouse or children attached. It should be merged into the better-developed Glasgow-1146 profile.

The merge does not reveal another son. Absolom remains John's only plausible attached son, and that relationship is still awaiting direct evidence.

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

Profile-stated death place: Newberry, South Carolina, United States

Newberry, South Carolina, United States

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

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.1 claim
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.1 source

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

  1. tree_only WikiTree profile export for Glasgow-2291
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-2291 was captured 2026-08-19T11:32:40+00:00; WikiTree profile revision unknown.

Profile location claims

EventDateLocationStatus
deathNewberry, South Carolina, United StatesWikiTree profile field

Profile source citations

No structured source citation was recoverable from the profile biography.

Full captured biography text
No public biography text was returned.
Raw WikiTree biography markup
No public biography markup was returned.