Stephanie, another approach is to use a parameter in the ROLE attribute
that maps to a specific path in your XSLT stylesheet. That way, you
could point to various paths and not be limited to a single path,
especially if you are linking to something other than an image. I use a
separate XSLT "module" that contains the mappings for the role terms.
This is also useful when you have a "development" area that is separate
from your "production" area and the two paths are different. The
"development" area stylesheet module may point to an UNC path such as
\\myserver\path\etc., but the "production" area stylesheet may point to
a path on your webserver. If you ever need to change these paths, all
you need to do is to update the paths in the "mappings" module for that
particular defined ROLE parameter.
Another tip is to use CSS declarations within the ALTRENDER attribute to
take care of things like alignment, borders, etc. This gives you the
flexibility to use a whole multitude of CSS properties which you would
just string together, separating each declaration with a semi-colon. In
your stylesheet, the ALTRENDER attribute would be mapped to the STYLE
attribute if your are using CSS declarations.
red;border-width:10px;" href="myimage.jpg" role="www-images"
arcrole="image/jpeg" title="This is my alt text" show="embed"
<img src="myimage.jpg" alt="This is my alt text" title="This is my alt
Since the XSLT is too cumbersome to include here, contact me offlist if
you want additional information.
Stephanie Ashley wrote:
> Would anyone be willing to share their xml encoding for an illustrative
> image on a finding aid" title page" (using <extptr> rather than <dao>) and
> the corresponding part of their xsl stylesheet? We're using a stylesheet
> adapted from the Cookbook but my xsl skills are very rudimentary and I
> didn't do the original adaptation, so tend to be able to make further
> modifications only when I have examples to work with.
> Stephanie Ashley
> Archives of American Art
> Smithsonian Institution