The source model seems inordinately complex.
On Fri, Jul 11, 2014 at 10:53 AM, Matthew Sherman <[log in to unmask]>
wrote:
> I guess it is the "doc:element/doc:element/doc:field" thing that is mostly
> what it throwing me.
>
>
> On Fri, Jul 11, 2014 at 10:52 AM, Dunn, Katie <[log in to unmask]> wrote:
>
> > Hi Matt,
> >
> > The W3C Recommendation for XPath has some good explanation and examples
> > for abbreviated XPath syntax here: http://www.w3.org/TR/xpath-30/#abbrev
> >
> > Katie
> >
> > -----Original Message-----
> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> > Matthew Sherman
> > Sent: Friday, July 11, 2014 10:39 AM
> > To: [log in to unmask]
> > Subject: [CODE4LIB] OAI Crosswalk XSLT
> >
> > Hi Code4Lib folks,
> >
> > I have a question for those of you who have worked with OAI-PMH. I am
> > currently editing our DSpace OAI crosswalk to include a few custom
> metadata
> > field that exist in our repository for publication information and port
> > them into a more standard format. The problem I am running into is the
> > select statements they use are not the typical XPath statements I am used
> > to. For example:
> >
> > <xsl:for-each
> >
> >
> select="doc:metadata/doc:element[@name='dc']/doc:element[@name='type']/doc:element/doc:element/doc:field[@name='value']">
> > <dc:type><xsl:value-of select="." /></dc:type> </xsl:for-each>
> >
> > I know what the "." does, but the other select statement is a bit foreign
> > to me. So my question is, does anyone know of some reference material
> that
> > can help me make sense of this select? I need to understand what it is
> > doing so I can make my own. Thanks for any insight you can provide.
> >
> > Matt Sherman
> >
>
|