# ManYue large-catalogue checks: verify beyond the first batch

Language: en
Canonical: [ManYue large-catalogue checks: verify beyond the first batch](<https://allluckly.cn/en/guides/manyue-catalog-page-completeness/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-catalog-page-completeness/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-catalog-page-completeness/>)
Published: 2026-10-27T00:00:00+08:00
Modified: 2026-10-27T13:09:52+08:00
Author: Bison

Choose known early, middle and late catalogue items to inspect account scope, multi-page loading and local filtering without inventing a complete-count claim.

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

A first screen of covers establishes only partial catalogue visibility. Large services may require more pages, nested navigation or indexing. Use known reference items to separate account scope, incomplete loading and filtering, while keeping the limits of sampling explicit.

## Build a same-account reference

Using the same reader account, choose three to five clearly identified items across the catalogue. Record title, library and edition rather than vague page positions. Do not compare a reader with an administrator total. Note indexing/maintenance and avoid a changing baseline; a small private reference list is sufficient.

## Clear filtering and fix the connection

Select the intended connection and scope, clear old queries and inspect refresh/error state. A multi-service home view is not necessarily the full server catalogue. Wait for visible loading to settle and keep connection and account fixed while locating reference items.

## Locate known items across the range

Locate and open each reference item. Missing late items are an observation, not proof of an undocumented fixed limit. Check loading, nested organisation and connection identity. Reconfirm missing entries in the same-account server view to exclude recent moves or visibility changes.

## Separate filtering from catalogue retrieval

Determine whether the entry filters loaded fields or uses a source-specific remote query. Verify a known simple title and clear it again. Local filtering cannot discover items absent from the loaded snapshot, and server syntax may not apply. Label search context before changing metadata or diagnosing matching.

## Check changes during multi-page loading

Wait for server maintenance to stabilise before one normal refresh. Record repeated items, missing references or explicit errors without deleting archives. Provide sample identities and timing to the maintainer, including concurrent catalogue changes. No guessed page sizes or manual internal-file edits are needed.

## Compare a smaller supported scope

Use a smaller supported feed or library scope only if the service actually offers one and permissions allow it. Preserve the original connection and label the comparison. Do not guess paths or reorganise all server files merely to test. Small-scope success narrows the issue without proving large-catalogue completeness.

## Inspect actual reading as another layer

After locating references, inspect body pages and sample a middle/end too. Catalogue presence, file readability and offline availability are separate results. Record each layer explicitly and leave untested checks blank. A page failure calls for its own permission/file investigation rather than erasing the catalogue observation.

## Acceptance and sampling limits

Finish with understood account scope, located references, explainable refresh/filter results and recorded page samples. Neither the list bottom nor a few passes proves the entire library intact. Keep date, connection and missing-reference notes for later checks without publishing private catalogues or rebuilding everything.

## Related guides and sources

[ManYue multiple servers: distinguish matching titles and personal library scope](<https://allluckly.cn/en/guides/manyue-server-library-scope/>); [ManYue after a server rescan: verify changed chapters and old bookmarks](<https://allluckly.cn/en/guides/manyue-server-rescan-identity/>).

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and [Apple public version lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn>). Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.