CH / STUDIOReading Journal: TabMap field guide

A practical reading method

Track a Family Across Generations Without Merging Names

Start one row per person with birth era or generation, first confirmed name, and the page where that identity becomes clear. Add each later title or family role to the same row only when the text supplies a relationship or time clue that connects it. Leave uncertain identities as separate rows and write the evidence that would be needed to join them.

Use this when a book repeats a name across generations or switches between a person’s name, title, and relationship role. A family tree alone can still hide uncertainty. Page anchors show when an identity is confirmed and prevent two people from being merged too early.

Use case

When this method helps

Use this when a book repeats a name across generations or switches between a person’s name, title, and relationship role.

A family tree alone can still hide uncertainty. Page anchors show when an identity is confirmed and prevent two people from being merged too early.

Method

Build the note

1. Start one row per person with birth era or generation, first confirmed name, and the page where that identity becomes clear.

2. Add each later title or family role to the same row only when the text supplies a relationship or time clue that connects it.

3. Leave uncertain identities as separate rows and write the evidence that would be needed to join them.

Example

See the boundary in practice

If a chapter calls someone only ‘the elder Thomas,’ keep that as an unresolved row until a date, parent, or child links him to the Thomas already in your notes.

Quality check

Before you trust the note

Every merged identity should have a page-level reason. If the reason is only that two people share a name, split the row again.