Transport is mistaken for format
SFTP does not define MARC, CSV, or EDIFACT contents.
Professional support for library collections and private collectorsFrom Düsseldorf to the World
A file route is useful when its receipt and acceptance are observable.
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
SFTP does not define MARC, CSV, or EDIFACT contents.
Both parties need acknowledgement rules.
02
Transport is separate from format: folders, naming, schedule, access, receipt, retention, and errors are all explicit.
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.
file: <agreed-name>.csv
source_issue: 139
book_id: 131711
sha256: <calculated-on-delivery>
directory: <institution-specific>
SFTP is preferred; FTP only after constraints are agreed.04
Name content and transport.
Set folders, access, timing.
Transfer a sample.
05
A timestamped file is placed and acknowledged after validation.
06
Transport does not hide mapping limits.
Access and retention are considered.
07 / Exlibrus