LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


EAD@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  April 2007

EAD April 2007

Subject:

Re: Table of Contents links to c01 and c02 tags

From:

Mike Ferrando <[log in to unmask]>

Reply-To:

Encoded Archival Description List <[log in to unmask]>

Date:

Mon, 16 Apr 2007 08:19:28 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (183 lines)

Michael (et al.),
One of the problems I have found using generate-id(), is that it is dependent on the XML source document when it generates unique strings. Further, the id string produced is dependent on either the XPATH statement given to the function, or if left empty the function returns the unique id for the context node of the XML source document.

The problem is that in most cases, I am generating many HTML (or whatever markup) elements in my output dependent on one or from the context of one node in my XML source (an EAD component for example).

Therefore, the generate-id() function is creating unqiue ids based on the assumption that you will have a 1-to-1 relationship between the XML source nodes and the HTML output (or whatever markup).

The result (depending on how you are writing your XSLT templates handling the XML Source document) can be repeated id values in your output.

Many will avoid this by either writing XPath statements to the unique elements they wish to create ids for, or writing their templates so that the context node of the template will return a unique string every time the template is called.

For myself, I dont' use this function. The reasons are as follows:
1. I don't wish to be constrained when I write my stylesheet to figuring out what the function will do based on how I am transforming the XML Source document. Frankly, I don't  want my output to be directly dependent on the XML Source (that is why I am writing the stylesheet!).
2. I don't want to write XPath statements that target known unique nodes in the XML Source to get a unique id string from the function. I would rather not have to figure out what each EAD document has  or does not have. The purpose of my stylesheet is to crunch may different EAD documents (I have a life already) without previewing each of them. (If the element does not exist, the function returns an empty set.)

So, what is my solution?

There are unique values for every EAD document.

1. total sum of elements (or nodes).
2. eadid (persistent identifier)

These two values can be used to create ids for any EAD document.

1. A global variable can be set in the stylesheet to get a count of all nodes in the EAD document. This value can be used at anyplace in the stylesheet as a base value to create a unique number. (imported stylesheet issues may have to pass params or recount)
2. Other syntax can be used to build this string to readily identify the ID as created by the stylesheet.

Finally, building a TOC is very problematic. The stylesheet writer must face the fact that this is an artificially created list that does not exist in the original EAD code. Therefore, building and creating @IDs must ultimately be dependent on the stylesheet not the source code. Binding the generation of id values on the these unique variables will result in unique ids for any and every EAD document. (Of course not having a eadid persistent identifier will make things rough. You might use the file name instead.)

Note: When you generate TOCs, be sure to remove any @ID attributes from elements that you may bring into the TOC (emph/@id). If you don't, you will have repeated @IDs in your HTML and your links will fail.

Anyway, my two cents.

Mike Ferrando
Library Technician
Library of Congress
Washington, DC
(202) 707-4454

----- Original Message ----
From: "Fox, Michael" <[log in to unmask]>
To: [log in to unmask]
Sent: Monday, April 16, 2007 10:10:45 AM
Subject: Re: Table of Contents links to c01 and c02 tags

Good morning, 

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.

    <a href="#{generate-id(archdesc/did/head)}">
        <xsl:value-of select="archdesc/did/head"/>
    </a>

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">
        <div style="margin-left:50pt">
            <a>
                <xsl:attribute name="href">#series<xsl:number></xsl:number>
                </xsl:attribute>
                <xsl:apply-templates></xsl:apply-templates>
            </a>
        </div>
    </xsl:template> 

In the end, these all depend on stylesheet support.


Michael Fox

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
MicheleR
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:

    <xsl:if test="@id">
       <a id="{@id}">
          (blah blah, usually unittitle goes here)
       </a>
    </xsl:if>

Part 2, putting the listing in the TOC, is done something like so for 
fixed IDs:

<xsl:for-each select="archdesc/dsc/c01[@level='series' or 
@level='subseries'] or archdesc/dsc/c02[@level='subseries']">
    <p>
       <b>
          <a href="#{@id}">
             (blah blah, usually unittitle goes here)
          </a>
       <b>
    </p>


There is a generate-id function that will create ids during transformation:

<a href="#{generate-id(.)}">

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:attribute name="href">
    <xsl:text>#series</xsl:text>
    <xsl:number count="c01" from="dsc"/>
</xsl:attribute>

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.

Michele

Jordon Steele wrote:
> Hello,
>  
> 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 
> stylesheet.
>  
> Thanks,
>  
> Jordon
>  
> Jordon Steele
> Archivist
> Biddle Law Library
> University of Pennsylvania Law School
> (215) 898-5011
>  




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
December 1995

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager