Dated assessments, source transcriptions and earlier working notes remain available in full. Where those disagree, use the current conclusion above and inspect its reasoning.
No separately maintained research assessment in this snapshot. The available records are preserved below.
Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1830
Profile-stated birthplace: Ballymoney, County Londonderry, Ireland
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.
Candidate comparisons and scoring
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.
Dates1828–1853PlacesKilrea, County Londonderry, Ireland, United Kingdom → Brooklyn, New York, United StatesParent comparisonNo shared parent is indexed
Why it may fit
same first and last name (+18)
birth years within 2 (+25)
overlapping locality (+8)
unassessed father attachments differ (−5)
Full comparison detail
same first and last name (+18)
birth years within 2 (+25)
overlapping locality (+8)
Conflicts: unassessed father attachments differ (−5)
Dates1828–1907PlacesBallynasollus, Kildress, County Tyrone, Ireland, United Kingdom → Ballynasollus, Kildress, County Tyrone, Ireland, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
same first and last name (+18)
birth years within 2 (+25)
uncertain father attachments differ (no deduction)
Full comparison detail
same first and last name (+18)
birth years within 2 (+25)
Conflicts: uncertain father attachments differ (no deduction)
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.
1807-00-00 · County Antrim, Ireland · 1885-06-24 · Lisnagaver, County Antrim, Ireland
Profile categories
Estimated_Birth_DateGlasgow Name StudyGlasgow_Name_Study
Record-bearing passages
Biography James Glasgow is estimated to have been born about 1830. His birth date and place have not been established.
James was a son of John Glasgow, the married farmer who died at Lisnagaver on 24 June 1885. The civil death registration identifies James Glasgow of Lisnagaver as the deceased man's son, present at the death and the informant. General Register Office of Ireland, civil death register (https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf), John Glasgow, Lisnagaver, 24 June 1885.
The record proves the father-son relationship but supplies no age, wife or other identifying details for James. Sources
General Register Office of Ireland, civil death register (https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf), John Glasgow, Lisnagaver, 24 June 1885. source link 1
https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf source link 1
Full captured biography text
Biography
James Glasgow is estimated to have been born about 1830. His birth date and place have not been established.
James was a son of John Glasgow, the married farmer who died at Lisnagaver on 24 June 1885. The civil death registration identifies James Glasgow of Lisnagaver as the deceased man's son, present at the death and the informant. General Register Office of Ireland, civil death register (https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf), John Glasgow, Lisnagaver, 24 June 1885.
The record proves the father-son relationship but supplies no age, wife or other identifying details for James.
Sources
* https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf
Raw WikiTree biography markup
{{Estimated Date}}
[[Category:Glasgow Name Study]]
== Biography ==
'''James Glasgow''' is estimated to have been born about 1830. His birth date and place have not been established.
James was a son of [[Glasgow-3474|John Glasgow]], the married farmer who died at Lisnagaver on 24 June 1885. The civil death registration identifies James Glasgow of Lisnagaver as the deceased man's son, present at the death and the informant.<ref name="FatherDeath">[https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf General Register Office of Ireland, civil death register], John Glasgow, Lisnagaver, 24 June 1885.</ref>
The record proves the father-son relationship but supplies no age, wife or other identifying details for James.
== Sources ==
<references />
* https://www.irishgenealogy.ie/files/civil/deaths_returns/deaths_1885/06280/4799372.pdf
Imported facts and reviewed decisions
Original exports stay unchanged. The public display uses explicitly approved decisions where available.