Although we have not implemented EAD3, I've started to use it conceptually and EAD3 has invaded my speech, particularly when it comes to our current effort to ingest all of our (just shy of 7000) finding aids from our existing EAD backed to ArchivesSpace. For example, we've been paying close attention to footages and gigabytes in extents in the hopes that we can ingest this data properly to then use them as "space occupied" extents.
Although many archivists' interaction with it may very soon not involve angle brackets and XML editing software, EAD is not dead. EAD at the moment is the lingua franca of archival description (I mean, it is a "metadata transmission standard for hierarchical descriptions of archival records".) If you want your inventories to hit ArchivesGrid and other awesome places where information is shared or re-purposed, it is important to continue to make your data available in a shared standard. In addition, getting your data into ArchivesSpace by keying is not efficient. I genuinely expect that data on resources will continue to be produced externally for some time (where it is more efficient to do so) and converted to EAD for ingest. Even if you key all your data into ArchivesSpace from now on, and even if your local search and discovery is via a single system, there are huge benefits to sharing outside that system.
Collections Services Archivist for Metadata, Systems, and Standards
Harvard University Archives
[log in to unmask]
voice: (617) 384-7787
fax: (617) 495-8011
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Peter Carini
Sent: Wednesday, February 17, 2016 10:55 AM
To: [log in to unmask]
Subject: Re: [EAD] EAD3 Implementation
I got nothin' for ya on this, but wanted to ask you a theoretical question instead of answering yours. ;-)
What do you see at the future of EAD?
I'm leaning away from EAD at the moment. We are using ArchivesSpace and I would like to use that as our public front end and abandon EAD altogether. We currently present our guides in EAD, but take no advantage what-so-ever of the power of the format. In addition, it is enormously problematic for archival record groups that are in a constant state of flux with new additions arriving biannually. Our guides to institutional records--and even some manuscript collections--are constantly out of date.
No need to respond quickly as this is purely theoretical and posed out of curiosity.
Hope all is well at Amherst!
From: Encoded Archival Description List <[log in to unmask]> on behalf of Kelcy Shepherd <[log in to unmask]>
Sent: Wednesday, February 17, 2016 9:05 AM
To: [log in to unmask]
Subject: EAD3 Implementation
I've been working on a piece on implementing EAD, and it has made me curious about the adoption of EAD3. Who is converting to, or actively planning their conversion to EAD3? What is your timeline for conversion? Are there any institutions just starting to encode their finding aids that are jumping right into EAD3?
Thanks in advance for sharing,
Head of Digital Programs
PO Box 5000
Amherst, MA 01002-5000