Discovery layer

VuFind discovery and explicit source-system mapping

Source → index → discovery card makes visible data problems explainable.

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 using VuFind
Cataloguing and technical teams

Origin is hidden

A visible error can originate in source or index.

Discovery is treated as supply

A search UI does not create an order connector.

Map source system, index route, and visible metadata for a VuFind environment; VuFind is not a ready supplier-order channel.

The profile traces source record to index and discovery card so issues reach the correct layer.

What you send

Data chain: Source, load, index, display fields
Test set: Known ISBNs and searches

What you receive

Presentation map: Where data enters and appears
Review record: Source, index, result comparison

The agreed workflow

01
Name source
Identify producing system.
02
Check index
Review search and card fields.
03
Assign correction
Choose source, index, or display.

A concrete working example

Example: VuFind ISBN trace

One book is checked from MARC source to result.

Chain: Source → index → card
Result: Visible/missing fields

What Exlibrus contributes to the process

Diagnostic route

Issues reach the responsible layer.

Honest framing

VuFind is discovery, not an order proof.

Discovery layer

VuFind discovery and explicit source-system mapping

Source → index → discovery card makes visible data problems explainable.

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 using VuFind
Cataloguing and technical teams

Origin is hidden

A visible error can originate in source or index.

Discovery is treated as supply

A search UI does not create an order connector.

Map source system, index route, and visible metadata for a VuFind environment; VuFind is not a ready supplier-order channel.

The profile traces source record to index and discovery card so issues reach the correct layer.

What you send

Data chain: Source, load, index, display fields
Test set: Known ISBNs and searches

What you receive

Presentation map: Where data enters and appears
Review record: Source, index, result comparison

The agreed workflow

01
Name source
Identify producing system.
02
Check index
Review search and card fields.
03
Assign correction
Choose source, index, or display.

A concrete working example

Example: VuFind ISBN trace

One book is checked from MARC source to result.

Chain: Source → index → card
Result: Visible/missing fields

What Exlibrus contributes to the process

Diagnostic route

Issues reach the responsible layer.

Honest framing

VuFind is discovery, not an order proof.

VuFind discovery and explicit source-system mapping | Exlibrus

VuFind discovery and explicit source-system mapping

Origin is hidden

Discovery is treated as supply

What you send

What you receive

Name source

Check index

Assign correction

Example: VuFind ISBN trace

Diagnostic route

Honest framing

Related building blocks

Describe your library task

VuFind discovery and explicit source-system mapping

Origin is hidden

Discovery is treated as supply

What you send

What you receive

Name source

Check index

Assign correction

Example: VuFind ISBN trace

Diagnostic route

Honest framing

Related building blocks

Describe your library task