Data sources
What WPH uses to document books, publishers, and translation movement
World Publishing Houses does not rely on one master feed. The product is built from edition-level source material that can be compared, cross-checked, and revisited when records change.
Last updated: April 8, 2026
Publisher pages and title listings
Publisher homepages, imprint catalogs, product pages, rights pages, and release announcements are the clearest starting point when WPH documents an edition or a publisher relationship.
Source registries
National bibliographies, ISBN-linked registries, library catalogs, and other public reference registries help confirm identifiers, publication dates, languages, and edition-level distinctions.
Catalog and metadata feeds
Where structured metadata is available, WPH may use ONIX-style feeds, distributor metadata, bibliographic APIs, and catalog exports to support edition matching and source comparison.
Translation and rights evidence
Translation paths, rights openings, grants, and market movement are documented from public publisher material, contributor disclosures, bibliographic records, and other sourceable public evidence.
How WPH Uses Sources
Different source types support different parts of the product
Publisher pages are the most direct public evidence for edition existence, imprint ownership, release timing, format, cover provenance, and sales-facing title copy.
Registries and library catalogs are useful for confirming identifiers, language codes, contributor names, and publication metadata when a publisher page is incomplete or has changed over time.
Catalog feeds and bibliographic APIs help WPH compare records at scale, but they are not treated as unquestionable truth. Structured feeds are strongest when they agree with a visible publisher or catalog source.
Translation and rights documentation is handled more cautiously. WPH looks for disclosed route evidence, contributor context, rights signals, grant references, or comparable public documentation before turning a hint into a surfaced opportunity.
Verification
Records are meant to be auditable, not just present
WPH stores source and provenance context at the edition level wherever possible. That allows one work to contain differently documented editions rather than flattening everything into a single undifferentiated book record.
Stronger records usually have more than one supporting signal: for example a publisher page plus a registry record, or a structured feed plus an auditable public source. When sources conflict, WPH prefers a partial record over a confident guess.
For the trust model behind these decisions, see Methodology.
Practical Limits
Not every field is equally easy to verify
Basic bibliographic details such as title, publisher, language, and release date are usually easier to confirm than translation paths, rights status, or contributor attribution history.
That is why some WPH pages are fuller than others. Country and edition pages may carry strong public evidence even when a global route view or rights summary is still light.
WPH does not turn missing detail into decorative certainty. If source support is thin, the page should say so plainly.
Related Policy
Image sourcing is handled separately
Cover images have their own sourcing and attribution rules. That part of the pipeline is documented separately because image provenance and display permission are not the same as ordinary bibliographic metadata.
For that policy, see Cover & Attribution Policy.