Custom SIKB0102 integration development
Appfront builds integrations with SIKB0102, the standard for the digital exchange of data from archaeological research. Archaeological companies, repositories, municipalities and the national information service use it to exchange data in an XML file, the packing slip, containing feature lists, find lists and box lists, among other things. We build the integration that creates a packing slip from your own fieldwork or finds registration, or reads a received packing slip into your repository or collection 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 packing slip. An archaeological company exports a packing slip from its own system, and the recipient, such as a repository, reads it into its own system. SIKB0102 is a different standard from the one for soil data.
Without an integration, data from a study is put into a format by hand, or supplied separately in spreadsheets alongside the boxes. A repository receives boxes of finds and has to transfer the data into its own system. Errors in a packing slip only come to light at the recipient. And anyone looking for a find in a repository cannot trace the data from the study back to the box.
We build custom because the integration has to fit your registration: which system you use for fieldwork, finds or repository management, which data it contains, which version of the standard your recipients ask for, and how boxes and storage locations are tracked. The standard is maintained by SIKB; we make sure your software works with it.
Packing slip from your system
A packing slip in line with SIKB0102, created from the data of your study: project, features, finds, samples, documents and boxes.
Validated before delivery
Validation against the requirements of the standard before the packing slip is delivered, so errors don't surface at the recipient.
Reading in at the recipient
A received packing slip read into your repository or collection system, with finds and boxes linked to storage locations.
How we build your SIKB0102 integration
We start with your studies or your repository: which system, which data, which version of the standard, and how things work now.
Your system, the data from studies or the repository, the version of the standard, and your recipients or suppliers.
The translation between your data and the packing slip, in the direction you need.
Validation against the requirements of the standard, with clear messages about what is missing or incorrect.
Testing with real studies and recipients, go-live, and maintenance when new versions of the standard are released.
What a SIKB0102 integration actually does
The components below feature in almost every SIKB0102 integration. Which ones you need depends on your role.
Creating packing slips
A packing slip from the project, features, finds, samples, documents and boxes in your system.
Reading in packing slips
A received packing slip read into your repository or collection system.
Validation
Validation against the requirements of the standard before delivery or after receipt.
Boxes and storage locations
Boxes and finds linked to storage locations in the repository.
Versions
Support for the version your recipients or suppliers use.
Log
For each packing slip: what was created or read in, when, and with what result.
Who we build a SIKB0102 integration for
The integration is intended for parties that exchange archaeological data.
Archaeological companies
Surveys that need to be delivered. The delivery note from your own system is the core.
Municipal archaeological services
In-house research and supervision. The check before delivery matters most.
Repositories and e-repositories
Receiving boxes and data. Importing and storage locations are what you need.
Software suppliers
Software for fieldwork or repository management. Supporting the standard is the core.
Technology and integrations
This page covers archaeological data under SIKB0102. For collection registration, see our page on collection registration and loan administration, for museum collections our page on collection management for museums, and for soil investigation under the SIKB protocols our page on SIKB software. You can read about our approach on building custom software.
For environmental soil investigation, with boreholes, samples and lab results, see our page on a SIKB0101 integration.
Why Appfront for your SIKB0102 integration?
A find without the data from the research loses part of its value. That is what we build on: data that follows the standard, validated before delivery, and imported where the boxes are stored.
No manual work
The delivery note comes from your system, not from a spreadsheet.
Errors caught early
Validation before delivery catches what the recipient would otherwise reject.
Data with the box
In the repository, the research data sits with the box and the find.
Security and privacy for a SIKB0102 integration
The integration processes data about sites and finds, information that is often not public in order to protect sites. Access is set up per 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 companies and repositories ask before getting started.
SIKB0102 is the standard for exchanging data from archaeological research digitally, maintained by SIKB. Data is exchanged in an XML file, the delivery note.
Among other things, data about the project, features, finds, samples, documents and boxes, as the standard prescribes.
No. SIKB0102 covers archaeological data. Soil and groundwater data have a different SIKB standard. Soil investigation under the SIKB protocols has its own page on this site.
Yes. Before delivery, the integration checks the delivery note against the requirements of the standard, with messages about what is missing or incorrect.
Yes. A received delivery note is imported into the repository or collection system, with boxes and finds linked to storage locations. Anyone searching for a find later will find the research data with the box.
The version your recipients or suppliers use. When a new version comes out, we adapt the integration in the admin. Where a recipient still asks for an older version, the integration can deliver both.
For archaeological companies, services and repositories with their own system, and for software suppliers that need to support SIKB0102.
Archaeological data following the standard, from and to your own system?
Tell us which system you use, whether you deliver or receive, and how it works now. We will show you what the delivery note, the validation and the import look like.