# Book Isle project reference archives: preserve links between books, notes and conclusions

Language: en
Canonical: [Book Isle project reference archives: preserve links between books, notes and conclusions](<https://allluckly.cn/en/guides/nasbook-project-reference-archive/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-project-reference-archive/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-project-reference-archive/>)
Published: 2026-10-27T00:00:00+08:00
Modified: 2026-10-27T13:09:53+08:00
Author: Bison

At project close, organise reference scope, note purposes and file sources, export readable records and verify a route back to the original text.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-project-reference-archive/>), translated on 2026-10-27. Original publication dates, attribution, code and version notes are retained.

References may remain useful after a project ends. Archive three owned sources by preserving editions, the notes behind particular conclusions and the locations of originals. A shared tag alone does not capture those relationships.

## Define the archive scope

State project scope and select three representative sources with edition, format, location and purpose. Distinguish evidence used in conclusions from casual browsing. A project tag is organisational, not bibliographic proof. Retain originals and existing access controls, excluding credentials/private connection details from ordinary archive notes.

## Separate evidence, open questions and personal ideas

Classify notes as supporting evidence, unresolved questions or unused ideas through supported notes or an external list. Do not treat every highlight as verified fact or expect automatic project synthesis. Retain chapter/quotation references for each important conclusion and identify multiple sources separately before reorganising shelf display.

## Use a restrained project tag for retrieval

Apply one stable project tag, testing a single book’s filtering before extending it. Preserve useful topic tags and avoid unexplained naming variants. Tags aid retrieval without moving files or packaging notes automatically. Verify the same edition from both the full shelf and project filter without unintended status changes.

## Connect conclusions to specific passages

List conclusions with supporting source, edition, chapter and note identifier. Record brief reasons for abandoned conclusions. Keep the full project report in its actual work location rather than assuming built-in project management or a citation database. Explicit links reduce the need to reconstruct reasoning from every highlight later.

## Export readable notes and verify them externally

Export needed notes/highlights to a managed project folder and reopen them externally. Verify one source passage and personal comment. Save a companion list for project relationships omitted by the format. Readable exports are not guaranteed full-state restores or substitutes for original PDFs/EPUBs. Record date and scope to identify final changes.

## Archive original sources and work outputs separately

Record real original locations and editions separately from reports/outputs, linking both through the project ID. Covers and excerpt images are not complete originals. Verify existing local or authorised remote source availability. Reading-data sync remains distinct from book-file preservation; this archive check does not require server migration or sync reconfiguration.

## Rehearse retrieval using only the archive list

Leave the current view and trace one conclusion using only the archive list to book, edition, note and passage. Find the same note in the external export too. Add missing fields where guessing is necessary. Verify the three samples before expanding and identify unchecked materials rather than claiming universal completion.

## Finish through verified relationships, not deletion

Project closure does not require deleting references. Before cleaning any output, verify uniqueness and scope. Investigate filters, project names and folders before bulk reimport. The archive should identify editions, evidence locations and original sources; verified retrieval, not a tidy tag or deletion count, establishes usefulness.

## Related tutorials and sources

[Export Book Isle reading data: keep notes, highlights and statistics](<https://allluckly.cn/en/guides/nasbook-reading-data-export/>), [Book Isle categories: plan reading with tags, status and ratings](<https://allluckly.cn/en/guides/nasbook-tags-status-rating/>).

Checked on October 27, 2026 using [Apple public version information](<https://itunes.apple.com/lookup?id=6766198898&country=cn>): Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Capability scope follows the [official App Store listing](<https://apps.apple.com/cn/app/id6766198898>) and corresponding controls. These are reproducible workflows and checks, without a claim of step-by-step physical-device, private-server or target-software testing. Dimensions, data and copy are exercises; follow your installed version.