DSpace Techies -
I'm looking for some assistance with understanding (primarily)
Manakin's DRI.
Here's a simple example task:
Changing the base URI for css stylesheets.
Current location is: {theme-name}/lib/{stylesheet-name}.css
Desired location is: {theme-name}/css/{stylesheet-name}.css
The template to overwrite is: "buildHead"
Here's the relevant portion of the XSLT:
<xsl:attribute name="href">
<xsl:value-of select="/dri:document/dri:meta/dri:pageMeta/
dri:metada...@element='contextPath'][not(@qualifier)]"/>
<xsl:text>/themes/</xsl:text>
<xsl:value-of select="/dri:document/dri:meta/dri:pageMeta/
dri:metada...@element='theme']...@qualifier='path']"/>
<xsl:text>/</xsl:text>
<xsl:value-of select="."/>
</xsl:attribute>
Now this *could* be done by something as simple as removing the nested
tags from the <xsl:attribute/> tag, but I'd prefer to do in a manner
that would seem more proper - tapping into the DRI and perhaps even
modifying it's content slightly.
The Problem:
Directing my browser to "http://{hostname}.{server}.{extension}/
{dspace-instance}/DRI/" does yield the raw xml for the DRI, but the
document -> meta -> pageMeta -> theme element doesn't seem to exist.
At least in the browser's output:
<pageMeta>
<metadata element="contextPath"/>
<metadata element="request" qualifier="queryString"/>
<metadata element="request" qualifier="scheme">http</metadata>
<metadata element="request" qualifier="serverPort">8080</metadata>
<metadata element="request"
qualifier="serverName">dld.library.gatech.edu</metadata>
<metadata element="request" qualifier="URI"/>
<metadata element="search" qualifier="simpleURL">/search</metadata>
<metadata element="search" qualifier="advancedURL">/advanced-search</
metadata>
<metadata element="search" qualifier="queryField">query</metadata>
<metadata element="page" qualifier="contactURL">/contact</metadata>
<metadata element="page" qualifier="feedbackURL">/feedback</metadata>
<metadata element="title">DSpace Home</metadata>
<metadata element="feed" qualifier="rss+xml">/feed/rss_1.0/site</
metadata>
<metadata element="feed" qualifier="rss+xml">/feed/rss_2.0/site</
metadata>
<trail target="">DSpace Home</trail>
</pageMeta>
Questions:
1) Why does the DRI in my browser seem to be incomplete? Is there
something I can do to have it show a more complete set of data? Or is
this just a limitation imposed by when the content gets generated from
the pipelines?
2) How would one tap into / modify the existing DRI? Or might this
just be a bad idea even for small changes such as the posted example?
3) What suggestions might you offer as a best solution for
accomplishing tasks that involve the XSLT and DRI for presentation
level changes?
Any tips, hints, or suggestions would definitely be appreciated
Many Thanks!
- Patrick Etienne
---
Patrick K. Étienne
Systems Analyst
Digital Library Development
Library and Information Center
Georgia Institute of Technology
email: [email protected]
phone: 404.385.8121
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
