The EAD Cookbook stylesheets do use the XSLT generate-id() to link the table of contents with the body of the document.
I disagree with Michele's assertion that this is problematic for the table of contents. The link in the table of contents references the id that has been generated for the portion of the document to which it is being linked. This code in the table of contents will always generate the same id value at both the source and target because the former merely references the latter. Being part of a <xsl:for-each> loop. it is always relative.
Internal links are admittedly more problematic and explict @id attributes at the link target are clearly the most reliable option.
However, here's a code challenge for someone who wants to try a more hands-off approach.
In the case of linking <c01> titles in an <arrangement> statement with their descriptions in <dsc>, could one use the <xsl:number> feature to number both the titles in <arrangement> and the <c01> elements in <dsc> and then use the generate-id() to link them based on the number assigned? This assumes of course that the titles are listed in <arrangment> in the same order as they appear in <dsc>.
This would be a more sophisticated approach than the one currently employed in the Cookbook which simply assigns numbers.
<xsl:template match="archdesc/scopecontent/arrangement/list/item | archdesc/arrangement/list/item">
In the end, these all depend on stylesheet support.
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
Sent: Saturday, April 14, 2007 11:03 AM
To: [log in to unmask]
Subject: Re: Table of Contents links to c01 and c02 tags
Hi Jordon --
It's a two-part process; you didn't mention which part you need, so
here's both. Part 1 is making sure that the c01s and c02s in the body
of the inventory have an ID to link to; this is done in the dsc# style
sheet. Part 2 is adding a listing in the TOC that links to the correct
IDs; that's done in the eadcbs# style sheet. IDs can be fixed (via use
of the id attribute in EAD) or generated during transformation; the
former is obviously more reliable.
The code for part 1, inserting the ID in the body of the inventory
resides in whatever dsc style sheet you're using and looks something
like this for fixed IDs:
(blah blah, usually unittitle goes here)
Part 2, putting the listing in the TOC, is done something like so for
<xsl:for-each select="archdesc/dsc/c01[@level='series' or
@level='subseries'] or archdesc/dsc/c02[@level='subseries']">
(blah blah, usually unittitle goes here)
There is a generate-id function that will create ids during transformation:
but it can be problematic for a couple of reasons. First, since the IDs
are recreated every time you run a transformation you don't know what
they'll be at the time you're creating the TOC. Second, if you have any
internal links to c01s or c02s, you won't know what href to use in your
EAD since the IDs haven't yet been generated and may be different each time.
If you're really set on generating IDs during transformation, a more
reliable way is to generate IDs by counting the number of c01s/c02s,
something like this:
<xsl:number count="c01" from="dsc"/>
This will work easily for c01s since there's only one set of c01 tags at
the top level, but you'd have to somehow differentiate between the c02s
that are children of different c01s.
Caveat: if you're employing that feature that automatically links lists
in the <arrangement> element to their respective inventory items (in
eadcbs9 it's the section that begins "<!-- The next three templates
format a list within an arrangement..."), that uses the "count" function
and switching to the fixed-id method will require repairs to that feature.
Jordon Steele wrote:
> Does anyone know what code to use to create links between series and
> subseries titles in the table of contents to the corresponding c01 and
> c02 tags in the body of the finding aid? I think I tweaked this part of
> the code on my stylesheet a little too much, and I forgot what the
> original code was!
> If it helps, I'm using a customized version of eadcbs9.xsl as my primary
> Jordon Steele
> Biddle Law Library
> University of Pennsylvania Law School
> (215) 898-5011