Print

Print


It looks like to me that this code (using <a> rahter than <img>) would embed a link to to an image into the finding aid rather than actually causing the image to appear automatically.    Which you use would depend on the results you want to achieve.

The code below, of course, would have to be embedded into one or more templates rather than functioning independently of the formatting for a given level.   

Fun stuff.

Michael



-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
Amy McCrory
Sent: Friday, March 03, 2006 10:04 AM
To: [log in to unmask]
Subject: dao XSLT


Some basic code for outputting <dao> elements to HTML was published 
in 2001, and should probably be considered the starting point for 
anyone trying to do this.  The citation to the article is:

Prom, Christopher J.  "Extending the capabilities of the EAD 
cookbook."  OCLC Systems & Services, v. 17, n. 2 (2001), p. 89-95.

An adaptation, done by OSU's much-missed Web librarian, was done this 
way, reflecting the <daogrp>'s location inside a <c02><did>:

<xsl:for-each select="../parent::*/daogrp/daoloc">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of select="@href" />
</xsl:attribute>
<xsl:apply-templates />
<br/>
</xsl:element>
</xsl:for-each>

As Michael Rush and Michael Fox have explained, changes have to be 
made depending on how the EAD is structured, and what the desired 
output would look like.  Fox's example used an <xsl:template> rather 
than an <xsl:for-each>; either of these approaches could make sense 
depending on the context.

Anyone with useful variations on the basic instructions might want to 
post them to this list.  I think they'd get a lot of use.

Amy


----------------------------------------------------------------------
Amy McCrory
Digital Imaging Specialist, Preservation Department
228 Thompson Library, 1858 Neil Avenue
The Ohio State University Libraries
Columbus, OH 43210
(614) 292-8647