This is almost completely unrelated to your original question, Michele, but since you mentioned taking up “less space” (in response to Deena’s example that includes an html table in the output) – and since I’m just now attempting to provide a new way to output EAD tables from my stylesheet – I thought I’d go ahead and share this experiment:

 

Basically, I needed to use of some EAD <table> tags this week, and I wanted to update our online display in the process.  So, I’m now outputting any EAD tables that have a <thead> into a fixed-height HTML table with a fixed header.  Here’s an example:

 

http://digital.lib.ecu.edu/special/ead/view.aspx?q=%22list%20of%20officers%22&id=0409#histnote

(scroll down to the end of this section, where there’s a table labeled “List of Officers”, which should be highlighted in red)

 

For what you’re talking about, though, I really like the example given by Susan McDonald.  What’s more, the Emory finding aids look amazing! (and I wonder if Sharpdot worked on this with the library? – and, if so, are there any articles or presentations documenting that process?). 

 

 

Mark Custer

 

 

From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
Sent: Friday, May 21, 2010 11:52 AM
To: [log in to unmask]
Subject: Re: Index to correspondence?

 

I like your display of the index – takes up much less space than our nested lists.  Thanks!

 

Michele

 

From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Deena Schwimmer
Sent: Friday, May 21, 2010 9:46 AM
To: [log in to unmask]
Subject: Re: Index to correspondence?

 

Michele,

We do the same thing as Susan describes below.  For example,  http://libfindaids.yu.edu:8082/xtf/view?docId=ead/henrymorais/henrymorais.xml

As I read the description of <ref> in the tag library, it can be used to provide a dynamic link, or to direct the reader from a descriptive note to a specific component.  

 

Deena

 

________

Deena Schwimmer, Archivist

Yeshiva University Archives

mail: 500 W. 185th St., New York, NY 10033 / interoffice: MGL 602

email: [log in to unmask] / phone: (212) 960-5451 / fax: (212) 960-0066

 

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
Sent: Friday, May 21, 2010 9:00 AM
To: [log in to unmask]
Subject: Re: Index to correspondence?

 

So you use the ref elements but without a target attribute?  For some reason that never occurred to me; I guess I had it in my head that since ref is a linking attribute it had to have a target, so I didn't consider it.  Interesting possibility, thanks.

 

Michele

 

-----Original Message-----

From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of McDonald, Susan Potts

Sent: Friday, May 21, 2010 8:46 AM

To: [log in to unmask]

Subject: Re: Index to correspondence?

 

Michelle:

 

We have several such indexes at Emory relating to our literary collections.  The indexes are simply part of the encoded finding aid and are located at the end of the <c> components.  Here's some sample coding:

 

<index>

                <head>Index of Selected Correspondents</head>

                <note>

                  <p>This index, which relates to the correspondence in Series 1, covers

                         letters from 1973-1999.</p>

                </note>

                <indexentry>

                  <persname>Batten, Guinn</persname>

                  <ptrgrp>

                         <ref>1995 July 29, ALS, 1p.</ref>

                         <ref>undated APCS [August 7]</ref>

                         <ref>1996 September 23, TLS, 1p.</ref>

                         <ref>1999 May 22, TLS, 2pp.</ref>

                         <ref>CC to GB: 1999 June 1, TLS, pp. 2</ref>

                         <ref>1999 August 4, TLS, 3pp.</ref>

                  </ptrgrp>

                </indexentry>

 

You can look at the finding aid at: http://marbl.library.emory.edu/findingaids/browse_results?q=findingaids/content&id=carson746_107393

 

 

Susan