Re: [Dspace-tech] change to mirage.

2012-04-18 Thread Blanco, Jose
To: Blanco, Jose Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] change to mirage. 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

Re: [Dspace-tech] change to mirage.

2012-04-18 Thread helix84
On Wed, Apr 18, 2012 at 16:20, Blanco, Jose blan...@umich.edu wrote: So I should put my variable where we are processing DRI, but where would that be in the item-view.xsl file?  Or would it be in some other file. It doesn't matter which file (unless you want to override one template with

Re: [Dspace-tech] change to mirage.

2012-04-18 Thread helix84
On Wed, Apr 18, 2012 at 16:49, Blanco, Jose blan...@umich.edu wrote: xsl:variable name='requestcopy'xsl:value-of select=available//xsl:variable This is probably not what you expect. Here you're testing whether the current DRI node is available, i.e. whether you have an available/ element in

[Dspace-tech] change to mirage.

2012-04-17 Thread Blanco, Jose
I'm in mirage and would like to add some logic to xsl:template match=mets:file In item-view.xsl based on a flag I have added to the DRI xml. Is there a way to do this? Is it better to add the flag to the mets xml file? Would that not violate the METs namespace? Thank you! Jose

Re: [Dspace-tech] change to mirage.

2012-04-17 Thread helix84
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