Cornelia Francina Magdalena Elizabeth Oosthuizen (infant)

2 February 1852 – 1854 · Oosthuizen line

Descends from the root couple, 2 generations up

Names

Given: Cornelia Francina Magdalena Elizabeth Meyer
Surname: Oosthuizen

The formal baptismal name and the name a person was actually called are both kept, and neither is derived from the other. Spelling drift between records is evidence, not noise.

Immediate family

Father: Jacobus Daniel Johannes Oosthuizen
Mother: Sophia Johanna Mocke
Brothers and sisters: 1844Nicolaas Frederik Hitge

1846Aletta Catharina Maria Helena Hitge

1848Adriana Cecilia Oosthuizen

1850Sophia Johanna Oosthuizen

1852Fredrica Johanna Oosthuizen

1854~Ockert Almero Oosthuizen

1856Frederik Simon Oosthuizen

1858Jacobus Johannes Oosthuizen

1860Margaretha Appollonia Oosthuizen

1863John Peter Oosthuizen

1867Pieter Marincowitz Oosthuysen

A life in the record

2 February 1852 born Born
1854 died Died

What we don't know

No dated record ties this person to a specific piece of ground.

A sourced gap beats an unsourced fill. These are the open questions on this person, stated rather than papered over.

Research notes

[FS K8RV-S4V][TREE] Born 2 Feb 1852, baptised 10 Feb 1852 at Prince Albert (DRC register, indexed on FamilySearch, ark:/61903/1:1:6KQ6-MPNG); died about 1854, at about two. Daughter of J.D.J. Oosthuizen (PER-000004) x Sophia Johanna MockeM (PER-000136). THE 'MEYER' SURNAME RESOLVED, 30 Jul 2026: it is the TAIL OF HER GIVEN NAMES, not her surname - she was baptised with the full name of CORNELIA FRANCINA MAGDALENA ELIZABETH MEYER (b. 13 Nov 1814 Graaff-Reinet, d. 1855, tree), wife of JAN HENDRIK STRYDOM - who was the FULL BROTHER of David Jan (Jacobus) Strydom, the 1841 RONDABEL grantee (PER-000042). A godmother from the neighbour family, honoured with a full-name vernoeming - the same habit as Peeter Marincowitz Oosthuysen (PER-000403), Sophia Johanna Mocke OosthuizenM (PER-000421) and Almero Jacobus Hitge OosthuizenL (PER-000016). The FamilySearch indexer read 'Meyer' as a surname; the register image is unavailable online [TO VERIFY against the register when found]. The namesake died in 1855, a year after the child. DATE FLAG: her 2 Feb 1852 birth collides with her sister Fredrica Johanna's 27 Jun 1852 (PER-000381) - four and a half months apart, impossible for one mother; one of the two dates is wrong, the register-indexed 2 Feb 1852 being the stronger [TO VERIFY].

[5 Aug 2026] MERGED PER-000380 into this row. One profile,, on two rows: the model's single live tree id collision. PER-000470's own notes did the adjudication on 30 Jul 2026 - 'Meyer' is the tail of her given names, a full-name vernoeming after the godmother Cornelia Francina Magdalena Elizabeth MeyerM (tree), misread as a surname by the FamilySearch indexer. PER-000470 survives because it carries the baptism, the death and the correct surname; PER-000380's GL5W-F4T is the family-tree _FID that LEAD-0019 already records as disagreeing with this row's hand-entered K8RV-S4V, so the pair is id-proven twice over. DISAGREEMENTS, kept rather than resolved - the FamilySearch id settles these in one click: display_name: kept 'Cornelia Francina Magdalena Elizabeth OosthuizenH (infant)', PER-000380 said 'Cornilia Francina Magdalena Elizabeth Meyer'; given: kept 'Cornelia Francina Magdalena Elizabeth MeyerM', PER-000380 said 'Cornilia Francina Magdalena Elizabeth'; surname: kept 'Oosthuizen', PER-000380 said 'Meyer'; line: kept 'Oosthuizen', PER-000380 said 'Meyer'; familysearch_id: kept 'K8RV-S4V', PER-000380 said 'GL5W-F4T'. Retired ids kept for the trail: FamilySearch GL5W-F4T - a merged FamilySearch id still resolves, so it remains a usable door.

These are working notes, not finished prose: they carry the reasoning, the corrections and the things still marked to verify. They are kept here so the page itself can read as what is known.

Open questions

Nine people carry a different FamilySearch id here and in the tree priority 2 · LEAD-0036
For nine people the model records one FamilySearch id and the family-tree's _FID records another. Which is the live profile, and are the two ids two profiles for one person that want merging on FamilySearch itself?

What would settle it Loading each id and seeing whether it redirects.
Seven pairs of siblings born too close together for both to be real priority 2 · LEAD-0108
Seven mothers in this model have two children whose exact birth dates fall less than ten months apart, twins excluded. For each: are the two rows one child, is one date wrong, or is one parentage link wrong?

What would settle it One register entry per pair.
Two more merges kept the survivor's FamilySearch id. Was it the right one? priority 2 · LEAD-0115
Three merges in this model retired a FamilySearch id the survivor does not carry. One has now been adjudicated and the RETIRED id was correct. Are the other two the same way round? PER-000470 (kept K8RV-S4V, retired GL5W-F4T) and PER-000211 (kept GB6B-ZCM, retired L1GX-62B).

What would settle it Reading each pair and saying which profile is the person. Where FamilySearch itself holds both, it needs merging there too.
Seven people carry a hand-entered FamilySearch id that the family-tree disagrees with priority 3 · LEAD-0019
Backfilling familysearch_id from the family-tree's _FID tag agreed with the hand-entered value on 103 of 110 people and disagreed on 7. Which id is current for each - or do both resolve to the same person after a merge?

What would settle it A redirect proves a merge and the survivor id is the one to keep. Two live, distinct profiles means one of them is the wrong person, and the vitals decide which.

Elders

FamilySearch profile K8RV-S4V