I am using "External Documents" sub-records to link to external web pages containing information that supplements biographical / historical information documented in a finding aid. The URLs in the External Documents work in both the staff and public interfaces of ArchivesSpace, but when I export the finding aid to EAD, the External Documents (including URLs) are missing.
External Documents are not mapped to an EAD element, so not included in EAD exports. The standard tooltip for the External Documents sub-record says "Links to information in other description or management systems, such as donor files, processing plans, etc." but it is definitely possible to include other kinds of information there, especially since there's a publish checkbox. It would be good to hear from others in the community whether they would want External Documents to be part of an EAD, and how they'd map them.
Thank you for your response, Christine. When I started using the External Documents to link to external resources, I assumed that the External Documents would map to the <extref> "Extended Reference" EAD element in an export. Though I'm not sure why I made this assumption or if the <extref> element is already being used for some other purpose in ASpace EAD exports.
I also thought that it might be useful to create a distinction between using (1) Digital Objects: to link Archival Object or Resource records to digitized archival resources in a collection vs. (2) External Documents: to link Archival Object or Resource records to online documents that provide supplemental information about the collection from external sources, such as an article, Wikipedia entry, or a finding aid published by a different institution.
Perhaps others have made this distinction via other means. Are you aware of any common practices to achieve this distinction? Or do you think users generally use Digital Objects for both of the purposes described in my previous paragraph? This might be a question for the ArchivesSpace Users Group list.
Thanks again for your feedback, Christine!
Commenting on behalf of the Dev Pri sub-team. We feel there is not a need to map External Documents to an EAD tag and <extref> is a linking element (http://eadiva.com/2/extref/) so we are closing this ticket.