Individual research record
John Glasgow
c. 1648-07-09 – ?
Glasgow-3093 · 1 mapped association
At a glance
Identity & family
Tree links organise the family; documentary status still varies.
- Birth
- c. 1648-07-09 · Mid Calder, Midlothian, Scotland
- Death
- Not recorded · Place not recorded
- Parents
- James Glasgowconfident
- Spouses
- Not recorded
- Children
- Not recorded
- Gender
- Male
- WikiTree
- Glasgow-3093
- 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
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.
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
John GlasgowGlasgow-3012
- 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
John GlasgowGlasgow-1498
- 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)
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
Current conclusion
John Glasgow (Glasgow-1084) is ruled out as the father named in the cited baptism. The 9 July 1648 Mid Calder entry identifies the child's father as Jamis Glasgow, and the live tree now attaches James Glasgow (Glasgow-3332). Whether Glasgow-3332 is the correct identity of that Jamis remains a separate question; a man named John cannot replace the recorded father.
Life and record timelineChronological mapped occurrences and their underlying sources.1 record
Profile-stated birthplace: Mid Calder, Midlothian, Scotland
One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.
Source and mapping detail
WikiTree profile export for Glasgow-3093
No sufficiently specific citation match found.
Precision: Settlement/parish centrepoint
Case-file source findingsSource extracts and analysis regenerated from findings.md.1 section(s)
Source findings
| Source | Finding | Assessment |
|---|---|---|
| FamilySearch X1BL-JXR | Indexes Johne Glasgow at Mid Calder in 1648 and names father Jamis Glasgow. | Direct evidence for the father's given name; rules out John Glasgow-1084. |
Evidence assessmentWhat is supported, uncertain or disputed in the current case model.2 claims
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.
Case-file priorities and cautions
Recommended action
Keep Glasgow-1084 out of potential-father results. Investigate which James Glasgow the baptism identifies.
Sources and provenanceStructured citations and source-quality classifications.2 sources
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-3093
John Glasgow
Updated 2025-04-21
Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20
WikiTree biography, citations and relationship snapshot
Glasgow-3093 was captured 2026-08-10T14:12:13+00:00; WikiTree profile revision 2025-04-21.
Profile location claims
| Event | Date | Location | Status |
|---|---|---|---|
| birth | — | Mid Calder, Midlothian, Scotland | WikiTree profile field |
Immediate relationship snapshot
| Relationship | Person | WikiTree ID | Dates and places returned |
|---|---|---|---|
| Parents | James Glasgow | Glasgow-3332 | 1634-00-00 · Biggar, Lanarkshire, Scotland. · 0000-00-00 |
Record-bearing passages
Biography Johne was born about 1648. He is the son of a 'Jamis Glasgow' in Mid Calder, Midlothian, Scotland Sources
Profile source citations
- https://www.familysearch.org/ark:/61903/1:1:X1BL-JXR source link 1
Full captured biography text
Biography Johne was born about 1648. He is the son of a 'Jamis Glasgow' in Mid Calder, Midlothian, Scotland Sources * https://www.familysearch.org/ark:/61903/1:1:X1BL-JXR
Raw WikiTree biography markup
== Biography == Johne was born about 1648. He is the son of a 'Jamis Glasgow' in Mid Calder, Midlothian, Scotland == Sources == <references /> * https://www.familysearch.org/ark:/61903/1:1:X1BL-JXR