Event meaning is missing
A label may not explain shipment or exception.
Professional support for library collections and private collectorsFrom Düsseldorf to the World
A narrow event tells the receiver what changed and how to verify it.
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
A label may not explain shipment or exception.
Retries and an exception route are required.
02
Events, payload, endpoint ownership, signature, and retry policy need a technical agreement.
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.
{
"event": "<agreed-event>",
"bookId": 131711,
"isbn": "978-5-17-160839-2",
"status": "stock"
}
signature · retries · timing → <agreed contract>04
Specify one change and meaning.
Document payload and retry.
Inspect a bounded notification.
05
An order reference and status are signed for the receiver.
06
Every event has known meaning.
Failure treatment is explicit.
07 / Exlibrus