ManYue LANraragi tag lookup: distinguish app filtering from server search syntax

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

LANraragi’s web search has its own syntax, which should not be assumed to run unchanged in ManYue. Use one known tag to compare server metadata, delivered fields and app scope. The goal is a reliable archive lookup rather than an invented advanced-query feature.

Establish a known server tag

Choose a known archive in your authorised server and record its title, author tag and a distinctive subject tag. Confirm these are actual metadata, including any namespace. Do not change metadata in bulk or copy keys into the comparison note. Server search success is a starting point, not proof of identical app behaviour.

Inspect the item delivered to the app

Refresh the intended connection and compare visible title, authors and tags. A shared cover does not establish updated metadata. For missing fields, check server persistence, account scope and refresh. Do not rename the item to force a match or treat external inventory data as automatically searchable in the app.

Test one distinctive term first

Search one distinctive visible title/tag term within the selected connection. Compare a known-absent term and clear the query to restore the list. Check scope, spelling and refresh state before interpreting an empty result as deletion. Catalogue loading and filtering are separate observations.

Do not transplant compound web syntax

LANraragi documents compound, exclusion and wildcard syntax for its web search. The app may filter loaded fields instead. Use the server’s supported interface for complex queries and a clear title to locate the result in the app. Label each context and simplify a failed expression before suspecting damaged metadata.

Use namespaces to interpret similar terms

Namespaces clarify whether a repeated term denotes an author or subject. Verify the actual tag and test a distinctive portion without inventing namespace buttons or Boolean support. Compare title and identity when several results match. Correct your server metadata through its normal process and retain before/after evidence.

Verify the archive after finding it

Open beginning, middle and end to confirm the intended edition and readable pages. Tags do not prove image access, downloading or progress sync. Archive-based organisation can differ from series/chapter services. Record an anchor and verify re-entry from normal navigation without changing server contents.

Recheck targeted metadata updates

After a deliberate metadata correction, wait for the server’s processing, refresh normally and repeat the original simple query. Keep filenames, paths and account fixed. Report server fields, app fields and refresh results separately before rebuilding anything, retaining a known-good sample for future comparison.

Acceptance and empty-result checks

Finish with matching known metadata, understandable simple-query behaviour and the correct readable archive. Simplify unsupported expressions before assuming data loss. For missing authors, inspect actual tag namespaces and delivered fields. Report identity, term and stage without API keys.

Connect ManYue to LANraragi: archives, tags and a personal comic library; ManYue multiple servers: distinguish matching titles and personal library scope.

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 and Apple public version lookup. 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.

Also consult the official LANraragi web-search documentation; its server syntax does not establish equivalent client query support.