The Editor provides the facility to upload EAD. However, there are caveats that you need to be aware of.
EAD is a complex and permissive standard. There are a large number of tags and attributes, and options about how tags are used and nested. It is not possible for the Editor to deal with all of these options.
There are three versions of EAD, but we only work with EAD2002. You cannot upload EADv1 and we do not advise uploading EAD3 as the Editor may not deal with the differences compared to EAD2002.
If your EAD description uses the fields that are included within the Editor, then the upload should populate all of those fields accordingly
Treatment of EAD in the Editor
If your EAD description uses fields that the Editor does not use, our aim is to preserve the data, so that when you submit the description (or download it) that data remains intact. However, you may not necessarily be able to see the content within the Editor itself.
Please be aware: there may be combinations of tags and attributes that are not recognised by the Editor, so you need to be aware of this when uploading EAD. We can address many of these issues as they are raised, but we will never be able to accommodate all of the variations within EAD.
We have taken steps to accommodate some of the more common fields and attributes that are used in EAD descriptions. ,
It may be that a description does not upload successfully and you get a message that it is invalid. If you are not sure why this is the case, please email us.
Uploading Calm EAD
It is not possible to upload Calm EAD to the Editor. This is because there is so much variation in the EAD output from Calm that we cannot deal with it in our Editor processing. We need to deal with it through our data ingest pipelines, which analyse the data and check for Hub valid EAD. For example, Calm EAD exports may have the Calm reference and an Alt Ref, which may be the same or different to the Calm reference, and you may wish to use it as the main reference, just display it as an alternative reference, or remove it on upload to the Archives Hub. This is the kind of thing we can deal with in our pipelines, but not through our Editor.
We have not tested the EAD output from all archival management systems, but all should be treated with caution and we highly recommend talking to us about providing a direct export of the EAD to us, and by-passing the Editor.