Hi All,
Our Library staff have identified an issue when using the Search in Dspace;
specifically, browsing for Muller-Wille doesn't find the researcher
Müller-Wille because the umlaut wasn't included in the search term.
I assume this is the same for academics who have accents etc. in their
Hi Kevin,
Please see the comments in this class:
https://github.com/DSpace/DSpace/blob/03276502d60b2644c0c2e6e1ace8846eb6cd5bf5/dspace-api/src/main/java/org/dspace/sort/OrderFormat.java
Note that for authors, the standard normalization used is:
I am able to edit the JSP files and see those changes.
I just edited build.properties and [dspace-src] and ran mvn clean package
and ant update. The changed DSpace name showed up on home page and the
title.
So looks like it is only changes to the the Message.properties file that do
no show up. I
I have recently updated my tomcat from v7.0.42 to 7.0.47. I am
encountering the following error when starting tomcat/dspace. Dropping
back to 7.0.42 fixes the problem... I'm wondering if anybody else has
tried this new tomcat and experienced this, and if there is a workaround so
that I can stay
We have seen that if we redeload or dspace instance a few hours later
our postgress connection pool begin to grow and push our limit of 175.
Presently we are using version 3 of DSpace and with that
commons-pool-1.4.jar
I wonder if I should be using a more courrent version.
From this question:
Thanks Brian!
I'm still not clear on what this means -- wrong version of Maven? I'm
using:
Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
On Fri, Dec 6, 2013 at 2:03 PM, Brian Freels-Stendel bfre...@unm.eduwrote:
Hi Bill,
This looks like a jaxen conflict between maven and
Hi Bill,
If you're running DSpace v.3.x, I'd at least consider upgrading to maven 3 as a
test. As I say, I don't have enough knowledge to really diagnose the problem;
just enough to get suspicious about what might be using jaxen.
B--
From: Bill Tantzen [mailto:wile...@gmail.com]
Sent:
7 matches
Mail list logo
