Glasgow Surname Project

Individual research record

Ruth Glasgow

1782-10-20 – ?

Glasgow-334 · 1 mapped association

Currituck, North Carolina, United States→Harpers River, Davidson, Tennessee, United States
View on mapOpen WikiTreeCompareReport a correction

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
1Close relations
7Evidence items
7Candidate leads
Birth
1782-10-20 · Currituck, North Carolina, United States
Death
Not recorded · Harpers River, Davidson, Tennessee, United States
Parents
William Glasgowunmarked
Spouses
Not recorded
Children
Not recorded
Gender
Female
WikiTree
Glasgow-334
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 fit36/100
Similar Person
Dates1791–?PlacesSouth Carolina, United States → Walker Creek, Lafayette, Arkansas, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 9 (+10)
  • overlapping locality (+8)

No indexed conflict

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

Conflicts: No indexed conflict

Open side-by-side comparison
Automated fit28/100
Similar Person
Dates1802–1863PlacesNewberry, South Carolina, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 20 (+2)
  • overlapping locality (+8)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 20 (+2)
  • overlapping locality (+8)

Conflicts: No indexed conflict

Open side-by-side comparison
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. 1782

Profile-stated birthplace: Currituck, North Carolina, USA

Currituck, North Carolina, 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-334

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.9 claims
3Tree Only
2Derivative
2Unknown

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

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

  1. unknown Glasgow-334 was created by Kaylene Silvester through the import of cora glasgow 4 gen.ged on Jan 9, 2015. This comment and citation can be deleted after the biography has been edited and primary sources are included.
  2. derivative Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW
  3. derivative Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER
  4. tree_only Source: S116 Author: Ancestry.com Title: Public Member Trees Publication: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006; Repository: #R3
  5. unknown Repository: R3 Name: www.ancestry.com Address: E-Mail Address: Phone Number:
  6. tree_only Source: S27 Author: Ancestry.com Title: Public Member Trees Publication: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;; Repository: #R3
  7. tree_only WikiTree profile export for Glasgow-334
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-334 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-03-28.

Profile location claims

EventDateLocationStatus
birth—Currituck, North Carolina, USAWikiTree profile field
death—Harpers River, Davidson, Tennessee, USAWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ParentsWilliam GlasgowGlasgow-3571757-11-28 · Currituck, Province of North Carolina · 1805-08-14 · Currituck, Currituck Parish, North Carolina, United States
SiblingsCaleb GlasgowGlasgow-2201781-04-09 · Currituck, North Carolina, USA · 1818-00-00
SiblingsLove GlasgowGlasgow-3021785-01-30 · Currituck, North Carolina, USA · 1839-00-00
SiblingsIsaac Wesley GlasgowGlascow-141786-12-03 · Currituck, North Carolina, United States · 1848-06-09 · Dresden, Weakley, Tennessee, United States
SiblingsSamuel GlasgowGlasgow-3391790-03-04 · Currituck, North Carolina, USA · 0000-00-00 · Halifax, North Carolina, USA
SiblingsJohn Cooper GlasgowGlasgow-2801794-12-03 · Currituck, North Carolina, USA · 1835-00-00 · Stewart, Tennessee, USA
SiblingsIssac GlasgowGlasgow-23631800-00-00 · United States · 1870-00-00
SiblingsSophia GlasgowGlasgow-3411801-09-26 · Currituck, North Carolina, USA · 1832-00-00 · Harpers River, Davidson, Tennessee, USA

Record-bearing passages

  • Biography This biography was auto-generated by a GEDCOM import. Glasgow-334 was created by Kaylene Silvester through the import of cora glasgow 4 gen.ged on Jan 9, 2015. This comment and citation can be deleted after the biography has been edited and primary sources are included. It's a rough draft and needs to be edited. Name : Name: Ruth /Glasgow/ Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER Birth : Birth: :: Date: 20 OCT 1782 :: Place: Currituck, North Carolina, USA Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER Death : Death: :: Place: Harpers River, Davidson, Tennessee, USA Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW : Death: :: Place: Harper's River, Davidson, Tn Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER Found multiple copies of DEAT DATE. Using Array Sources

    • Source: S116 Author: Ancestry.com Title: Public Member Trees Publication: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006; Repository: #R3
    • Repository: R3 Name: www.ancestry.com Address: E-Mail Address: Phone Number:
    • Source: S27 Author: Ancestry.com Title: Public Member Trees Publication: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;; Repository: #R3

Profile source citations

  1. Glasgow-334 was created by Kaylene Silvester through the import of cora glasgow 4 gen.ged on Jan 9, 2015. This comment and citation can be deleted after the biography has been edited and primary sources are included.
  2. Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW
  3. Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER
  4. Source: S116 Author: Ancestry.com Title: Public Member Trees Publication: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006; Repository: #R3
  5. Repository: R3 Name: www.ancestry.com Address: E-Mail Address: Phone Number:
  6. Source: S27 Author: Ancestry.com Title: Public Member Trees Publication: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;; Repository: #R3
Full captured biography text
Biography
This biography was auto-generated by a GEDCOM import. Glasgow-334 was created by Kaylene Silvester through the import of cora glasgow 4 gen.ged on Jan 9, 2015. This comment and citation can be deleted after the biography has been edited and primary sources are included. It's a rough draft and needs to be edited.
Name
: Name: Ruth /Glasgow/ Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER 
Birth
: Birth: 
:: Date: 20 OCT 1782
:: Place: Currituck, North Carolina, USA Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER 
Death
: Death: 
:: Place: Harpers River, Davidson, Tennessee, USA Source: #S27 Page: Database online. Data: Text: Record for William GLASGOW 
: Death: 
:: Place: Harper's River, Davidson, Tn Source: #S116 Page: Database online. Data: Text: Record for SARAH COOPER 
Found multiple copies of DEAT DATE. Using Array
Sources
* Source: S116 Author: Ancestry.com Title: Public Member Trees Publication: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006; Repository: #R3 
* Repository: R3 Name: www.ancestry.com Address: E-Mail Address: Phone Number: 
* Source: S27 Author: Ancestry.com Title: Public Member Trees Publication: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;; Repository: #R3
Raw WikiTree biography markup
== Biography ==

''This biography was auto-generated by a GEDCOM import.<ref>Glasgow-334 was created by [[Silvester-158 | Kaylene Silvester]] through the import of cora glasgow 4 gen.ged on Jan  9, 2015. ''This comment and citation can be deleted after the biography has been edited and primary sources are included.''</ref> It's a rough draft and needs to be edited.''

=== Name ===
: Name:  Ruth /Glasgow/<ref>Source: [[#S27]]  Page:  Database online. Data:   Text:  Record for William GLASGOW</ref><ref>Source: [[#S116]]  Page:  Database online. Data:   Text:  Record for SARAH COOPER</ref>

=== Birth ===
: Birth:  
:: Date:  20 OCT 1782
:: Place:  Currituck, North Carolina, USA<ref>Source: [[#S27]]  Page:  Database online. Data:   Text:  Record for William GLASGOW</ref><ref>Source: [[#S116]]  Page:  Database online. Data:   Text:  Record for SARAH COOPER</ref>

=== Death ===
: Death:  
:: Place:  Harpers River, Davidson, Tennessee, USA<ref>Source: [[#S27]]  Page:  Database online. Data:   Text:  Record for William GLASGOW</ref>
: Death:  
:: Place:  Harper's River, Davidson, Tn<ref>Source: [[#S116]]  Page:  Database online. Data:   Text:  Record for SARAH COOPER</ref>
Found multiple copies of DEAT DATE. Using Array

== Sources ==

<references />

* Source: <span id='S116'>S116</span> Author:  Ancestry.com Title:  Public Member Trees Publication:  Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006; Repository: [[#R3]]  
* Repository: <span id='R3'>R3</span> Name:  www.ancestry.com Address:   E-Mail Address:   Phone Number:  
* Source: <span id='S27'>S27</span> Author:  Ancestry.com Title:  Public Member Trees Publication:  Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date: 2006;; Repository: [[#R3]]