ManYue personal library audit: use five sample books to find missing files or records

In a long-used library, uncertainty often concerns which books are local, which covers outlive their source, and which records are backed up. Audit five representative books and turn gaps into concrete follow-up tasks. Sampling identifies useful maintenance work without proving the entire collection is faultless or requiring a full-library cleanup.

Choose representatives by source and state

Choose a local import, a downloaded server book, a NAS item, an online server entry and an important finished work. Substitute actual common material for categories you do not use. Include different ages and file types instead of five books from one fresh import batch. Record each source, edition and purpose, and state the sampling scope explicitly.

Create an audit inventory without credentials

For each sample, leave fields for readability, current position, offline state, original-file location and data-backup date. Mark unchecked fields honestly rather than filling them from memory. Record connection names and types without credentials, plus audit date and device. A simple personal note is sufficient; no dedicated audit dashboard is assumed.

Check real pages before metadata

Inspect beginning, middle and end for every sample. Verify current account access for online entries and paths for NAS books. Separate missing entries, catalogue failures, page failures and isolated image problems. Keep working samples intact instead of responding to the first issue with a full cache wipe. Record observations before planning targeted repairs.

Test offline samples disconnected

For books intended for offline use, disconnect and inspect several positions through local entries. Mark online-only items not applicable rather than failed. Record the extent of partial downloads before repairing them under suitable network and permission conditions. Check original backups separately. Use clear states such as complete, partial, unavailable or not applicable.

Check reading anchors and bookmarks

Open resume for active books and a meaningful bookmark for the finished sample. Compare actual scenes, not only numbers. Replaced files or editions can change page mapping. Preserve the old description before relocating a shifted reference. Record edition and source so missing records can be distinguished from valid records pointing into different content.

Check where sync and backups actually go

If you sync across devices, verify one sample through the normal handoff sequence. Locate the latest independent data export and the original comic files separately. A successful sync is not a newly created backup. Turn gaps into specific tasks, such as preserving one original, exporting current records or rehearsing one restore, rather than writing an unactionable reminder.

Prioritise repairs by practical impact

Repair issues affecting current reading or imminent travel first, then archival gaps and duplicates. Recheck the same sample after each targeted repair and date the result. Storage cleanup requires its own original-file and deletion-scope checks. Keep successful observations too, so the next audit can distinguish new issues from outstanding ones without rebuilding everything.

Questions and completion criteria

Do five passing books prove the entire library intact? No; expand checks for important material as needed. How often should you audit? Let library changes, moves, new devices and large imports guide the timing. Finish with a dated, scoped device inventory, evidence for checked items and a concrete next step for every gap. Update the same inventory next time.

Related guides and sources

ManYue recovery rehearsal: check backup coverage before retiring a device; ManYue NAS folder moves: verify paths, library entries and local copies.

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.