Science History Institute ArchivesSpace Scripts

Important

This code is no longer used and the repository was archived in August 2022. Backups are being provided by our ArchivesSpace third party provider. EAD harvest is being managed by https://github.com/sciencehistory/export_archivesspace_xml .

About

• This was a collection of scripts we use to manage and back up our ArchivesSpace instance.
• It did two main things:

1. Allow our EADs to be harvested over HTTP by peer institutions.
2. Provide scripts for a cronjob to back up our ArchivesSpace data.

Credits

• Much of this work is due to Sarah Newhouse and Daniel Sanford.
• Eddie Rubeiz spent some time in summer 2020 cleaning it up, making it more reliable and documenting it.

Installation

• When you create a new ArchivesSpace server, check this code out into the /home/ubuntu on our ArchivesSpace server: /home/ubuntu/archivesspace_scripts.
• Make sure the directory is owned by the ubuntu:ubuntu user.

Usernames and passwords

To allow the code to talk to the ArchivesSpace, you will want to put usernames and passwords will go into script_settings.sh Run cp script_settings_sample.sh script_settings.sh

Export instructions

• To run a complete export, just run ./complete_export.sh. This shields you from a number of steps that were previously run manually, to get around the fact that:
  • the server has yet to be fully set up in Ansible

Next Steps

• Eliminate setup.sh. The commands in that script should be moved to the Ansible configuration.
• Make it possible for the code to be checked out in an arbitrary location. (Currently, the directory /home/ubuntu/archivesspace_scripts is hardcoded in various places.)
• Add the complete_export.sh cron job to Ansible, so that a new server automatically runs it.
• When building a new ArchivesSpace server, automate the checkout of this code into the /home/ubuntu directory.
• Remove the two backup scripts (s3-backup.sh mysql-backup.sh) and place them in the Ansible code. They don't really belong in this code.
• Get rid of script_settings.sh and script_settings_sample.sh too. Their only function is to serve as a bandaid so we can make sure the export scripts are checked into Github without any passwords in it.