Data roles are conflated
Commercial data and catalogue records serve different uses.
ONIX supports product selection; it does not by itself guarantee a full catalogue record.
Our library supply service covers Russian and Ukrainian books only.
Describe your library taskThe system role and data handover are designed for the institution; this is not a standard integration claim.
01
Commercial data and catalogue records serve different uses.
The receiver must name expected identifiers and prices.
02
Version, identifiers, commercial fields, update timing, and receiving use are agreed before any ONIX handover.
03 / Example of an agreed profile
We accept the library's existing acquisition data, verify the title and availability, and return the agreed fields to the library workflow.
ISBN, title list, order reference, and the acquisition fields required by your library.
We map fields, check required values, and prepare a limited test specimen for acceptance.
Verified bibliographic data, price, and status through the agreed format and transport route.
Illustrative example. Field mapping, character set, validation, and transport are agreed before a pilot.
ProductIdentifier/IDValue ← 978-5-17-160839-2
TitleDetail/TitleText ← название книги
Contributor/PersonName ← Сьюзи Литтл
Publisher/PublisherName ← АСТ
PublishingDate ← 2026
PriceAmount ← 43.00
CurrencyCode ← <согласованный источник>04
Confirm product metadata use.
Agree commercial elements.
Validate one message.
05
ISBN, contributor, publisher, price, and availability are present.
06
Trade metadata is not presented as MARC.
Commercial data supports review.
07 / Exlibrus