An application for publishing archival description and digitised records. Data is supplied by archival processing systems; Aron takes care of presentation, search and permanent links.
Aron makes the archival description and digitised records available to researchers: full-text search and filtering, browsing archival fonds from the top level down to individual records, and a permanent link to every record.
The archival description is created in Elza or in another archival processing system and is passed to Aron automatically. The archivist transfers nothing by hand – whatever the archive has processed and marked for publication is published.
The name, logo, colours, menu and descriptive model come from configuration, with no changes to the program. The interface is available in Czech and English and meets the WCAG 2.1 accessibility guidelines at level AA.
Built, ready-to-run versions of Aron are available for download free of charge. For Linux deployments we also provide deployment scripts that automate installation, updates and backups.
The administration guide covers installation, upgrading, configuration and operation of the Aron system.
The application is open source under the Apache 2.0 licence. The archive is therefore not tied to a single supplier: it can run the publishing software itself, have it adapted to its needs, or take part in its development.
Aron is an open source application for publishing archival description, including the display of digital archival objects (digitised archival records).
The archival description is created in Elza or in other software for processing archival records and is passed to the publishing system automatically. Aron does not interfere with the creation or management of the archival description; it displays what the archive has processed in its own system and decided to publish.
Aron lets researchers search the archival description, browse the hierarchy of archival fonds and view the attached digitised records.
With Aron, the archive gains a high-quality publication layer it does not have to build itself.
The source code is published under the Apache 2.0 licence.
If you are interested or have any questions, contact us by e-mail at aron-podpora@lightcomp.cz. We will be happy to answer them.
The Aron application can be operated in several ways. We will gladly help you choose the option that suits you best.
Both the source code and the builds of the system are freely available under the Apache 2.0 licence. The system is a single runnable application with its configuration in files alongside it, so the archive can deploy and run it on its own. We do not provide technical support for the freely available versions.
We deploy the system in your infrastructure for you – installation, configuration of the descriptive model and appearance, connection to the archival system, and updates to new versions. Technical and methodological support is included.
We run the system on our infrastructure. The archive does not have to worry about the server, updates or backups and can concentrate on the content it publishes.
From the archival systems in which the archive processes its holdings – the Elza application, the PEvA register and other systems. Data is delivered to the application automatically by a service that collects it from the archival system; the archivist transfers nothing by hand and enters nothing in Aron.
Elza is a tool for processing archival records and creating the archival description in line with standards and methodological rules. Aron is a publishing system for researchers that makes the finished description accessible. The two are used together: whatever is processed in Elza and marked for publication appears in Aron.
Aron is a single runnable application that also contains the web interface; it needs a PostgreSQL database. For full-scale operation we recommend Elasticsearch; smaller deployments can use the built-in search engine, which needs no additional service.
No. The same application can run either at the root of an address or in a subdirectory of an existing website, without a special build.
Yes, both are a matter of configuration. The name, logo, colours, menu, home page, displayed description elements and filters are all set in configuration files, with no changes to the program and no custom build of the application.