Hi Standa,

I'm curious as to why you have decided to switch from hyperlinking the container title to instead adding "customizable linking text"?  Aside from the default "view item," what other examples of text-links are going to be added?

Also, I really like how the fronts of the folders have also been digitized in the Joseph Roth collection.  Thanks for pointing out these examples,

Mark Custer

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Stanislav Pejsa
Sent: Tuesday, January 19, 2010 10:20 PM
To: [log in to unmask]
Subject: Re: Adding EAD to the 'layer of discovery'?

Hi Michele,
The Center for Jewish History is a consortium of archives and special libraries, and at this moment we are in a transition phase  when some Partners are digitizing their complete collections like the one of Joseph Roth. However, the pace of transition is uneven. We are also working on new stylesheet that should take these digitization efforts into account. The Roth's finding aid is stretching the old stylesheet a bit.

Unfortunately, we have not found a way yet in DigiTool to link back to the finding aid, but the new stylesheet will open a new window for the digital content, so that users won't lose the finding aid when they click on the object. Furthermore, the stylesheet will provide a linking text that will be customizable, so the title won't be the hyperlinked. The customizable linking text can appear either in the attribute title of the dao element or in the daodesc/p.

Advanced searching on EAD tags would be great, but it is the processed finding aid in the plain text that's indexed.

This is the snippet we use as an example for encoding links to digital objects (mainly) in DigiTool 

<c02 level="file"> 
<container type="box">1</container>
<container type="folder">5</container> 
<dao actuate="onrequest" show="new" href="xxxxxx" role="dgtl" linktype="simple" />

The href attribute contains a pid (permanent identifier in DigiTool) and the attribute role will invoke a parameter that contains a full path to the resource (in that way we believe we may minimize typos - we could also simply use the full path in the href attribute). Since there is no attribute title or subelement daodesc in this example the stylesheet will provide linking text "View item". The stylesheet, however, is still work in progress.

The following finding aid is the test example:

Best, Standa

 -----Original Message-----
From: Michele R Combs [mailto:[log in to unmask]] 
Sent: Tuesday, 19 January, 2010 11:39
To: [log in to unmask]
Subject: Re: [EAD] Adding EAD to the 'layer of discovery'?

Hi Standa -
This is *very* nice.  Some follow-up questions: If I go into an EAD finding aid, like the Roth one, then click on a link to a digitized item and view it, how do I then get back to the EAD?  Is Digitool handling the rendering and display of the EAD finding aid as well as the indexing/searching?  Does it allow advanced searching based on EAD tags (e.g. date, origination, persname) ?  Would you mind sharing the raw EAD so I can see how the digital objects are encoded?
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Stanislav Pejsa
Sent: Sunday, January 17, 2010 10:03 PM
To: [log in to unmask]
Subject: Re: Adding EAD to the 'layer of discovery'?
Sorry for the late answer. DigiTool (ExLIbris) also makes it possible to index a complete finding aid. The mechanism is the same as others mentioned, DigiTool extracts a text from the xml tags and the plain text file then is indexed and serves for retrieval. 
Here at The Center for Jewish History, the full-text extraction routine is used only for those finding aids that have a container list that is not encoded in the marc record. We are just in the process of converting all collection level records in MARC into EAD. Naturally, it would not make any sense to run a full-text on these finding aids, as they are identical with the marc record ingested into the DigiTool and indexed there as well.
Have a look at:
and search for Albania - one of the retrieved objects should be the Joseph Roth Collection. Albania is not mention in the record for the collection, but appears several times in the container list.
Standa Pejša, Center for Jewish History 
 -----Original Message-----
From: Custer, Mark [mailto:[log in to unmask]] 
Sent: Tuesday, 22 December, 2009 15:23
To: [log in to unmask]
Subject: [EAD] Adding EAD to the 'layer of discovery'?
I'm curious if anyone on the list has experience with adding their EAD documents into a larger discovery system?  
Here are two examples of what  I mean:
*         Triangle Research Library Network now indexes (and displays) entire EAD documents.  
Example (in which I've restricted my results to "archival materials" and entered "ammons" as my keyword):
*         University of Chicago library's implementation of AquaBrowser seems to index entire EAD documents.  
Example (in which I've searched for "American Automobile Brief History", quotes included, and where the first 3 results returned should be for archival finding aids): 
So, this leads me to three questions in particular:
1.       Can you point me to any other online examples of "discovery tools" that are ingesting entire EAD documents?  Summon, Encore, Primo, Blacklight, etc.??? (but, again, I'm not asking about OPACS that only search a MARC surrogate of the EAD) 
2.       For those of you that are including the entire EAD in your library's discovery tool, did you already have surrogate MARC records for those collections in your catalog?  If so, how are you dealing with those now that you're adding the EAD?
3.       What do you think of whole retrieval experience (advanced search options, facets, incorporation into the relevancy algorithm, etc.)?
Thanks in advance for any and all advice and/or other examples that might be out there,
Mark Custer