Exporting EAD from various external systems
The Archives Hub is developing export processes for archival systems. Consistency and repeatable processes are a priority for us, so that we avoid version control issues, save time, and ensure that our descriptions reflect your own master copies.
The Export Process
EAD descriptions are created:
- using an EAD export facility from within the archive software system
- using OAI-PMH to harvest directly from a system
We put the data through 'pipelines' that check and validate the data. We analyse the results and may create an error report if required. We will work with the contributor to deal with the errors. Our aim is to provide help and support throughout the process.
We may be able to run scripts to address some of the errors, whilst others will require the contributor to make changes, for example, invalid dates or missing titles.
When the EAD is valid and Hub compliant it goes live and we ensure that the contributor is set up in our Admin Interface with the correct pipeline. This will mean that they can then upload data themselves, as and when they wish, so that it goes live immediately.
If you are interested in exporting from your archival system, please contact us. We are likely to ask you for a sample of your data in the first instance, so that we can start to analyse it and create a suitable pipeline.
If you have the knowledge and resources to create a bespoke EAD export, you may like to look at our EAD for the Hub page.
Please note: these pages are frequently updated as we work towards an integrated and automated workflow, but they will give you some information about what is required for exporting.
- Exporting from Calm
- Exporting from AdLib
- Exporting from ICA AtoM
- Exporting from Epexio
- Exporting from Modes
'The export looks great and I'm delighted that full descriptions of the archive collections at [the centre] will now be available via the Hub. Thank you for all your patience and hard work helping me work through the process'