Currently all meta-data that was imported into AtoM and subsequently amended by the TI staff is only being backed up as MySQL data. This may not be a very useful format as the actual data is spread over many tables structured after the AtoM data model.
It would be preferable to have (recent) EAD exports available at any time in the future.
As discussed today, one way to achieve it could be a script that is triggered daily/weekly by a cron job on projects VM (where Elasticsearch resides) or directly on the web server of dialog/webprojekt. The exports could be stored on a volume that is backed up by TSM or alternatively sent to a dedicated mail address/mailing list.
@Sviat2513, maybe you can have a look at the export feature of Symfony (as described here in the Atom 2.1 documentation) and think of a solution.
Currently all meta-data that was imported into AtoM and subsequently amended by the TI staff is only being backed up as MySQL data. This may not be a very useful format as the actual data is spread over many tables structured after the AtoM data model.
It would be preferable to have (recent) EAD exports available at any time in the future.
As discussed today, one way to achieve it could be a script that is triggered daily/weekly by a cron job on projects VM (where Elasticsearch resides) or directly on the web server of dialog/webprojekt. The exports could be stored on a volume that is backed up by TSM or alternatively sent to a dedicated mail address/mailing list.
@Sviat2513, maybe you can have a look at the export feature of Symfony (as described here in the Atom 2.1 documentation) and think of a solution.