Lane Relationships & 1891 Register

Browse father, mother, and spouse links decoded from Lane Genealogies (1891)—numbered families, carry-forward children, and the PDF page each edge came from.

Context: how the printed register is organized. Evidence: each link’s book code and PDF page in Postgres (or the in-memory graph fallback).

Hub Full tree page Book plates Direct line Path between two

Quick jumps · numbered families

Multi-volume research

Internet Archive · Vol. I

Decoded families from Lane Genealogies Vol. I (1891), Vol. II (1897), and Vol. III (1902). Pick any numbered family below, or use the graph controls.

Loading research totals…

Relationship graph

Links from the 1891 register — No. N family blocks, (N) carry-forward children, and pedigree chains — stored with the book page each link came from.

Show

Book part

Family No.

Generations

Father Mother Spouse Book-coded links only

Time Build Mute

1500 Press Play to watch the family graph build through time

Loading relationship graph…

Relationships explorer

Every parent / spouse link in lane_relationship. Book-coded rows show the register code (family No., child numeral, carry-forward) and the PDF page.

How register codes work

No. N — a numbered family block in the book (head, wife, children).
(N) before a child’s roman numeral — that child heads family No. N later in the register.
Pedigree — abbreviated father → grandfather chain printed after the head’s name.
Unmatched OCR crumbs stay on a review list. High-signal register heads/wives/children can be synthesized with book provenance via --enrich.

Deep link examples: ?familyNo=3&section=boston, ?q=Lane&relation=father&bookOnly=1, ?id=10, ?timebuild=1 (auto-start year clock).