Re: [Dspace-tech] IMPORTANT NEWS: Important Info for Future Editions | Ranking Web of Repositories
Hi Hilton, Looking at their proposal I can see that as an institution we’ll be excluded on at least 3 points, assuming that they meant to finish point 4 with “will be excluded”. 4) Repositories using ports others than 80 or 8080 5) Institutional repositories that use the name of the software in the host name will be excluded. 6) Institutional repositories that use more than 4 directory levels for the URL address of the full texts will be excluded. We’ll be excluded by point 4 as we use https rather than http (there is a redirect on http that bounces visitors to the https site). We’ll be excluded by point 5 as our repository has a hostname of dspace. Finally we’ll be excluded by point 6 as our setup has 5 directories to the full text. But looking at what actually is important here, which I believe to be the visibility of our repository’s content, I found myself ruling out making any changes to comply with their proposal. If we switch to http as suggested by their point 4 then we’ll actually worsen our position in Google search results. From the point of view of point 5 I can’t see anyway to justify the workload required to switch hostnames and keep all the legacy links working (if we let the old links break then our visibility will definitely decrease). Finally trying to do anything about point 6 would require extensive changes to our DSpace configuration and code (and the same large workload to keep the legacy links working). In other words our repository’s visibility will be negatively affected if we try to complying with their new proposal. Regards, Jason Cooper. From: Hilton Gibson [mailto:hilton.gib...@gmail.com] Sent: 01 September 2014 19:01 To: dspace-tech; General List Subject: [Dspace-tech] IMPORTANT NEWS: Important Info for Future Editions | Ranking Web of Repositories The Ranking is also a powerful tool for penalizing bad practices, with especial emphasis in the awful naming proposals by software developers that ignore librarian traditions and in many ways are going against intellectual rights of depositing authors. We truly believe the lengthy and useless addresses coined for the repository items have a negative impact in their web visibility and affect the authors will to deposit as it makes difficult the citation of full texts in future papers. http://repositories.webometrics.info/en/node/26 Hi All Sorry for the cross-posting How will this affect DSpace installations? Regards hg -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] After upgrading to 3.2 Alert emails have started to fail
Hi, After upgrading to version 3.2 of DSpace I have noticed in the logs that errors that try to send an email alert fail with the following error: 2013-08-02 10:02:51,325 WARN org.dspace.app.webui.util.UIUtil @ Unable to send email alert javax.mail.internet.AddressException: Illegal address in string ``'' at javax.mail.internet.InternetAddress.init(InternetAddress.java:94) at org.dspace.core.Email.send(Email.java:302) at org.dspace.app.webui.util.UIUtil.sendAlert(UIUtil.java:419) at org.dspace.app.webui.servlet.InternalErrorServlet.doGet(InternalErrorServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:364) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:213) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:724) Has anyone seen this error before and if so what was the cause and what did you have to do to fix it? Regards, Jason Cooper. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] After upgrading to 3.2 Alert emails have started to fail
Hi, mail.admin had my email address in it, but alert.recipient didn't have an email address. I have now put my email address in for that one as well (in double quotes). Now I just need to get an error that would send an alert to test that I get the email. Regards, Jason. -Original Message- From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84 Sent: 02 August 2013 10:31 To: Jason Cooper Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] After upgrading to 3.2 Alert emails have started to fail What's your value of the mail.admin configuration property in dspace.cfg? Seems like you have an empty string there. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] After upgrading to 3.2 Alert emails have started to fail
Hi, Thanks for the help. I have removed the double quotes now from the config and will see if I get any errors/emails appear. Regards, Jason. From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84 Sent: 02 August 2013 10:55 To: Jason Cooper Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] After upgrading to 3.2 Alert emails have started to fail Don't use quotes. This is what that section should look like: mail.from.address = dspace-nore...@dspace.lboro.ac.ukmailto:dspace-nore...@dspace.lboro.ac.uk # Currently limited to one recipient! feedback.recipient = j.l.coo...@lboro.ac.ukmailto:j.l.coo...@lboro.ac.uk # General site administration (Webmaster) e-mail mail.admin = j.l.coo...@lboro.ac.ukmailto:j.l.coo...@lboro.ac.uk # Recipient for server errors and alerts alert.recipient = j.l.coo...@lboro.ac.ukmailto:j.l.coo...@lboro.ac.uk # Recipient for new user registration emails registration.notify = j.l.coo...@lboro.ac.ukmailto:j.l.coo...@lboro.ac.uk mail.from.address doesn't have to exist, but it has to be filled in (this is probably what's causing the problem). And you probably want to leave registration.notify empty. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] DSPACE Upgrade...
On Thu, Aug 1, 2013 at 4:39 PM, Joseph Sayah joseph.sa...@lau.edu.lb wrote: Currently we have DSPACE version 1.6.0 and we are planning to upgrade to the latest version, my question is the following: is it possible to upgrade directly form version 1.6.0 to the latest version, and can you provide me with the necessary documents of the upgrade… Hi Joseph, I have just been dealing with the same issue myself and I would suggest that you follow Helix's advice about moving to a machine with the latest version of your preferred OS if possible. If you don't have that luxury then make sure that your server meets all the minimum requirements before doing the actual upgrade. Things that I discovered that I needed to bring up to date, on our RedHat Enterprise Linux 5 server, before moving to 3.2 from 1.6.2 were: * Postgresql - We were still on 8.1 and had to upgrade to 8.4. To upgrade we needed to export the full database, remove the old version of postgress, install the newer 8.4 version, initialise the database and finally import the exported database. (http://www.postgresql.org/docs/8.4/static/install-upgrading.html was very helpful when doing this). * Maven and Ant - just grab the latest binaries from apache and make sure they appear at the start of your path. * Java - while java 1.6 will work for almost everything if you need to be able to harvest from DSpace via OAI-PMH then you will need version 1.7 at least (also make sure that tomcat is using the 1.7 java and not an older 1.6 java). Definitely follow Helix's advice about starting fresh with the configuration files as there are a lot of changes to the structure them between 1.6 and 3.2. Some bits are broken out into their own config files and a lot of the config entries usualy altered have been pulled out into the build.properites file. Now the usual advice; Run through the whole upgrade on your test instance to make sure that you know what needs doing and in what order (Write it down as you go, so you can repeat it on your live server without forgetting a step); and finally make sure you have a full backup before you do it, just to be on the safe side. Regards, Jason Cooper -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Error - javax.servlet.ServletException: Unable to compile class for JSP
Hi, DSpace / Tomcat has suddenly decided that it can't compile a class and produces the following stack dump. javax.servlet.ServletException: Unable to compile class for JSP at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:119) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:286) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:662) Has anyone encountered this or has any suggestions on possible causes? I suspect the OS (Red Hat Enterprise 5) has updated something vital but can't see what it is from the error. Regards, Jason Cooper -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Error - javax.servlet.ServletException: Unable to compile class for JSP
On 20/12/2011 22:19, Jason Cooper wrote: Hi, DSpace / Tomcat has suddenly decided that it can't compile a class and produces the following stack dump. ...snip... Has anyone encountered this or has any suggestions on possible causes? I suspect the OS (Red Hat Enterprise 5) has updated something vital but can't see what it is from the error. Regards, Jason Cooper Figured it out, yum had updated tomcat and altered the owner of its work directory. effectively which stopped tomcat from using it to compile its JSPs. Regards, Jason Cooper. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] notify emails not being sent in 1.5.2
Hi, Just to let everyone know I have figured it out and also so when the next person hits this there is an answer to the problem. The problem was being caused by Java not using dspace’s javamail. A solution is on http://old.nabble.com/javax.mail.NoSuchProviderException:-smtp-td17671684.html specifically this post http://old.nabble.com/Re:-javax.mail.NoSuchProviderException:-smtp-p17676327.html was key to solving it. Regards, Jason. Hi, I have an install of version 1.5.2 on Linux that doesn’t seem to be sending the notify emails out. Unfortunately the test-email script isn’t available in version 1.5.2 (it was added in version 1.6 I believe). Does anyone have any suggestions on how to debug the sending of the notify emails or any suggestions of common problems that stop them being sent. Regards, Jason Cooper. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] FW: notify emails not being sent in 1.5.2
Hi, I have an install of version 1.5.2 on Linux that doesn’t seem to be sending the notify emails out. Unfortunately the test-email script isn’t available in version 1.5.2 (it was added in version 1.6 I believe). Does anyone have any suggestions on how to debug the sending of the notify emails or any suggestions of common problems that stop them being sent. Regards, Jason Cooper. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
