Glasgow Surname Project

Individual research record

James Thomas Glasgow

1788-05-16 – 1849-10-28

Glasgow-803 · 1 mapped association

Newberry County, South Carolina, United StatesAbbeville County, South Carolina, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
3Close relations
3Evidence items
7Candidate leads
Birth
1788-05-16 · Newberry County, South Carolina, United States
Death
1849-10-28 · Abbeville County, South Carolina, United States
Parents
James Glasgowunmarked
Spouses
Margaret (Morrow) Glasgow
Children
Jane Elizabeth (Glasgow) Burdette
Gender
Male
WikiTree
Glasgow-803
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 positionJane Elizabeth (Glasgow) Burdette (1818)
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 fit16/100
Weak Lead
Dates1777–1838Generationnominally 11 years; approximate dates permit about 15–21 years age gapRecorded placesNewberry, South Carolina, United StatesIndependent clue breadth · 4Age · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate has only broad or undated birth-locality overlap: newberry, south (+6)
  • the nominal 11-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–21 years) (+4)
  • candidate's birth is 41 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 11-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–21 years) (+4)
  • candidate's birth is 41 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate has only broad or undated birth-locality overlap: newberry, south (+6)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate has another child, Robert Glasgow, born 12 years from the subject in the same specific birth locality (+2; possible sibling-household clue)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

Automated fit0/100
Weak Lead
Dates1773–1858Generation15 years age gapRecorded placesAntrim, County Antrim, Ireland · Racavan, County Antrim, Ireland · County Antrim — exact locality unprovedIndependent clue breadth · 3Age · Child Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 15-year parent-child age gap (+10)
  • candidate's birth is 45 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

candidate is recorded only outside the subject's birth country (−25); candidate already has another child named James McClure Glasgow (Glasgow-1780) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • possible 15-year parent-child age gap (+10)
  • candidate's birth is 45 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

Deductions and cautions: candidate is recorded only outside the subject's birth country (−25); candidate already has another child named James McClure Glasgow (Glasgow-1780) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show 3 lower-scoring possible mothers
Automated fit0/100
Weak Lead
Dates1750–?Generation38 years age gapRecorded placesCounty Antrim — exact locality unprovedIndependent clue breadth · 3Age · Child Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 68 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

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 68 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

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

Automated fit0/100
Weak Lead
Dates1747–1832Generation41 years age gapRecorded placesIrvine, Ayrshire, Scotland · Ontario, Canada · Irvine — AyrshireIndependent clue breadth · 3Age · Child Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 41-year parent-child age gap (+10)
  • candidate's birth is 71 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

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

Show complete scoring
  • possible 41-year parent-child age gap (+10)
  • candidate's birth is 71 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • candidate's given name recurs among another recorded child (+1; Jane occurs in 71 public profiles)

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

Automated fit28/100
Chronology-Only Fallback
Dates1765–?Generation23 years age gapRecorded placesLocation not supplied — profile holding pointIndependent clue breadth · 3Age · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowWilliam GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 23-year parent-child age gap (+18)
  • candidate's birth is 53 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

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

Show complete scoring
  • plausible 23-year parent-child age gap (+18)
  • candidate's birth is 53 years before the subject's earliest dated child (1818), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1783–1802) (+6; other parent William Glasgow)

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

James GlasgowGlasgow-2439

Automated fit46/100
Similar Person
Dates1789–1831PlacesSouth Carolina, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 1 (+25)
  • overlapping locality (+8)

unassessed father attachments differ (−5)

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

Conflicts: unassessed father attachments differ (−5)

Same-name candidate

James GlasgowGlasgow-62

Automated fit43/100
Similar Person
Dates1789–1860PlacesVirginia, United States → Pittsylvania, VirginiaParent 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

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

Profile-stated birthplace: Newberry County, South Carolina, USA

Newberry County, South 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-803

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.4 claims
1Derivative
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.3 sources

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

  1. unknown US Federal Census; 1820 U S Census; Census Place: Abbeville, Abbeville, South Carolina; Page: 15; NARA Roll: M33_118; Image: 27
  2. derivative "United States, Census, 1820", FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XHLQ-T78 : Sat Mar 09 21:50:10 UTC 2024), Entry for James Glasgow, 1820.
  3. tree_only WikiTree profile export for Glasgow-803
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-803 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-12-08.

Profile location claims

EventDateLocationStatus
birthNewberry County, South Carolina, USAWikiTree profile field
deathAbbeville County, South Carolina, USAWikiTree profile field
marriage1810-02-27Abbeville County, South Carolina, USAWikiTree relationship field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ParentsJames GlasgowGlasgow-8041735-11-11 · Ayr, Ayrshire, Scotland · 1788-05-19 · Newberry, Newberry, South Carolina, USA
ParentsMaryNorris-66041748-04-05 · Coatbridge, Lanarkshire, Scotland · 1842-07-23 · Abbeville County, South Carolina, USA
ChildrenJane Elizabeth BurdetteGlasgow-8021818-06-11 · Abbeville County, South Carolina, USA · 1892-03-31 · Calhoun County, Alabama, USA
SpousesMargaret GlasgowMorrow-36821793-02-17 · Abbeville County, South Carolina, USA · 1842-07-23 · 1810-02-27

Record-bearing passages

  • Biography James was born in 1788. He passed away in 1849. Sources

    • US Federal Census; 1820 U S Census; Census Place: Abbeville, Abbeville, South Carolina; Page: 15; NARA Roll: M33_118; Image: 27
    • "United States, Census, 1820", FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XHLQ-T78 : Sat Mar 09 21:50:10 UTC 2024), Entry for James Glasgow, 1820.

Profile source citations

  1. US Federal Census; 1820 U S Census; Census Place: Abbeville, Abbeville, South Carolina; Page: 15; NARA Roll: M33_118; Image: 27
  2. "United States, Census, 1820", FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XHLQ-T78 : Sat Mar 09 21:50:10 UTC 2024), Entry for James Glasgow, 1820. source link 1
Full captured biography text
Biography
James was born in 1788. He passed away in 1849. 
Sources
* US Federal Census; 1820 U S Census; Census Place: Abbeville, Abbeville, South Carolina; Page: 15; NARA Roll: M33_118; Image: 27
* "United States, Census, 1820", FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XHLQ-T78 : Sat Mar 09 21:50:10 UTC 2024), Entry for James Glasgow, 1820.
Raw WikiTree biography markup
== Biography ==
James was born in 1788. He passed away in 1849. 
== Sources ==
<references />
* US Federal Census; 1820 U S Census; Census Place: Abbeville, Abbeville, South Carolina; Page: 15; NARA Roll: M33_118; Image: 27
* "United States, Census, 1820", FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XHLQ-T78 : Sat Mar 09 21:50:10 UTC 2024), Entry for James Glasgow, 1820.