Custom SIKB0102 integration development
Appfront builds integrations with SIKB0102, the standard for digitally exchanging data from archaeological research. Archaeological firms, depots, municipalities and the national information infrastructure exchange data through it in an XML file, the pakbon (delivery note), containing, among other things, lists of features, finds and boxes. We build the integration that generates a pakbon from your own fieldwork or find registration, or that imports a received pakbon into your depot or collections system.
What is a SIKB0102 integration?
SIKB0102 is the standard for exchanging digital data from archaeological research. It describes which data is exchanged, such as feature lists, find lists and box lists, and how it is structured in an XML file. That file is called the delivery note (pakbon). An archaeological firm exports a delivery note from its own system, and the recipient, such as a repository, imports it into theirs. SIKB0102 is a different standard from the one for soil data.
Without an integration, research data is entered manually in a format, or supplied separately in spreadsheets alongside the boxes. A depot receives boxes of finds and has to transfer the data into its own system. Errors in a pakbon only surface at the recipient's end. And anyone searching for a find in a depot cannot trace the research data back to the box.
We build custom because the integration must match your registration: which system you use for fieldwork, finds or depot management, what data it holds, which version of the standard your recipients require, and how boxes and storage locations are tracked. The standard is maintained by SIKB; we make sure your software works with it.
Delivery note out of your system
A SIKB0102 delivery note generated from your research data: project, features, finds, samples, documents and boxes.
Checked before delivery
Checks against the standard's requirements before the delivery note is sent, so errors don't surface at the recipient.
Import at the recipient
A received pakbon imported into your depot or collections system, with finds and boxes linked to storage locations.
How we build your SIKB0102 integration
We start with your research or repository: which system, which data, which version of the standard, and how things work today.
Your system, the research or repository data, the version of the standard, and your recipients or suppliers.
The translation between your data and the delivery note, in the direction you need.
Checks against the requirements of the standard, with clear notices about what is missing or incorrect.
Testing with real investigations and recipients, going live, and management when new versions of the standard are released.
What a SIKB0102 integration does in practice
The components below recur in almost every SIKB0102 integration. Which ones you need depends on your role.
Creating a packing list
A packing list from project, feature, find, sample, document and box data in your system.
Importing a packing list
A received packing list imported into your depot or collections system.
Validation
Checks against the requirements of the standard before delivery or after receipt.
Boxes and storage locations
Boxes and finds linked to storage locations in the depot.
Versions
Support for the version used by your recipients or suppliers.
Audit log
For each packing list, what was created or imported, when, and with what result.
Who we build SIKB0102 integrations for
The integration is intended for parties that exchange archaeological data.
Archaeological firms
Investigations that must be delivered. The packing list from your own system is the core.
Municipal archaeological services
Own investigations and supervision. The check before delivery matters most.
Depots and e-depots
Receipt of boxes and data. Importing and storage locations are what is needed.
Software suppliers
Software for fieldwork or depot management. Support for the standard is the core.
Technology and integrations
This page is about archaeological data under SIKB0102. For collection registration, see our page on collection registration and loan management; for museum collections, see our page on collection management for museums; and for soil investigation under the SIKB protocols, see our page on SIKB software. You can read about our approach under custom software development.
For environmental soil investigation, covering boreholes, samples and laboratory results, see our page on a SIKB0101 integration.
Why choose Appfront for your SIKB0102 integration?
A find without the investigation data loses part of its value. That is what we build on: data according to the standard, checked before delivery, and imported where the boxes are stored.
No manual work
The packing list comes from your system, not from a spreadsheet.
Errors caught in advance
Checking before delivery catches what the recipient would otherwise reject.
Data with the box
In the depot, the investigation data stays with the box and the find.
Security and privacy for a SIKB0102 integration
The integration handles data on find locations and finds, information that is often not public in order to protect sites. Access is set up by role, and every delivery note is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a SIKB0102 integration
Questions that archaeological firms and depots ask before getting started.
SIKB0102 is the standard for digitally exchanging data from archaeological investigations, managed by SIKB. Data is exchanged in an XML file, the packing list.
Among other things, data about the project, features, finds, samples, documents and boxes, as the standard prescribes.
No. SIKB0102 concerns archaeological data. For soil and groundwater data there is a different SIKB standard. For soil investigation under the SIKB protocols there is a separate page on this site.
Yes. Before delivery, the integration checks the delivery note against the requirements of the standard, with notices about anything missing or incorrect.
Yes. A received delivery note is imported into your depot or collection system, with boxes and finds linked to their locations. Anyone who later searches for a find can see the details of the investigation alongside the box.
The version your recipients or suppliers use. When a new version is released, we adjust the integration in its management. Where a recipient still requests an older version, the integration can supply both.
For archaeological firms, services and repositories with their own system, and for software suppliers who need to support SIKB0102.
Archaeological data according to the standard, to and from your own system?
Tell us which system you use, whether you send or receive, and how things work at the moment. We will show you what the delivery note, the check and the import look like.