Harvest direction unclear
A repository page does not identify consumer or allowed set.
Professional support for library collections and private collectorsFrom Düsseldorf to the World
A harvest is repeatable only when set and update semantics are explicit.
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 repository page does not identify consumer or allowed set.
Dates and deletion markers affect accuracy.
02
Direction, allowed sets, deletion treatment, schedule, and target use are agreed before repeated collection.
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.
baseURL: <agreed repository>
set: <agreed set>
metadataPrefix: <agreed prefix>
source_book_id: 131711
incremental window: <agreed from/until rule>04
Name publisher, harvester, use.
Agree range and deletion rules.
Inspect one response.
05
A request records set, prefix, identifiers, and dates.
06
Update logic is documented.
Repository scope remains agreed.
07 / Exlibrus