Koha environment

Koha acquisitions, EDI/import and local-field profile

Koha configuration is local, so the import framework matters.

Our library supply service covers Russian and Ukrainian books only.

Describe your library task

Custom solution

The system role and data handover are designed for the institution; this is not a standard integration claim.

Naming a system does not claim partnership, certification, or a pre-built connector.

When this is useful

Libraries operating Koha
Teams maintaining Koha imports

Instances differ

Versions, plugins, frameworks, and fields vary.

Import is untested

MARC or EDI needs library-side evidence.

Document a Koha instance's acquisitions, EDI, or MARC-import profile before data or order handover; instances are not assumed identical.

The workflow begins with version, import framework, local fields, and test data—not a universal connector claim.

What you send

Koha profile: Version, framework, route, fields
Test material: Sample MARC or order data

What you receive

Instance map: Fields, route, controls
Test evidence: Observed local outcome

The agreed workflow

01
Describe instance
Collect version and framework.
02
Map sample
Agree destination fields.
03
Inspect result
Validate local test.

A concrete working example

Example: MARC import into Koha

A test record is checked in the import framework.

Profile: Koha version and framework
Result: Record fields appear

What Exlibrus contributes to the process

Instance-aware

Other installations do not dictate this one.

Local rules kept

Compatibility is tested.

Koha environment

Koha acquisitions, EDI/import and local-field profile

Koha configuration is local, so the import framework matters.

Our library supply service covers Russian and Ukrainian books only.

Describe your library task

Custom solution

The system role and data handover are designed for the institution; this is not a standard integration claim.

Naming a system does not claim partnership, certification, or a pre-built connector.

When this is useful

Libraries operating Koha
Teams maintaining Koha imports

Instances differ

Versions, plugins, frameworks, and fields vary.

Import is untested

MARC or EDI needs library-side evidence.

Document a Koha instance's acquisitions, EDI, or MARC-import profile before data or order handover; instances are not assumed identical.

The workflow begins with version, import framework, local fields, and test data—not a universal connector claim.

What you send

Koha profile: Version, framework, route, fields
Test material: Sample MARC or order data

What you receive

Instance map: Fields, route, controls
Test evidence: Observed local outcome

The agreed workflow

01
Describe instance
Collect version and framework.
02
Map sample
Agree destination fields.
03
Inspect result
Validate local test.

A concrete working example

Example: MARC import into Koha

A test record is checked in the import framework.

Profile: Koha version and framework
Result: Record fields appear

What Exlibrus contributes to the process

Instance-aware

Other installations do not dictate this one.

Local rules kept

Compatibility is tested.

Koha acquisitions, EDI/import and local-field profile | Exlibrus

Koha acquisitions, EDI/import and local-field profile

Instances differ

Import is untested

What you send

What you receive

Describe instance

Map sample

Inspect result

Example: MARC import into Koha

Instance-aware

Local rules kept

Related building blocks

Describe your library task

Koha acquisitions, EDI/import and local-field profile

Instances differ

Import is untested

What you send

What you receive

Describe instance

Map sample

Inspect result

Example: MARC import into Koha

Instance-aware

Local rules kept

Related building blocks

Describe your library task