[Dspace-tech] Hiding dark items
We got quite a few queries recently about how we hide dark items from the browse and OAI-PMH views. We've picked our code apart and put the changes online: http://tools.dspace.cam.ac.uk/dark_items.html We hope this will be useful for other people in the DSpace community. Best regards, -- Tom De Mulder td...@cam.ac.uk - Cambridge University Computing Service +44 1223 3 31843 - New Museums Site, Pembroke Street, Cambridge CB2 3QH - 29/07/2011 : The Moon is Waning Crescent (14% of Full) -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Trouble upgrading Solr stats from 1.6.2 to 1.7.1
Wally, Something is clearly wrong with solr, maybe look to make sure your getting a clean build of the war in deployment (IE verify the list of jars is right in WEB-INF/lib and look at your DSpace/solr config compared the original in source. also review you solr pom in your dspace/modules/solr to make sure it's identical to source. Mark On Thursday, July 28, 2011, wally grotophorst wal...@gmu.edu wrote: Trying to sort out a SOLR stats issue that remains after our otherwise successful upgrade from 1.6.2 to 1.7.1 When running 1.6.2, the Solr stats service worked perfectly. Once we upgraded, I see this if I go to http://localhost:8080/solr/admin: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 32 in the jsp file: /admin/index.jsp The method getRequestHandlers() in the type SolrCore is not applicable for the arguments (ClassReplicationHandler) 29:%-- jsp:include page=header.jsp/ --% 30:%-- do a verbatim include so we can use the local vars --% 31:%@include file=header.jsp % 32:%boolean replicationhandler = !core.getRequestHandlers(ReplicationHandler.class).isEmpty();% 33:br clear=all 34:table 35: Stacktrace: org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:423) org.apache.jasper.compiler.Compiler.compile(Compiler.java:317) org.apache.jasper.compiler.Compiler.compile(Compiler.java:295) org.apache.jasper.compiler.Compiler.compile(Compiler.java:282) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:295) org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:60) Does this ring a bell with anyone? The only change we made to solr configuration was adding this line to dspace.cfg: solr.resolver.timeout = 200 I see 1.7.1 added other files that appear to be related to stats (e.g., /dspace/config/dspace-solr-search.cfg) but I haven't touched those... Platform: Mac OSX Server 10.6.8 java version 1.6.0_26 Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) - Wally Wally Grotophorst Associate University Librarian Digital Programs and Systems University Libraries George Mason University Fairfax, Virginia 22030 (703) 993-9005 -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Mark R. Diggory @mire - www.atmire.com 2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010 Esperantolaan 4 - Heverlee 3001 - Belgium -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] from aspect to theme
Mark, I'm pretty much finished with this. I just want to run it by Jim next time we meet, but I do have one question. The Tombstone page shows a - In the area where normally you have links that take you back to where you came from, like DSpace Home Archive Test Area University of Michigan Transportation Research Institute Reports View Item How do I get this to show up? I've tried a couple of things but can't find the mechanism that handles this. Thank you! Jose -Original Message- From: Blanco, Jose [mailto:blan...@umich.edu] Sent: Friday, July 22, 2011 3:15 PM To: Mark Diggory Cc: dspace-tech@lists.sourceforge.net; Mark H. Wood Subject: Re: [Dspace-tech] from aspect to theme Mark, I think I understand your directions. Sorry if I'm being hard headed about this, but I'm hoping that making this change will help me get smarter about Manakin and Cocoon. So, I created the selector. I think it does what is suppose to do. I've changed the sitemap in the ArtifactBrowse as you suggested. BTW, I don't quite understand what the difference is between ArtifactBrowse, BrowseArtifacts, and ViewArtifacts. Can you explain it without too much trouble? Here is a the change to the sitemap file. I think it's what you suggested: map:match type=HandleAuthorizedMatcher pattern=!READ map:select type=WithdrawnSelector map:when test=true map:transform type=TombstoneView/ map:serialize type=xml/ /map:when map:otherwise map:select type=AuthenticatedSelector map:when test=eperson map:transform type=RestrictedItem/ map:serialize/ /map:when map:otherwise map:act type=StartAuthentication map:parameter name=header value=xmlui.ArtifactBrowser.RestrictedItem.auth_header/ map:parameter name=message value=xmlui.ArtifactBrowser.RestrictedItem.auth_message/ /map:act map:serialize/ /map:otherwise /map:select /map:otherwise /map:match Now, I have my new transformer aspect/artifactbrowse/TombstoneView.java, and I'm not exactly sure how to change it. I copied the ItetemViewer.java file to TombsotneView.java, but how do I change the output of the body that is output? What needs to be output so that the themes know what to do? Thank you so much for this help -Jose -Original Message- From: Mark Diggory [mailto:mdigg...@atmire.com] Sent: Friday, July 22, 2011 1:48 PM To: Blanco, Jose Cc: dspace-tech@lists.sourceforge.net; Mark H. Wood Subject: Re: [Dspace-tech] from aspect to theme On Fri, Jul 22, 2011 at 10:28 AM, Blanco, Jose blan...@umich.edu wrote: Mark, I was kind of trying to do this. I started by creating an ItemViewerNew ( transformer ) using the esiting ItemViewer that was already there but modifying as necessary to have the reason for withdraw show up on the short display. According to what you are saying I should be able to create this new ItemViewerNew transformer without ( hopefully ) impacting the theme, but I’m not seeing it. Don’t I need a new theme to put the reason code just above where the bitstreams are listed, and how do I eliminate the capability to click on the link that lets you go to the bitstream. Not if you use the ArtifactBrowser aspect to generate the message, basically, your writing the DRI elements in Java rather than looking up the METS doc in XML/XSLT calls. You would be doing something like: Item item = (Item) HandleManager.getObject(handle) DCValue[] values = item.getMetadata(….). and then creating a DRI div to hold the message you retrieved. -- What I am proposing eliminates your working in the theming layer and creating a separate view for rendering the Tombstone that is not subject to the complexities your finding in the ItemViewer. For this you would be doing the following: a.) Creating a Transformer and adding DRI sections in its body method b.) Looking up the DSpace Item via the provided handle. c.) Rendering the message by getting the metadata out of the item for the view that is of interest in this case. This would be the simplest approach to rendering a view and would be useful in the next release. You would add: 1.) TombstoneView.java as a transformer 2.) Add a section before the restricted sections in ArtifactBrowser site maps. 3.) Write a WithdrawnSelector that will allow the site map to have conditional logic to determine if the item is withdrawn or not. 4.) Wrap the following section with that selector so that you can execute the WithdrawnView on the handle prior to the restricted view being evaluated. map:select type=AuthenticatedSelector map:when test=eperson map:transform type=RestrictedItem/
Re: [Dspace-tech] Batch metadata corrections question: does anyone know why the limit is set to just 20 items at a time? AND: question about regular recompiling
Thank you, Peter, Stuart, Andrea, Alex - So it sounds like it comes down to how much RAM is available on our server. We're going to try 1000, and see how it goes, as we are still on a development server for just this kind of reason. We are looking at correcting a very large batch of records (retrospective ETDs) before we go live, so this is kind of exceptional..but looking forward, I can see we'll have to be correcting/recompiling regularly. I'm still kind of new, so if anyone has any advice/warnings about doing regular batch corrections as a regular thing, I'd be glad to hear it. How do you handle updates and recompiling? Quarterly? After hours? Thanks everyone, Irene Berry, MLIS Digital Services Librarian Dudley Knox Library, Naval Postgraduate School -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] remove metadata elements from SWORD deposited item
Hi all, I wanted to find out if there is a way to remove a metadata element from the SWORD deposit? I have the following scenario: An item from a source DSpace instance is getting SWORD deposited into another target DSpace instance. So, when the item is deposited into the target DSpace repo, I see two different Handle URI in dc.identifier.uri, one from the source DSpace and the other from the target DSpace. I would like to remove the Handle assigned by the source DSpace and just keep the one assigned by the target. Has anyone run into this issue? If so, any workarounds to this issue? Thanks. Diwakar Timilsina Systems Analyst, UITS University of Arkansas, Fayetteville Email: diwa...@uark.edumailto:diwa...@uark.edu Phone: 479.575.6160 -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Pre-determined Handle? for Batch ingestion
We have some records has pre-determined identifiers for ETDs (e.g. azu_etd_11015). These records are also loaded to our catalog. We use batch ingestion for Both Catalog and DSpace. Are there anyone who pre-set handles for Batch ingestion for DSpace? In other words, if I can have pre-determined handles such as http://hdl.handle.net/1721.123/azu_etd_11015 for the case of record (azu_etd_11015), it will be great to save time not to wait for getting assigned handles before DSpace ingestion. In this case, the handle is known before ingestion to DSpace and Catalog. Thanks, Yan -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] from aspect to theme
Its added to the pageMeta as a trail, you might look at ItemViewer and copy that code, then maybe add Tombstone on the end of it... Mark On Fri, Jul 29, 2011 at 7:45 AM, Blanco, Jose blan...@umich.edu wrote: Mark, I'm pretty much finished with this. I just want to run it by Jim next time we meet, but I do have one question. The Tombstone page shows a - In the area where normally you have links that take you back to where you came from, like DSpace Home Archive Test Area University of Michigan Transportation Research Institute Reports View Item How do I get this to show up? I've tried a couple of things but can't find the mechanism that handles this. Thank you! Jose -Original Message- From: Blanco, Jose [mailto:blan...@umich.edu] Sent: Friday, July 22, 2011 3:15 PM To: Mark Diggory Cc: dspace-tech@lists.sourceforge.net; Mark H. Wood Subject: Re: [Dspace-tech] from aspect to theme Mark, I think I understand your directions. Sorry if I'm being hard headed about this, but I'm hoping that making this change will help me get smarter about Manakin and Cocoon. So, I created the selector. I think it does what is suppose to do. I've changed the sitemap in the ArtifactBrowse as you suggested. BTW, I don't quite understand what the difference is between ArtifactBrowse, BrowseArtifacts, and ViewArtifacts. Can you explain it without too much trouble? Here is a the change to the sitemap file. I think it's what you suggested: map:match type=HandleAuthorizedMatcher pattern=!READ map:select type=WithdrawnSelector map:when test=true map:transform type=TombstoneView/ map:serialize type=xml/ /map:when map:otherwise map:select type=AuthenticatedSelector map:when test=eperson map:transform type=RestrictedItem/ map:serialize/ /map:when map:otherwise map:act type=StartAuthentication map:parameter name=header value=xmlui.ArtifactBrowser.RestrictedItem.auth_header/ map:parameter name=message value=xmlui.ArtifactBrowser.RestrictedItem.auth_message/ /map:act map:serialize/ /map:otherwise /map:select /map:otherwise /map:match Now, I have my new transformer aspect/artifactbrowse/TombstoneView.java, and I'm not exactly sure how to change it. I copied the ItetemViewer.java file to TombsotneView.java, but how do I change the output of the body that is output? What needs to be output so that the themes know what to do? Thank you so much for this help -Jose -Original Message- From: Mark Diggory [mailto:mdigg...@atmire.com] Sent: Friday, July 22, 2011 1:48 PM To: Blanco, Jose Cc: dspace-tech@lists.sourceforge.net; Mark H. Wood Subject: Re: [Dspace-tech] from aspect to theme On Fri, Jul 22, 2011 at 10:28 AM, Blanco, Jose blan...@umich.edu wrote: Mark, I was kind of trying to do this. I started by creating an ItemViewerNew ( transformer ) using the esiting ItemViewer that was already there but modifying as necessary to have the reason for withdraw show up on the short display. According to what you are saying I should be able to create this new ItemViewerNew transformer without ( hopefully ) impacting the theme, but I’m not seeing it. Don’t I need a new theme to put the reason code just above where the bitstreams are listed, and how do I eliminate the capability to click on the link that lets you go to the bitstream. Not if you use the ArtifactBrowser aspect to generate the message, basically, your writing the DRI elements in Java rather than looking up the METS doc in XML/XSLT calls. You would be doing something like: Item item = (Item) HandleManager.getObject(handle) DCValue[] values = item.getMetadata(….). and then creating a DRI div to hold the message you retrieved. -- What I am proposing eliminates your working in the theming layer and creating a separate view for rendering the Tombstone that is not subject to the complexities your finding in the ItemViewer. For this you would be doing the following: a.) Creating a Transformer and adding DRI sections in its body method b.) Looking up the DSpace Item via the provided handle. c.) Rendering the message by getting the metadata out of the item for the view that is of interest in this case. This would be the simplest approach to rendering a view and would be useful in the next release. You would add: 1.) TombstoneView.java as a transformer 2.) Add a section before the restricted sections in ArtifactBrowser site maps. 3.) Write a WithdrawnSelector that will allow the site map to have conditional logic to determine if the item is withdrawn or not. 4.) Wrap the following section with that selector so that you can execute the WithdrawnView on the handle prior to the restricted view being evaluated.
[Dspace-tech] SSL and HTTPS Question
Dear Dspace-Tech, So, I've turned on the configuration flag that forces the user to use HTTPS when they log in to DSpace; Should the rest of their session take place over an https connection or is it safe for them to go back to regular http after they have logged in? Thank You, Joseph -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] SSL and HTTPS Question
Hi Jospeh, So, I've turned on the configuration flag that forces the user to use HTTPS when they log in to DSpace; Should the rest of their session take place over an https connection or is it safe for them to go back to regular http after they have logged in? For most sites, it is considered safe to go back to http. You might want to consider securing a few other pages, such as the password change page. Thanks, Stuart Lewis Digital Development Manager Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: +64 (0)9 373 7599 x81928 -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
