Individual research record
James Glasgow
c. 1813 (estimated) – ?
Glasgow-4024 · 1 mapped association
At a glance
Identity & family
Tree links organise the family; documentary status still varies.
- Birth
- c. 1813 (estimated) · Cookstown (estimated)
- Death
- Not recorded · Place not recorded
- Parents
- Not recorded
- Spouses
- Not recorded
- Children
- Not recorded
- Gender
- Male
- WikiTree
- Glasgow-4024
- Research clusters
- Descendants of James Glasgow (c.1700)
- 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
Known-position checks: 0 support · 0 conflict. Ordinals retain unnamed children and recognise reused names.
Estimate and relationship notes
- Estimated as age 18 at the earliest known adult record (1831).
- Estimated from the earliest mapped residence record (1831).
Relationship comparison
Potential parents or duplicates
Compare scored leads with the subject details above—not proof.
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
James GlasgowGlasgow-1623
- same first and last name (+18)
- same birth year (+30)
No indexed conflict
Full comparison detail
- same first and last name (+18)
- same birth year (+30)
Conflicts: No indexed conflict
Same-name candidate
James Robert GlasgowGlasgow-212
- same first and last name (+18)
- birth years within 10 (+10)
- shared recorded place (+20)
No indexed conflict
Full comparison detail
- same first and last name (+18)
- birth years within 10 (+10)
- shared recorded place (+20)
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
Conclusion
Created unconnected on 20 August 2026 from the St Luran's burial transcript. The record identifies James Glasgow, residence Cookstown, buried 13 March 1831, aged 40. A PRONI pre-1858 wills and administrations index entry independently names James Glasgow of Cookstown in 1831. The same name, residence, and year strongly identify the two entries as the same man, but neither supplies family relationships.
Life and record timelineChronological mapped occurrences and their underlying sources.1 record
Probate residence: Cookstown, County Tyrone
The residence supports the local cluster but no profile match is secure.
Source and mapping detail
PRONI Names, Pre-1858 Wills and Admons: James Glasgow, Cookstown, County Tyrone, 1831
Explicitly attached to this mapped association.
Precision: Settlement centrepoint
Evidence assessmentWhat is supported, uncertain or disputed in the current case model.1 claim
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.
Case-file assessments
Identity links
| Profile | Distinction |
|---|---|
| Glasgow-1024 | Proposed father of adults born in the 1740s–1750s; not age 40 in 1831 |
| Glasgow-3444 | Reports 1776–1866 |
| Glasgow-3986 | Larne/St Cedma's man, reportedly born about 1773 |
| Glasgow-2988 | Earlier Kildress candidate |
Reciprocal exclusion notes were saved on Glasgow-3444, Glasgow-3986, and Glasgow-2988. Glasgow-1024 was not edited because its live update remains on hold pending Glasgow-3305 research.
WikiTree also recorded rejected matches with Glasgow-2439, Glasgow-3095, and Glasgow-1483 during creation.
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.
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced
WikiTree profile information
Glasgow-4024
James Glasgow
Updated unknown
Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20