Skip to content
UsecaseBoard
← All use cases
dev.toFamily History

Promote genealogy leads only after finding the original record

At a glance

A genealogist extends a GEDCOM tree through assistant research and record verification. This workflow is listed under Family History, Research, Evidence Management.

Agents / tools
AI assistant, GEDCOM, Playwright, Topola

SourceBuilding a tool for these workflows? See weekly rates.

What they did

1) Prepare a GEDCOM family tree, an assistant with file, browser and regional archive access. Give each site separate browsing instructions. For sites requiring an account, sign in yourself through a persistent browser profile before the run. 2) Choose a person whose parents are unknown. Let the assistant search genealogy sites for candidate relatives, recording those leads at QUAY 2, the author's provisional evidence rating. 3) Locate the corresponding civil or parish record, transcribe it, and check the proposed relationship against that record. Upgrade supported information to QUAY 3; discard unsupported leads. 4) Add the confirmed people, relationship and source to GEDCOM and commit the change. Repeat on the next unresolved branch. 5) Inspect the updated tree in Topola and review suggested cross-tree matches conservatively before accepting them.

How it went

The author reports a tree exceeding 1,200 people, with one branch spanning 13 generations.

Worth knowing

QUAY ratings are the author's interpretation. A smart match can attach an unrelated family and corrupt an entire branch.

Save ideas in this browser. Upvotes count across the board.

Prompt excerpt

No prompt excerpt was provided by the source.

Sponsored

CodeBuddy

Tencent Cloud AI coding assistant for IDE and CLI.

Try CodeBuddy ↗
Explore all →