Glasgow Surname Project

Individual research record

Gillian Ann (Flaherty) Glasgow

1972-07-24 – c. 2023

Flaherty-1127 · 1 mapped association

Birthplace unknownDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
1Close relations
2Evidence items
0Candidate leads
Birth
1972-07-24 · Place not recorded
Death
c. 2023 · Place not recorded
Parents
Not recorded
Spouses
John Glasgow
Children
Not recorded
Gender
Female
WikiTree
Flaherty-1127
Research clusters
Scotland 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.

No sufficiently similar same-name person is currently indexed.

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

Kin-inferred from spouse John Glasgow’s birthplace: Glasgow, Scotland, United Kingdom

Glasgow

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links. This map placement is an estimate from kin and is not a directly recorded location for this person.

Kin-inferred One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Flaherty-1127

No sufficiently specific citation match found.

Precision: Kin-inferred relationship locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.2 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 Personal recollection of events witnessed by M Glasgow as remembered 30 Dec 2020.
  2. tree_only WikiTree profile export for Flaherty-1127
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

Flaherty-1127 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-11-12.

Record-bearing passages

  • Biography Gillian was born in 1972.
  • - Lived in Santa Monica CA - Lived in Mount Pleasant, South Carolina - Occupation: Administration
  • 323 Harbor Pointe Dr UNIT 16, Mt Pleasant, SC 29464 5220 Copley Cir, Summerville, SC 29485 1937 Oak Tree Ln, Mt Pleasant, SC 29464 925 W Chestnut Ave UNIT 23, Lompoc, CA 93436 1743 9Th St UNIT 6, Santa Monica, CA 90404 Sources

Profile source citations

  1. Personal recollection of events witnessed by M Glasgow as remembered 30 Dec 2020.
Full captured biography text
Biography
Gillian was born in 1972.
 
Personal recollection of events witnessed by M Glasgow as remembered 30 Dec 2020.

- Lived in Santa Monica CA
- Lived in Mount Pleasant, South Carolina
- Occupation: Administration

Addresses

 323 Harbor Pointe Dr UNIT 16, Mt Pleasant, SC 29464
 5220 Copley Cir, Summerville, SC 29485
 1937 Oak Tree Ln, Mt Pleasant, SC 29464
 925 W Chestnut Ave UNIT 23, Lompoc, CA 93436
 1743 9Th St UNIT 6, Santa Monica, CA 90404
Sources
Raw WikiTree biography markup
== Biography ==
Gillian was born in 1972.
<ref>
Personal recollection of events witnessed by [[Glasgow-933|M Glasgow]] as remembered 30 Dec 2020.
</ref>

- Lived in Santa Monica CA
- Lived in Mount Pleasant, South Carolina
- Occupation: 	Administration

Addresses
	

    323 Harbor Pointe Dr UNIT 16, Mt Pleasant, SC 29464
    5220 Copley Cir, Summerville, SC 29485
    1937 Oak Tree Ln, Mt Pleasant, SC 29464
    925 W Chestnut Ave UNIT 23, Lompoc, CA 93436
    1743 9Th St UNIT 6, Santa Monica, CA 90404

== Sources ==
<references />