Annual release 2022
In April 2022, all components were once again tagged to create a coherent setup of all applications. For this annual release feeder has received major updates, both in functionality as well as for the UI.
Solution components
| Component | Version | Description |
|---|---|---|
| docuteam feeder | 5.7 | Since 5.3 in 2021, there were a number of larger updates, e.g. an event API has been added, the UI framework has been replaced entirely, depositions can be uploaded using the UI, and quite a few useability improvements have been added. The UI framework update requires recent browsers (IE is not supported anymore). |
| docuteam packer | 6.3 | Additional functionality like a CSV metadata import has been added, and Italian language is supported. |
| docuteam actions | 6.3 | Improvements to existing actions are available. |
| docuteam rservices | 5.9 | Although rservices will be replaced in the context of the Fedora upgrade, security updates and bugfixes were applied. |
| docuteam bridge | 1.4 | "docuteam bridge API" is now integrated into docuteam feeder, creating consistent authorization and aligning models. |
| Fedora Repository Software | 3.8 | Given that version 6 of the Fedora Repository software is not yet published, we'll stay with 3.8.1 for yet another annual release. However, the migration paths have been pushed very much, and we're getting ready behind the scenes to offer an upgrade during the current year. |
| AtoM | 2.6 | We use the latest stable release of AtoM, extended with a plug-in to access the digital repository objects. |
General setup and requirements
Given that many of our clients prefer Windows environments, this corresponds to our default platform for on-site installations, where we support the latest versions (2019 and 2022). The instances should have minimal resources (4-8 CPU cores, 16GB RAM). Also by default, applications are installed on a separate drive/partition than the OS, requiring 100-200GB. Our preferred database system is Postgres. Other operating systems and DBMS may be supported, but have to be evaluated specifically. Backup is usually managed by the client, in consultation/collaboration with us.
By default, a setup of these applications is done using two server instances:
- One server with the applications for managing the ingest processes, primarily consisting of docuteam feeder and docuteam actions. In addition to the above requirements, a separate disk drive/partition is required as workbench, usually 3-4 times the size of the largest deposition to process.
- One server instance for the repository stack, currently Fedora Repository Software with docuteam rservices. Apart from the above requirements for OS and applications, the repository will need a storage area big enough to contain the records to be preserved, usually >=1TB.