Thanks, Brian. Turns out it had nothing to do with that element at all. I had a
problem further up in my stylesheet.
Jason
Jason Stirnaman
Biomedical Librarian, Digital Projects
A.R. Dykes Library, University of Kansas Medical Center
jstirna...@kumc.edu
913-588-7319
On 9/26/2011 at 11:16 AM, in message
4e8050f202010010c...@gwdomain.unm.edu, Brian Freels-Stendel
bfre...@unm.edu wrote:
Hi Jason,
It looks like your match should work (although it should only be necessary to
specify the mdschema if the element name also appears in other schemas.) I'm
wondering about the value-of select, though. Does anything come out if you use
'select=.'? Or, perhaps try a different form and use 'xsl:copy-of
select=./node()/'? (I'm not incredible at XSLT, but I'm not seeing where
'present element' is being supplied in that select)
B--
On 9/23/2011 at 3:54 PM, in message
4e7cb9d9020501558...@smtpout.kumc.edu, Jason Stirnaman
jstirna...@kumc.edu wrote:
I have a XSLT crosswalk. How do I access a metadata field from a different
schema in my stylesheet? For example, Here's my non-DC field in mets.xml:
dim:field element=spage language=en_US mdschema=rft1/dim:field
However, in my stylesheet applying the following template doesn't output
anything:
xsl:template match=dim:field[@element='spage' AND @mdschema='rft']
xsl:element name=FirstPage
xsl:value-of select=concat('E',text())/
/xsl:element
/xsl:template
Thanks,
Jason
Jason Stirnaman
Biomedical Librarian, Digital Projects
A.R. Dykes Library, University of Kansas Medical Center
jstirna...@kumc.edu
913-588-7319
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
