Skip to page content
Glasgow archive/David Methven
Catalogue · 08 Sep 2026
Person dossier · Methven-283

David Methven

c. 1833 (estimated) – Not recorded

Tools
The research account

Current conclusion

FamilySearch PZCK-J36 matches the WikiTree profile through the 1808 Cults identification, the 1838 Creich marriage, and the children. The 31 March 1833 baptism record names David Methven as father of William Methven and Isabell Chalmers as mother; it does not name David's parents.

Methven-283 · Read the complete current assessment

Birth
c. 1833 (estimated)Place not recorded
Death
Not recordedPlace not recorded

The family

Explore →

No parents named in the supplied model.

David MethvenSelected person

No children attached here.

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

What would move the research forward

Evidence and next steps

Recommended action

Hold Andrew Methven (9S8R-Q1H) and Margaret Clark (9S8R-Q1P) until a record directly supports David's parentage.

Read all current research questions

A life in the records

Open the full chronology →

Personal events

  1. Birth

Records mentioning them

  1. Baptism of son names David as father

    Mentioned person; role not specified

    Baptism of son names David as father

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.

Latest case researchThe current conclusion from the durable research case file.Updated

Current conclusion

Methven-283

FamilySearch PZCK-J36 matches the WikiTree profile through the 1808 Cults identification, the 1838 Creich marriage, and the children. The 31 March 1833 baptism record names David Methven as father of William Methven and Isabell Chalmers as mother; it does not name David's parents.

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
1833

Baptism of son names David as father

Location not specified

No additional note.

Documentedunknown
Source and mapping detail

Scotland, Births and Baptisms, 1564-1950

No sufficiently specific citation match found.

Precision: Not specified

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

Documented or strongly supported

David Methven was recorded in an unspecified place (1833).

proved1 linked evidence item

Baptism of son names David as father

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

Methven-283

Hold Andrew Methven (9S8R-Q1H) and Margaret Clark (9S8R-Q1P) until a record directly supports David's parentage.

Sources and provenanceStructured citations and source-quality classifications.1 source

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

  1. derivative Scotland, Births and Baptisms, 1564-1950
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
0Candidate leads
Birth
c. 1833 (estimated) · Place not recorded
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Not recorded
Children
Not recorded
Gender
Male
WikiTree
Methven-283
Research clusters
None assigned
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

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.

Estimate and relationship notes
  • Estimated from a birth or baptism record (1833).
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.

No sufficiently similar same-name person is currently indexed.

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.

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.