XML does not define mapping
Local treatment can differ after transformation.
Professional support for library collections and private collectorsFrom Düsseldorf to the World
XML makes structure inspectable, but the target mapping needs an explicit contract.
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
Local treatment can differ after transformation.
Namespaces and encoding need a sample.
02
The profile names MARCXML schema, source fields, transformation, encoding, and target validation.
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.
<datafield tag="020">
<subfield code="a">9785171608392</subfield>
</datafield>
<datafield tag="245">
<subfield code="a">Как начать писать: от заметки в блоге до большого романа</subfield>
</datafield>
<!-- mapping fragment, not a complete validated record -->04
Document schema and constraints.
Generate an XML record.
Check it with the library.
05
Bibliographic elements and a local order reference are inspected.
06
The file is reviewable before import.
Compatibility is target-specific.
07 / Exlibrus