Exporting EAD from various external systems
The Archives Hub is moving towards a more sustainable and efficient method of data processing. 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.
Our aim is to take descriptions in via two main routes:
1. The Hub EAD Editor
2. Exports from archival systems
We are working to create 'pipelines' for exported EAD descriptions:
1. The EAD descriptions are created by using an EAD export facility from within the archive software system
2. The exports are sent to the Hub
3. The Hub runs the EAD through one or more pipelines, that ensure it is valid EAD and compliant with Hub EAD requirements
4. We work with the contributor to iron out any errors or problems with the EAD
5. When the EAD is valid and Hub compliant it goes live
6. The aim is to then be able to take in further descriptions as you submit them and run them through the pipeline so that they are efficiently uploaded to the Archives Hub.
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.
More Information on exporting from archival systems
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.
'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'