Target is assumed generic
Each database has its own permitted searches and syntax.
A connection profile explains what is queried and what response is expected.
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
Each database has its own permitted searches and syntax.
A connection does not prove usable bibliographic output.
02
A connection test is needed because databases, attributes, syntax, and local access rules vary.
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.
search term: 978-5-17-160839-2
use attribute: <from target profile>
database: <agreed database>
record syntax: <agreed syntax>
character set: <agreed charset>
connect → search → present → validate04
Record database and access.
Specify query and record form.
Retrieve known item.
05
A named database returns a known MARC record for inspection.
06
The profile is institution-specific.
Known records expose limits.
07 / Exlibrus