Hi Jose,
I believe this is not a problem and that the only way to influence
processing of mets or dim based on DRI is to save state in a variable
when in DRI and use the variable in mets/dim. Consider this:
<!-- here we are processing DRI -->
<xsl:variable name='container'><xsl:value-of
select="/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'
and @qualifier='container']"/></xsl:variable>
<!-- Generate the info about the item from the metadata section -->
<xsl:template match="dim:dim" mode="itemSummaryView-DIM">
<!-- here we are processing DIM -->
<table class="ds-includeSet-table">
<xsl:choose>
<xsl:when test="$container = 'hdl:123456789/18574'">
<xsl:call-template
name="itemSummaryView-DIM-fields-collection-specific-fields" />
</xsl:when>
<xsl:otherwise>
<xsl:call-template name="itemSummaryView-DIM-fields" />
</xsl:otherwise>
</xsl:choose>
</table>
</xsl:template>
I haven't run into a problem with this. That being said, if anyone has
an alternative suggestion, I'd be interested to hear it.
Regards,
~~helix84
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
