Re: [Dspace-tech] Scroll Bar Bug

2015-07-09 Thread Pottinger, Hardy J.
Hi, Arthur, I looked at your attached screen shot, the item you're concerned about is the width of the collection select box. It is likely that you have a very wide/deep collection/community hierarchy, and the select box is just growing large enough to accommodate the contents. You might be able

[Dspace-tech] Scroll Bar Bug

2015-07-09 Thread Arthur Sady Cordeiro Rossetti
Guys, when I uploaded from version 5.1 to 5.2 in that new section " batch load import" im having a bug with the size of the scroll bar. I canĀ“t find in which file to change it. Im sending a print so you can see my situation. Does anyone know which file to change? Regards -- Arthur Sady C. Rosset

Re: [Dspace-tech] Creating a build path/classpath in Eclipse for DSpace

2015-07-09 Thread Terry Brady
Mark, Thanks for sharing this. I needed to install the m2eclipse plugin in order to get this to run. It appears to grab every jar file under the target directories and add them to the .classpath file. Terry On Thu, Jul 9, 2015 at 8:58 AM, Mark H. Wood wrote: > On Wed, Jul 08, 2015 at 07:20:3

Re: [Dspace-tech] (no subject)

2015-07-09 Thread Tim Donohue
Hi Ricardo, (I'm copying back in dspace-tech, as we ask that all questions be kept on the mailing list. It helps others also learn from the answers, or help with their own experience/answers. Thanks.) First off, I will mention that we do have plans to remove support for the database indexing

Re: [Dspace-tech] Physical memory insufficient

2015-07-09 Thread Tim Donohue
Hi Lewatle, We'd likely need more information here. How much memory have you made available to Java (via -Xmx / -Xms)? What is the specific out-of-memory error you are seeing in the DSpace logs? Is it a Heap Memory error or a PermGen one? Have you reviewed the recommendations for performance

Re: [Dspace-tech] dspace 1.7 statistics

2015-07-09 Thread v0ff4ik
Well, thanks for your help Terry once more, i've found the origin of this error. This version of dspace is not supported any more by developers and there are no necessary files to run solr correctly, we haven't downloaded them previously, by the time they were existing. The trying of installation

Re: [Dspace-tech] (no subject)

2015-07-09 Thread Tim Donohue
Hi Ricardo, It sounds like you are using an older version of DSpace with the Database-based browse system (which used bi_* tables)? That system has since been deprecated in recent releases, in favor of using Discovery / Solr for all search/browse activities. So, if you are using an older ve

Re: [Dspace-tech] Creating a build path/classpath in Eclipse for DSpace

2015-07-09 Thread Mark H. Wood
On Wed, Jul 08, 2015 at 07:20:39PM -0400, Terry Brady wrote: > Do you all have any tips for creating a proper build path for the DSpace > code base in Eclipse? > > My current process is very clumsy. > > I run the maven build and then I add jar files from the target directories > until all of the

[Dspace-tech] Physical memory insufficient

2015-07-09 Thread Lewatle Phaladi
Hi all, I am still getting blank page after upgraded well from 3.2 to 5.2 and I have found the attached error file in my dspace installation, just want to share with you to get more detail if the error is really the one preventing the upgrade to go through. Regards, Lewatle This communicati

[Dspace-tech] Turning off email notifications for a dspace Group.

2015-07-09 Thread Evans, Kevin
Hi, We have had a request from our library colleagues to turn off email notifications. The particular issue is as part of a Dspace Group (i.e. Curators) they receive an email notification for every item submitted. Is there a straightforward way to turn these off per group? Have I missed someth

[Dspace-tech] (no subject)

2015-07-09 Thread RICARDO EITO BRUN
Dear colleagues, after importing / migrating the database (Postgresql 9.1), everything is working fine but I am getting an error message when: a) trying to removing items, b) creating relations between items. The error message I get is: "org.postgresql.util.PSQLException ERROR: relation "bi_priva