I went back in and modified the XSLT that was processing the given names to now read:

<xsl:variable name="ref_id">
    <xsl:value-of select="@ID" />
</xsl:variable>
...
<xsl:for-each select="name">
INSERT INTO authors (id, ref_id, given, family, role)
VALUES(
    UUID(),
    <!--(SELECT id FROM citations ORDER BY added desc limit 1),-->
    '<xsl:value-of select="$ref_id"/>',
    <xsl:for-each select=".">
        '<xsl:for-each select="namePart[@type='given']">
            <xsl:value-of select="."/>
            <xsl:text> </xsl:text>
        </xsl:for-each>',

        '<xsl:value-of select="namePart[@type='family']"/>',
        '<xsl:value-of select="role/roleTerm"/>'
    </xsl:for-each>
    );
</xsl:for-each>

It looked like the SQL to grab the last item didn’t always return a record for whatever reason (a locking issue?). Since there was already a key in the field, I just switched over to use that in the inserts. Still need to go through and regularize the fields so MySQL isn’t attempting to pull a foreign key index on a variable width field, but this is an update to yesterday’s code.

I ran into a bit of a situation that was really blowing my mind. I have a rather large XML file (around 20,000+ lines) marked up in TEI that I wanted to do some transformations on (a day book and ledger from the 1850s). Essentially the code follows the format

What I wanted to accomplish was group all this together in separate divs for HTML output (ok, I actually need to write each page to its own file, but this is pretty much just one more step).

I just could not find a way to group this info this way using XSLT 1 without wrapping each page within its own div structure. I didn’t really want to go back and do this, so I asked the TEI-L list. David Sewell pinged me back with some XQuery code that recursively recalls the document structure for a given node.

He also mentioned that it would be pretty easy to write an XSLT 2 transformation that groups these nodes together. I did a little bit of digging and came up with

This transformed the pages to what I was wanting

The XSLT processor for ColdFusion doesn’t support XSLT 2.0 (it’s still a draft spec). However, Saxon does (specifically Saxon 8). For more on doing XSLT transformations, see XSLT 2.0 in ColdFusion. ]]> http://www.liquidfoot.com/2006/08/23/real-life-xslt-20-transformations/feed/ 0