Focused reading methods

Book Isle character notes: manually track relationships and chapter evidence

Build a small manual record of characters and changing relationships, checking aliases, viewpoint and read scope with source anchors rather than automatic entity mapping.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

A long novel can make returning characters and changing relationships hard to remember. Keep a small manual record with chapter evidence and read-scope boundaries. Book Isle assists navigation and notes; you interpret identities and relationships without assuming automatic alias detection or a generated network.

Limit the record to your read scope

Record edition and furthest-read chapter, then choose a few confusing characters. Avoid unread plot research and distinguish stated facts from guesses. Note first appearance, form of address and viewpoint. Use the current translation as baseline instead of trying to build a complete encyclopedia.

Create one stable character entry

Use a stable personal label with confirmed aliases, identity and chapter references. Do not merge similar names without evidence. Preserve and test one defining passage through available notes/bookmarks. An external document is enough; do not repurpose book metadata to invent character fields.

Attach evidence to each relationship

Write the relationship and confirming chapter, retaining uncertainty and viewpoint. A character claim is not automatically objective fact. Attach a tested anchor and short locator phrase, reading context rather than inferring a relationship merely from two people sharing a scene. Leave unresolved links unconfirmed.

Check alias matches in context

Search distinctive names in the correct book and read context for each match, respecting read scope. Check wording and text availability for missing results; use chapters for scans. Matching strings locate passages but do not establish identical entities or automatic alias merging.

Date relationship changes instead of overwriting

Add a new chapter-dated state for revelations or alliances and explain what evidence changes the earlier view. Preserve the information available at the earlier stage rather than projecting later truth backwards. Mark rejected guesses briefly. Split an overlong record by character or story phase while retaining anchors.

Update only characters affected by new reading

After a reading unit, update only meaningful relationship changes. Retain last-confirmed chapters for absent characters. Bookmarks locate and notes explain, with manual chapter/phrase mapping if needed. Keep edition identity and create an alias map for a new translation rather than globally overwriting old names.

Preserve scope when exporting or sharing

Reopen exported notes and verify names, chapters and interpretation. For any later sharing, label read scope and check spoilers; this workflow itself sends nothing. Preserve the book and notes separately and distinguish personal summaries from quotations. Verify the actual output rather than selecting an older spoiler-heavy version.

Acceptance and corrections

Finish with identifiable characters, chapter-supported relationships, separated guesses/changes and working references. Split mistakenly merged entries and verify their evidence individually. No generated graph is needed, and unresolved source information should remain uncertain instead of being filled with spoilers.

Book Isle excerpts: keep highlights and notes, then make a quote card; Book Isle full-text search: find a book and position from a phrase.

Checked on October 27, 2026: Apple public version information lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the official App Store description and controls depend on the installed version. This article describes a personal reading or library-checking workflow without claiming step-by-step physical-device or private-server testing. Book files and reading records are managed separately; development recognition, generation or automatic analysis is not treated as released functionality.