Skip to page content
Glasgow archive/Robert Glasgow
Catalogue · 08 Sep 2026
Person dossier · record-john-of-portrush-robert-glasgow-1666

Robert Glasgow

before 1645 – after 1666

Tools
At a glance

Robert Glasgow appears in the family catalogue.

Birth
before 1645Place not recorded
Death
after 1666Place not recorded

The family

Explore →

No parents named in the supplied model.

Robert GlasgowSelected person

No children attached here.

Relationship labels belong to each link. Partners are not assumed to be parents of every child.

A life in the records

Open the full chronology →

Personal events

  1. Birth

  2. Death

Records mentioning them

  1. Master of the John of Portrush transporting coal for the earl of Argyll

    Mentioned person; role not specified

    Scotland — exact locality unproved

    The catalogue proves the shipmaster and transport receipt but gives no age, residence, birthplace, route or relatives; the original receipt remains uninspected.

The research behind the story.

1 record associations →

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
1666

Master of the John of Portrush transporting coal for the earl of Argyll

Scotland — exact locality unproved

The catalogue proves the shipmaster and transport receipt but gives no age, residence, birthplace, route or relatives; the original receipt remains uninspected.

Documented catalogue occurrenceoriginal
Source and mapping detail

Argyll Estates Archives, Campbell family, dukes of Argyll papers, “Various accounts and receipts,” 1666–1678, GB 3452 ARG-04-03-67-78, former reference PFV 67, catalogue p. 149

Candidate matched on record type, year; inspect before treating it as the underlying record.

Precision: Country-level contextual point

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.1 claim
1Original

Documented or strongly supported

Robert Glasgow was recorded in Scotland — exact locality unproved (1666).

proved1 linked evidence item

Master of the John of Portrush transporting coal for the earl of Argyll

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.1 source
For working on the evidence

Research tools and original material

Original imported identity & family snapshot

Preserved imported material. It may include superseded assertions; the current display assessment is shown at the top of this dossier.

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
0Close relations
1Evidence items
2Candidate leads
Birth
before 1645 · Place not recorded
Death
after 1666 · Place not recorded
Parents
Not recorded
Spouses
Not recorded
Children
Not recorded
Gender
Male
WikiTree
No confirmed WikiTree destination
Research clusters
Unplaced early Glasgow records
Mapped descendants
Not calculated

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.

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.

Same-name candidate

Robert GlasgowGlasgow-3357

Automated fit43/100
Similar Person
Dates1646–?PlacesCurrie, Midlothian, ScotlandParent 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

Same-name candidate

Robert GlasgowGlasgow-1512

Automated fit28/100
Similar Person
Dates1652–?PlacesAyr, Ayrshire, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 7 (+10)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 7 (+10)

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.

Duplicate-safe creation

WikiTree profile workbench

No confirmed WikiTree profile is linked.

Live duplicate audit: checked 2026-09-08 across 198 exact-name or surname-variant search results.

Possible existing profiles

These are leads, not matches. Check locations, dates, relatives and source text.

Suggested WikiTree creation field

Birth
before 1645 · mark as uncertainTaken from the catalogue's birth field.

Paste-ready WikiTree biography

Review the candidate profiles above before creating a new one. Use the suggested vital field above so the periodic matcher can find the finished profile.

Already exists or just created?

No submission is needed. The periodic live WikiTree audit searches the name, suggested vital date and place; a matching profile will appear as a candidate after the next catalogue refresh.

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-09-08

Machine-readable dossier

Imported facts and reviewed decisions

Original exports stay unchanged. The public display uses explicitly approved decisions where available.

Read the original JSON · Reviewed decision register

Structured data downloadsOriginal structured dossier

Your research notebook.

Select 2 people to compare their evidence.