Private-library quality checks

Book Isle ebook provenance register: connect originals, editions and access routes

Create a small provenance and edition inventory distinguishing originals, temporary links, catalogue entries and reading records, then verify later exports and replacements.

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

Growing libraries can blur the difference between originals, access links and reading identities. Register a few authorised books with source, edition and storage details. The inventory aids traceability without replacing backups or validating an unknown source’s trustworthiness.

Create a stable inventory identity

Choose a few important authorised books and record actual bibliographic details and format with a stable personal inventory ID. Leave unknown editions unverified. Use real metadata fields plus external notes without inventing a provenance panel or treating your ID as a server identifier.

Separate acquisition from current storage

Record acquisition provenance separately from present storage, retaining necessary evidence privately. Moving a folder does not change acquisition history. Keep sensitive orders/accounts out of shared inventories, respect actual rights and mark unknowns. This is not a resource-site recommendation or automatic permission to redistribute.

Identify the recoverable original

Open the recorded original and verify contents and representative text, excluding placeholders or web previews. Identify independent recoverability beyond the current shelf. Label converted and working derivatives separately because their content/layout can differ. This prevents cleanup from removing the sole complete copy.

Register remote access without confusing it with a file

Record service, connection and item identity rather than temporary token-bearing links. Note the legitimate route for finding it again and local-copy status separately. Distinguish shared-library rights from sync storage. Preserve old identities when maintenance changes entries instead of overwriting by title alone.

Map the app entry to the original

Compare publication details, chapter and a phrase between app entry and original. Record metadata/content differences by layer. Do not merge revisions or assume alternate formats contain identical text. Test retrieval from both shelf and original storage so the inventory demonstrates practical usefulness.

Record reading-data preservation separately

Record actual note/progress preservation and export dates separately from book originals. Distinguish live records, readable exports, sync and recovery backups. Use truthful completion/restore-test status; merely opening settings is not a backup. Verify book availability on another device independently.

Preserve mappings through replacement and moves

Date new paths, revisions and differences without erasing provenance needed by old citations. Recheck publication/text and retain an old edition where required. A path move differs from content replacement. Test one source reference after updating instead of stopping at a renamed list entry.

Acceptance and maintenance limits

Finish when samples connect shelf, originals, edition and provenance, with separate record preservation and honest unknowns. Avoid storing unnecessary private links. An inventory is not a backup. Update meaningful changes instead of fabricating completeness; a small accurate register already prevents many identity and cleanup mistakes.

Book Isle filenames and display titles: keep a route back to originals; Export Book Isle reading data: keep notes, highlights and statistics.

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.