Print

Print


The next release of CONTENTdm (expected later this fall) will include improved EAD handling, including the ability to parse the EAD then customize a mapping of its tags to CONTENTdm metadata fields, and functionality to render an EAD, via DTD and XSL, as formatted HTML pages.  
 
More information about the improved EAD handling will be available upon release.
 
Judy Cobb
Product Manager, OCLC Digital Collection Services
[log in to unmask]
614 764 6233

________________________________

From: Encoded Archival Description List on behalf of Michele R Combs
Sent: Thu 10/2/2008 3:00 PM
To: [log in to unmask]
Subject: Re: EAD and CONTENTdm



We abandoned this idea a while ago, partly but not solely due to
continuing problems in getting it working.  Although ContentDM has
nominal EAD support, the fact is that it's designed for images, not
text.  It simply doesn't handle EAD files in a very sophisticated
manner, and certainly doesn't take full advantage of the format.  For
example, ContentDM only indexes 7 of the EAD elements; dates, subject,
abstract and scopecontent are not among them and we felt those were
pretty important (see
http://www.dimema.com/help4/acq-station/importing2a.html ).  Only the
first 128,000 characters are indexed for full-text searching.  Also,
ContentDM doesn't render the EAD before sending it out to the client, it
sends straight XML and puts the burden of rendering on the client-side;
since we couldn't predict what type of browser a researcher might be
using when they came to our site, we couldn't be sure it would display
the way we wanted it to.  That's less of a concern now that XML-capable
browsers are becoming more and more common, but still something to keep
in mind.

Caveat: our experience was a couple of years ago and things may be
different now!

Michele

>From: Encoded Archival Description List [mailto:[log in to unmask]] On
>Behalf Of Kathryn Stine
>Sent: Thursday, October 02, 2008 9:21 AM
>To: [log in to unmask]
>Subject: EAD and CONTENTdm
>
>Hello,
>
>I wonder if anyone on the list has experience they'd be able to
>share about using CONTENTdm to deliver finding aids. I've seen a
>number of options for doing this, including using CONTENTdm to
>deliver either PDFs or html pages of finding aids.
>
>My understanding, though, is that CONTENTdm should be able to import
>and deliver EAD xml files, providing a search interface that will
>allow users to search through content in each of the EAD elements.
>Has anyone had success in doing this?
>
>Thanks for any insights!
>
>Kathryn
>
>
>    Kathryn Stine
>    Archivist, Special Collections Department
>    University Library
>    University of Illinois at Chicago
>    801 S. Morgan, M/C 234
>    Chicago, Illinois 60607
>
>