Thanks for pointing this out. I find myself often confused when dealing
with the xsl files, and I think I did not realize that the only data
available inside a template comes from the match made by the template. So
if the match had been more specific for the template, the xsl in the
template could not access entities before that the match, right?
Like say you have
<a><b><c></c></b></a>
and the template match where "/b", you could not get to <a>, right?
Also, one more question, I see that you don't need to give the full path to
get to an entity, like:
<xsl:value-of
select="dim:field[@element='title'][not(@qualifier)][1]/node()"/>
I guess the rule is you indicate the namespace and go straight to the
entity you want, the xsl will grab the first specified entity available.
Right?
Thank you!
Jose
On Wed, Dec 5, 2012 at 10:08 AM, helix84 <[email protected]> wrote:
> On Wed, Dec 5, 2012 at 4:05 PM, Jose Blanco <[email protected]> wrote:
> > so the part where I test to see which short display to use based on
> > collection will not work because it looks at the dri?
>
> Right, I didn't notice that. Use the same trick as I just used - stash
> the value into a variable outside of the dim-processing template and
> use the variable in it.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
