Glasgow Surname Project

Individual research record

Douglas Pollock Glasgow

1936-03-19 – 1977-04-21

Glasgow-3699 · 1 mapped association

Edinburgh, Midlothian, Scotland, United KingdomEdinburgh, Midlothian, Scotland, United Kingdom

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
6Candidate leads
Birth
1936-03-19 · Edinburgh, Midlothian, Scotland, United Kingdom
Death
1977-04-21 · Edinburgh, Midlothian, Scotland, United Kingdom
Parents
John Glasgowunmarked
Spouses
Not recorded
Children
Kevin Glasgow
Gender
Male
WikiTree
Glasgow-3699
Research clusters
Scotland 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 positionKevin Glasgow (1954)
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.

Estimate and relationship notes
  • 1 parent reference point outside the current export.

Relationship comparison

Potential parents or duplicates

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

Higher-signal leadReview carefullyWeak lead

Possible mothers5 leads

Automated fit13/100
Weak Lead
Dates1898–1976Generation38 years age gapRecorded placesNorth Carolina, United States · Fort Collins, Larimer, Colorado, United StatesIndependent clue breadth · 3Age · Rare Branch-Name Recurrence · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • uncommon given names recur in both otherwise distinct descendant branches: Douglas +16 (3 public profiles; subject branch: Douglas Pollock Glasgow; candidate branch: Douglas Scott Glasgow) (+16 total)

candidate is recorded only outside the subject's birth country (−25)

Show complete scoring
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 56 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • uncommon given names recur in both otherwise distinct descendant branches: Douglas +16 (3 public profiles; subject branch: Douglas Pollock Glasgow; candidate branch: Douglas Scott Glasgow) (+16 total)

Deductions and cautions: candidate is recorded only outside the subject's birth country (−25)

Automated fit28/100
Chronology-Only Fallback
Dates1912–2002Generation24 years age gapRecorded placesLeith South, Midlothian, Scotland, United Kingdom · Edinburgh, Scotland, United Kingdom · South LeithIndependent clue breadth · 3Age · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: edinburgh (+6)
  • candidate's birth is 42 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 42 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • candidate has only broad or undated birth-locality overlap: edinburgh (+6)
  • same research cluster (+0; grouping is not kinship evidence)

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

Show 3 lower-scoring possible mothers
Automated fit24/100
Chronology-Only Fallback
Dates1893–?Generation43 years age gapRecorded placesEdinburgh, Midlothian, Scotland, United Kingdom · EdinburghIndependent clue breadth · 3Age · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 43-year parent-child age gap (+10)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • candidate's birth is 61 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • possible 43-year parent-child age gap (+10)
  • candidate's birth is 61 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit24/100
Chronology-Only Fallback
Dates1892–?Generationat most 44 years age gapRecorded placesEdinburgh, Midlothian, Scotland · EdinburghIndependent clue breadth · 3Age · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • candidate's birth is 62 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • bounded birth date gives a parent-child age gap of at most 44 years (+10; true age remains uncertain)

No indexed conflict; documentary proof still required

Show complete scoring
  • bounded birth date gives a parent-child age gap of at most 44 years (+10; true age remains uncertain)
  • candidate's birth is 62 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit24/100
Chronology-Only Fallback
Dates1889–?Generation47 years age gapRecorded placesEdinburghIndependent clue breadth · 3Age · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 47-year parent-child age gap (+10)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • candidate's birth is 65 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • possible 47-year parent-child age gap (+10)
  • candidate's birth is 65 years before the subject's earliest dated child (1954), a compatible grandparent-generation interval (+4)
  • same specific indexed locality despite wider place-label differences: edinburgh (+10)
  • same research cluster (+0; grouping is not kinship evidence)

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

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 fit0/100
Similar Person
Dates1950–2006PlacesScottsbluff, Scotts Bluff, Nebraska, United States → Kearney, Buffalo, Nebraska, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 14 (+2)

death years differ by 29 (−18); unassessed father attachments differ (−5)

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

Conflicts: death years differ by 29 (−18); 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. 1936

Profile-stated birthplace: Edinburgh, Midlothian, Scotland

Edinburgh

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

No sufficiently specific citation match found.

Precision: Settlement centrepoint

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 https://www.ancestry.com/genealogy/records/douglas-pollock-glasgow-24-2fc0sxg
  2. tree_only WikiTree profile export for Glasgow-3699
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-3699 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-09-29.

Profile location claims

EventDateLocationStatus
birthEdinburgh, Midlothian, ScotlandWikiTree profile field
deathEdinburgh, Midlothian, ScotlandWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ParentsJohn GlasgowGlasgow-36981899-00-00 · Tarbrax, Inverarity, Forfarshire, Scotland, United Kingdom · 1975-00-00
ParentsBridgetO'Bryne-171910-00-00 · 0000-00-00
ChildrenKevin GlasgowGlasgow-37001954-00-00 · Edinburgh, Scotland, United Kingdom · 2010-00-00
SiblingsJohnGlasgow-36971928-00-00 · Forth, Lanarkshire, Scotland, United Kingdom · 0000-00-00

Record-bearing passages

Profile source citations

  1. https://www.ancestry.com/genealogy/records/douglas-pollock-glasgow-24-2fc0sxg source link 1
Full captured biography text
Biography
Douglas was born in 1936. He was the son of John Glasgow and Bridget O'Bryne. He passed away in 1977.
Sources
* https://www.ancestry.com/genealogy/records/douglas-pollock-glasgow-24-2fc0sxg
Raw WikiTree biography markup
== Biography ==

Douglas was born in 1936. He was the son of [[Glasgow-3698|John Glasgow]] and [[O'Bryne-17|Bridget O'Bryne]]. He passed away in 1977.
== Sources ==
<references />
* https://www.ancestry.com/genealogy/records/douglas-pollock-glasgow-24-2fc0sxg