...
- prepending DRI/ to the beginning of the page url but after the context path, i.e.
http://manakin<manakin-urlurl>/DRI/search
- appending the XML parameter to the end of the URL, i.e.
http://manakin<manakin-urlurl>/search?XMLorhttp://manakin<manakin-urlurl>/search?query=texas&page=2&XML
The only difference between these two methods is the whether the XML is passed through the Internationalization (i18n) transformer. The first method returns raw DRI XML with <i18n:text> tags still unprocessed, while the second one resolves them to their corresponding string values. In general, using the DRI/ directive allows for easier navigation though the DRI document, although the ?XML is still useful when access to the raw DRI is needed.
...
| Code Block |
|---|
<!-- Add general page metadata -->
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="lib/css/reset.css"/>
<map:parameter name="stylesheet.screen#2" value="lib/css/style.css"/>
<map:parameter name="javascript#1" value="lib/jquery-1.2.min.js"/>
<map:parameter name="javascript#2" value="lib/tamu-menus.js"/>
<map:parameter name="theme.path" value="\{global:theme-path\}"/>
<map:parameter name="theme.name" value="\{global:theme-name\}"/>
</map:transform>
<!-- Add browser-specific stuff -->
<map:select type="browser">
<map:when test="explorer6">
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="lib/css/style-ie6.css"/>
</map:transform>
</map:when>
<map:when test="explorer7">
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="lib/css/style-ie7.css"/>
</map:transform>
</map:when>
<map:when test="safari2">
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="lib/css/style-safari2.css"/>
</map:transform>
</map:when>
<map:when test="safari3">
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="lib/css/style-safari3.css"/>
</map:transform>
</map:when>
</map:select>
|
...
| Code Block |
|---|
<map:select type="browser">
<map:when test="lynx">
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="../style.css"/>
<map:parameter name="stylesheet.screen#2" value="style-lynx.css"/>
<map:parameter name="theme.path" value="\{global:theme-path\}"/>
<map:parameter name="theme.name" value="\{global:theme-name\}"/>
</map:transform>
</map:when>
<map:otherwise>
<map:transform type="IncludePageMeta">
<map:parameter name="stylesheet.screen#1" value="../style.css"/>
<map:parameter name="theme.path" value="\{global:theme-path\}"/>
<map:parameter name="theme.name" value="\{global:theme-name\}"/>
</map:transform>
</map:otherwise>
</map:select>
<map:transform src="../main.xsl"/>
|
...
- The following setting in dspace.cfg must be set to true: xmlui.theme.allowoverrides=true
- The "themepath" value should be appended to the end of the url, i.e.
http://manakin<manakin-urlurl>/search?themepath=Theme1/ or http://manakin<manakin-urlurl>/search?themepath=CompundTheme/SubTheme1/
Processing an external XML document
...
<xsl:template match="dri:list">Wiki Markup {{<xsl:template match="dri:list\[1\]" priority="2">}}
Wiki Markup {{<xsl:template match="dri:list\[count(child:.*)=0\]" priority="3">}}
and so on to any level of complexity. Furthermore, this relationship is not necessarily symmetrical; in the example above a template that matches only empty lists will only trigger for empty lists, but a template that matches all lists can match all empty lists as well. This creates an ambiguity that must be resolved by the XSL processor. To that end templates are prioritized as follows:
...