Hi there,
At the UK Archives Hub we currently store in EAD, but we are moving to a system where we will be storing JSON. But that’s OK because EAD is primarily for sharing the descriptions, so the important thing is how we can export. So, for example, we provide descriptions from the Archives Hub to the European Aggregator (Archives Portal Europe) and we’ve provided descriptions to Cendari (research portal). This kind of sharing requires a common data exchange format, and at the moment EAD is the best option to use.
We also take in descriptions from other systems, and at present we require these to be in EAD because that makes it possible to cope with large scale ingest. As it is, the variations in the data are substantial, but having everything in EAD is a good starting point, even if we do have to carry out quite a bit of transformation work to get all the data to a certain standard.
We aren’t planning on moving to EAD3 yet, as we have our work cut out implementing a new system.
all the best,
Jane
Jane Stevenson
Archives Hub Service Manager
[log in to unmask]
On 18 Feb 2016, at 15:12, Brian Sheppard <[log in to unmask]> wrote:
> Using a more restrictive localized schema is always an option. It will remain valid as an EAD, but can remove a lot of ambiguity or unneeded flexibility.
>
>> On February 18, at 8:10 AM, Regine I. Heberlein <[log in to unmask]> wrote:
>>
>> Our main issue is not with serializing to EAD but with the underlying data model of EAD, or absence thereof. We’re at this stage simply trying to model out entities and properties.
>>
>> As Ethan observes, as long as the data can be mapped to a shared standard for sharing purposes, there’s no issue. That standard is currently EAD as agreed-upon by the professional community, though personally I would also point out that as far as data standards go, it’s a pretty lax one, which comes with its own problems. But that’s a separate matter.
>>
>> Regine Heberlein
>> Principal Cataloger and Metadata Analyst, Rare Book Collections
>> Princeton University Library
>> One Washington Road
>> Princeton, NJ 08540
>> 609-258-6156
>>
>> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Roke, Elizabeth Russey
>> Sent: Wednesday, February 17, 2016 3:21 PM
>> To: [log in to unmask]
>> Subject: Re: EAD3 Implementation
>>
>> I’d be interested to hear from others who are considering moving away from EAD. How are you planning to store and query metadata in finding aids? RDF? Like many others, we’re outputting our EAD in RDF to serve “Big Data” computational analysis projects. But I still see value in having a shared way to store metadata that ensures some consistency among the archival community. If not EAD, then what?
>>
>> Best,
>> Elizabeth
>> ___________________________
>> Elizabeth Russey Roke
>> Digital Archivist
>> Stuart A. Rose Manuscript, Archives, & Rare Book Library
>> 404.727.2345 | [log in to unmask]
>>
>>
>>
>> "The Stuart A. Rose Manuscript, Archives, & Rare Book Library collects and connects stories of human experience, promotes access and learning, and offers opportunities for dialogue for all wise hearts who seek knowledge.”
>>
>> Read the Rose Library blog: https://scholarblogs.emory.edu/marbl/
>>
>> Like the Rose Library on Facebook: https://www.facebook.com/emorymarbl
>>
>> Follow the Rose Library on Twitter: https://twitter.com/EmoryRoseMARBL
>>
>> From: Encoded Archival Description List <[log in to unmask]> on behalf of "Regine I. Heberlein" <[log in to unmask]>
>> Reply-To: Encoded Archival Description List <[log in to unmask]>
>> Date: Wednesday, February 17, 2016 at 1:32 PM
>> To: "[log in to unmask]" <[log in to unmask]>
>> Subject: Re: EAD3 Implementation
>>
>> Hi Kelcy and Peter,
>>
>> We, too, are considering giving up on EAD altogether, though nothing concrete is in the works yet—it’s a theoretical consideration at this point. Basically the pain of moving to EAD3 doesn’t seem worth the small benefit to us and we’d rather move to a much more rigorous data model. I’d love to exchange notes with anyone also thinking along those lines.
>>
>> Cheers,
>>
>> Regine
>>
>> Regine Heberlein
>> Principal Cataloger and Metadata Analyst, Rare Book Collections
>> Princeton University Library
>> One Washington Road
>> Princeton, NJ 08540
>> 609-258-6156
>>
>>
>> -----Original Message-----
>> 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: EAD3 Implementation
>>
>> Hi Kelcy,
>>
>> 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!
>>
>> Peter
>>
>> _______________
>> Peter Carini
>> College Archivist
>> Dartmouth College
>>
>> ________________________________________
>> 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
>>
>> Hi all,
>>
>> 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,
>>
>> Kelcy
>>
>>
>> Kelcy Shepherd
>> Head of Digital Programs
>> Amherst College
>> PO Box 5000
>> Amherst, MA 01002-5000
>> 413-542-5481
>>
>>
>>
>>
>>
>> This e-mail message (including any attachments) is for the sole use of
>> the intended recipient(s) and may contain confidential and privileged
>> information. If the reader of this message is not the intended
>> recipient, you are hereby notified that any dissemination, distribution
>> or copying of this message (including any attachments) is strictly
>> prohibited.
>>
>> If you have received this message in error, please contact
>> the sender by reply e-mail message and destroy all copies of the
>> original message (including attachments).
>
> —————————————————————————————
> Brian Sheppard
> UW Digital Collections Center
> [log in to unmask]
>
>
>
>
>
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
|