Thank you for this, it did exactly what I wanted, and was a lot easier
than through the themes. It also gave me a hint for other changes I can
make through here, instead of long lines of code in my themes :)
 
 
 
Thanks
Jennifer
 

Jennifer Whalan
Systems Support Officer
Innovation & Access, Northern Territory Library
Department of Natural Resources, Environment, The Arts and Sport
Northern Territory Government 

Phone:  (08) 8922 0757
Fax:    (08) 8922 0722
Email:  [email protected] <mailto:[email protected]> 
Web:    www.ntl.nt.gov.au <http://www.ntl.nt.gov.au/> 

The information contained in this message and any attachments may be
confidential information and may be subject to legal privilege, public
interest or legal profession privilege. If you are not the intended
recipient, any use, disclosure or copying of this message or any
attachments is unauthorised. If you have received this document in
error, please advise the sender. No representation or warranty is given
that attached files are free from viruses or other defects. The
recipient assumes all responsibility for any loss or damage resulting
directly or indirectly from the use of any attached files.

 

________________________________

From: Kim Shepherd [mailto:[email protected]] 
Sent: Monday, 15 June 2009 2:08 PM
To: Jennifer Whalan; [email protected]
Subject: RE: [Dspace-tech] Removing Community-List from front page -
XMLUI



Hi Jennifer,

 

The best way would be to override the ArtifactBrowser aspect - took me a
while to figure out the correct paths while I was testing this live, but
I imagine (hope!) if you put a custom sitemap.xmap into
[dspace-src]/dspace/modules/xmlui/src/main/resources/aspects/ArtifactBro
wser/sitemap.xmap, then rebuild, your overridden sitemap will be used.

 

(FWIW, the quick way to test this live is to make a
WEB-INF/classes/aspects/ArtifactBrowser directory beneath your main
xmlui webapp directory, copy the original ArtifactBrowser sitemap.xmap
(you can find it in your dspace-xmlui-api source tree) into this
directory and make changes from there)

 

Once you've got everything copied over and ready to customise, you can
take a look at the file itself, and when you get to:

 

<map:match pattern="">

 

Then you're matching the homepage.

You'll see that within this pattern match, the CommunityBrowser
transform is called:

 

<map:transform type="CommunityBrowser">

       <map:parameter name="depth" value="1"/>

 </map:transform>

 

You can just remove this map:transform block altogether, and the
resulting homepage won't display the community list.

 

I'm just re-reading this now and it's pretty messy to follow, sorry...
just reply if you get stuck.

 

Cheers,

 

Kim

 

 

From: Jennifer Whalan [mailto:[email protected]] 
Sent: Monday, 15 June 2009 1:33 p.m.
To: [email protected]
Subject: [Dspace-tech] Removing Community-List from front page - XMLUI

 

To any XSLT experts out there. Or at least anyone who is better than me.

 

 

We are preparing our test instance of 1.5.2 to go live, and one of the
requirements is that the list of communities is removed from the front
page. In the main theme I started off with

 

 <xsl:template match="/dri:document/dri:body/dri:d...@id =
'aspect.artifactbrowser.CommunityBrowser.div.comunity-browser']" />

 

but then found out that the community-list page displays the list of
communities/collections in the same way.

 

So I need to remove from the front page, but keep on the community-list
page.

 

The next bit I tried was:

 

 <xsl:template name="removeCommunity">
  <xsl:choose>
   <xsl:when
test="string(/dri:document/dri:meta/dri:pageMeta/dri:metada...@qualifier
='URI']) != 'community-list'">
    <xsl:apply-templates select="/dri:document/dri:body/dri:d...@id =
'aspect.artifactbrowser.CommunityBrowser.div.comunity-browser']"
mode="hide" />
    
   </xsl:when>
   <xsl:otherwise>
    <xsl:apply-templates select="/dri:document/dri:body/dri:d...@id =
'aspect.artifactbrowser.CommunityBrowser.div.comunity-browser']" />
   </xsl:otherwise>
  </xsl:choose>
 </xsl:template>
 
 <xsl:template
match="/dri:document/dri:body/dri:d...@id='aspect.artifactbrowser.Commun
ityBrowser.div.comunity-browser']" mode="hide" priority="1" />

 

 

Which actually shows both of them (though I thought it would do the
opposite). It seems (to me) that the only way to hide it on the front
page is to make a template to match comunity-browser, but that would
still hide it everywhere else.

 

If anyone knows how I can solve this problem in XSLT could you please
let me know? Otherwise if there's a way to do this in the source?

 

 

Thanks

Jennifer Whalan

 

 

 

Jennifer Whalan
Systems Support Officer
Innovation & Access, Northern Territory Library
Department of Natural Resources, Environment, The Arts and Sport
Northern Territory Government 

Phone:  (08) 8922 0757
Fax:    (08) 8922 0722
Email:  [email protected] <mailto:[email protected]> 
Web:    www.ntl.nt.gov.au <http://www.ntl.nt.gov.au/> 

The information contained in this message and any attachments may be
confidential information and may be subject to legal privilege, public
interest or legal profession privilege. If you are not the intended
recipient, any use, disclosure or copying of this message or any
attachments is unauthorised. If you have received this document in
error, please advise the sender. No representation or warranty is given
that attached files are free from viruses or other defects. The
recipient assumes all responsibility for any loss or damage resulting
directly or indirectly from the use of any attached files.

 

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to