Goobi-to-Goobi
Administration plugins for migrating from one Goobi workflow system to another Goobi workflow system
Last updated
Administration plugins for migrating from one Goobi workflow system to another Goobi workflow system
Last updated
Identifier
intranda_administration_goobi2goobi_export intranda_administration_goobi2goobi_import_infrastructure intranda_administration_goobi2goobi_import_data
Repository
Licence
GPL 2.0 or newer
Last change
25.07.2024 11:11:13
The two plugins described here can be used to transfer data from one Goobi workflow system to another Goobi workflow system (Goobi-to-Goobi). This documentation explains how to install, configure and use the associated plugins.
Before the export and import mechanism can be used, various installation and configuration steps must be completed. These are described in detail here:
The mechanism for transferring data from one Goobi workflow system to another Goobi workflow system (Goobi-to-Goobi) is divided into three major steps.
These three steps are as follows:
The first step involves enriching the data within the file system on the source system with the information that Goobi has stored internally in the database for each process. When this step is performed, an additional xml file containing the database information on the workflow and some other necessary data is written to the folder for each Goobi process.
After the complete creation and enrichment of the export directories on the source system, they can be transferred to the server of the target system. This can be done in different ways. Due to the amount of data involved, a transfer using rsync has proven to be the most suitable.
After the export directories have been successfully transferred to the target system, the data can be imported there. To do this, the data must be stored in the correct place in the system and some further precautions regarding the infrastructure must also be prepared.
