Hi Jason,
Unfortunately not - you'll need to use the source version. There isn't much
difference in the build procedure, so it shouldn't be too much hassle to
switch. Alternatively if it isn't urgent, you could wait until 1.6.1 is
released in the next month or two, as this will contain the
Hi Bryce,
You can check that both your database and email settings are OK by running
these scripts:
- [dspace]/bin/dspace test-database
- [dspace]/bin/dspace test-email
Depending on the error, if you view the HTML source of the internal error page
in your browser, half way down you may see
Hi,
In version 1.50 and later, the war files have been replaced by unpacked webapp
directories. After you run ant, you'll find a [dspace]/webapps directory, and
in this are directories for each webapp (jspui, xmlui, oai etc) where
previously you had .war files.
Copy the whole directory to
Hi Manu,
I'm testing 1.6 version and when I try to access to http:/my-dspace-url/solr
I get this message from Tomcat: Access to specified resource is forbidden.
The solr statistics are displayed with the jspui / xmlui rather than via the
solr webapp. The solr webapp is just there to provide
Hi Yelayou,
I use a shared Linux server with Tomcat and PostgreSQL features for my
project and
I need assistance on how to configure DSpace if possible.
Which parts of the DSpace configuration are you having difficulty with? The
manual should address most of these:
-
Hi Domingo,
Caused by: org.jdom.JDOMException:
http://apache.org/xml/features/validation/schema feature not recognized for
SAX driver oracle.xml.parser.v2.SAXParser
I suspect the error is related with the oracle parser since we are running
dspace in a OC4J hosted on an OAS 10.1.3, but
Hi Tumie,
we are trying to upgrade from dspace 1.5.2 to 1.6.0 but everything works fine
until step 9 for rolling log appeander upgrade were we get an error Exception
in thread main java.lang.noclassdefFoundError
org/dspace/app/launcher/scriptlauncher.
Have you managed to successfully run
Hi,
I've been running tests for upgrading our DSpace 1.4.2 installation to
1.6.x while remaining on PostgreSQL 7.4. For the upgrade steps to
succeed I had to make a couple of changes to the database schema
migration steps because PSQL 7.4 doesn't seem to support 1) changing a
data type of an
Stuart,
Thank you very much for pointing out this! I did copy all the
subdirectories to [tomcat]/webapps/ and removed the old war files there.
So my blank screen issue is not related to the missing war files (I have
solved the permission problem.). I will continue to struggle with the
blank
Hi
You can also deploy a default interface.
See: http://ir.sun.ac.za/wiki/index.php/Default_Interface
http://ir.sun.ac.za/wiki/index.php/Default_InterfaceCheers
hg.
On 15 April 2010 12:02, Shaw Yu x...@vcu.edu wrote:
Stuart,
Thank you very much for pointing out this! I did copy all the
Thank you for sharing this information.
Asko Soukka wrote:
Hi,
I've been running tests for upgrading our DSpace 1.4.2 installation to
1.6.x while remaining on PostgreSQL 7.4. For the upgrade steps to
succeed I had to make a couple of changes to the database schema
migration steps because
Thank you for the information. There is just too much to learn for an
old man. :-) .
Hilton Gibson wrote:
Hi
You can also deploy a default interface.
See: http://ir.sun.ac.za/wiki/index.php/Default_Interface
Cheers
hg.
On 15 April 2010 12:02, Shaw Yu x...@vcu.edu mailto:x...@vcu.edu
Ahh, there was a stack trace in the html source. Below is the stack trace.
However, its not obvious to me what exactly is wrong and how to fix it after
reading through the stack trace.
Unable to aquire dispatcher named default
=
Thank you very much for the replies. I will try them.
Regards
On Thu, Apr 15, 2010 at 9:48 AM, Stuart Lewis s.le...@auckland.ac.nzwrote:
Hi Manu,
I'm testing 1.6 version and when I try to access to
http:/my-dspace-url/solr
I get this message from Tomcat: Access to specified resource is
I have just brought up a 1.6 instance and have also set the solr server
in dspace.cfg as:
solr.log.server = http://localhost:8080/solr/statistics
solr.statistics.query.filter.spiderIp = true
solr.statistics.query.filter.isBot = true
When I click at the 'View Statistics', I got no
Hi,
I think I got the solution for this error. There are a few steps I have
not done:
1. [dspace]/reports directory was not created. Why this is not
automatically created when we deployed the system? Just wonder.
2. In dspace.cfg, (report.dir = ${dspace.dir}/reports)
there is an extra
The Top City Views in the Solr Statistics is still not correct. It seems
that it is able to detect only Bangkok in Thailand while it is not true.
I remember that I raised this issue during the firest testathorn, and it
was solved. But why it is not working correctly again?
Panyarak
Prince
I know this is probably an easy one, but I'm having trouble finding an answer
in the DSpace Wiki or 1.5.2 DSpace manual.
I've got a collection in DSpace that is using Dublin Core for metadata, and I
would like to change the way the Simple Item Record displays those values.
Simply put, I would
Thanks a lot Mark. You are right. The
'solr.statistics.query.filter.spiderIp' must be false. And it works now.
But the detection of City is not quite correct. Where can I fine tune it?
Panyarak Ngamsritragul
Prince of Songkla University.
On Thu, 15 Apr 2010, Mark Diggory wrote:
Verify
Panyarak,
The city detection is all performed by the geoLite database, which is
downloaded to your [dspace] directory when you ant update. The work is does
to give location info from an IP address. To have more accurate data, they
offer a monthly updated paid version, GeoIP.
Stacy,
You should probably be using a different metadata field not a different
label. We encountered requests like this in dsp...@mit for fields like
Advisor vs. Supervisor vs. Thesis Advisor...
Mark
On Thu, Apr 15, 2010 at 9:33 AM, penning...@rhodes.edu wrote:
I know this is probably an easy
Thanks a lot Peter. The information you kindly shared is very helpful.
I download the patch you mention and I suspect that the file is corrupted.
There is a line saying '\ No newline at end of file' and the lines follow
may not be part of the patch too.
Panyarak Ngamsritragul
Prince of
22 matches
Mail list logo