According to the 1.6.2 documentation, this should be no problem, it's even
recommended there to run it on postgres 8.x
http://www.dspace.org/1_6_2Documentation/ch03.html#N10708
best regards,
Bram Luyten
@mire
Technologielaan 9 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 -
Hi All,
In dspace 1.6. I want to move a collection(3377) from a community(231)
to another community(310)
I used a dspace command sudo /home/dspace/bin/dspace community-filiator
--set --parent=10568/310 --child=10568/3377.
But Error, child community cannot be found: 10568/3377.
Can
Hi All,
In dspace 1.6. I want to move a collection(3377) from a community(231)
to another community(310)
I used a dspace command sudo /home/dspace/bin/dspace community-filiator
--set --parent=10568/310 --child=10568/3377.
But Error, child community cannot be found: 10568/3377.
Can
I believe this should be corrected in dspace 1.7.1, the warning is
caused by a bug that was uncovered in 1.7.0.
On Wed, Mar 30, 2011 at 9:37 AM, liss RR liss...@hotmail.com wrote:
Hi all,
I 've intalled dspace 1.7.0 and I get this error in the logs file
ERROR
Hello,
the community filiator relates to sub-community management, see
8.9. Sub-Community Management of the DSpace System Documentation.
It does not handle collection-community relations.
You can move a collection on db level (usual warning about backup etc.)
with the following sql command:
Hi All,
I m getting the following errors, but I cannot figure out the source of the
problem.
-Original Message-
From: dsp...@uzlib.uz.ac.zw [mailto:dsp...@uzlib.uz.ac.zw]
Sent: Wednesday, March 30, 2011 8:49 PM
To: ictmana...@uzlib.uz.ac.zw
Subject: DSpace: Internal Server Error
An
Thanks .. this worked.
So this page is cached for a bit in the appserver.
From my observations some pages are not cached in this fashion
is there any controls at the cache level? I've found cocoon.properties
file buried in the webapp
--
thanks
kevin.foote
On Wed, 30 Mar 2011,
On Thu, Mar 31, 2011 at 14:51, Kevin P. Foote kpfo...@iup.edu wrote:
From my observations some pages are not cached in this fashion
is there any controls at the cache level? I've found cocoon.properties
file buried in the webapp
I have no idea. Try looking for Cocoon documentation (it's not
I've just implemented Solr stats. They seem to be working fine when logged
onto a collection/community. But if you were to
go to http://localhost:8080/solr/ Zilch.
I'm running everything via apache to tomcat.
I'm thinking I have my vhost locked down too hard, or my proxy is wrong.
Any
Dear All,
I want to upload .csv metadata file at present Import Metadata menu is not
displaying under administrative tools in my installation admin interface
(using Dspace 1.7.0). Can any one help me to enable Import Metadata menu.
At Admin login Interface I am getting below given items except
Jeff,
What exactly is Zilch? a 403? a 404? Post your dspace-solr-search and
dspace.cfg config and where your dspace instance is running.
Mark
On Thu, Mar 31, 2011 at 7:33 AM, Jeffrey Trimble jatrim...@ysu.edu wrote:
I've just implemented Solr stats. They seem to be working fine when logged
Hi Manju,
There is only supposed to be an Import Metadata button if your user is the
site admin. If you log in as the admin user (dspacedemo+admin@...) on the
demo site ( demo.dspace.org/xmlui ), you'll notice that admin user gets the
import metadata button, but none of the other users have it.
Jeffrey,
Is Dspace installed on your local machine (localhost), or a remote server?
Because, there is a localhostrestrictionfilter that will give you
403/Forbidden if you try to visit a remote solr.
You can look at this for some info: https://jira.duraspace.org/browse/DS-631
#solr, #tomcat,
it seems that increasing the connection pool in dspace.cfg resolves the
problem (keeping the ResultTTL=0):
i've increased the db.maxconnection = 30 to db.maxconnection = 500 and
it seems working fine. I do not know how much this will affect the server!
I can't really troubleshoot the problem but
What happens when you go to the equivalent of: http://demo.dspace.org/*
xmlui/admin/metadataimport* on your instance?
Peter Dietz
On Thu, Mar 31, 2011 at 12:06 PM, Manju N manjunayak1...@gmail.com wrote:
Hi, Dietz
Thank you very much for your help.
I logged as
After your last posting for testing Solr, I thought I would do it for my
server, just to see what I got.
So if I run: http://yourhost:yourport/solr/search/select?q=*:*
I get a 403 error. Mine is
http://digital.maag.ysu.edu:8080/solr/search/select?q=*:*
HTTP Status 403-
type STATUS REPORT
Jeff,
Can't you use http://localhost:8080/solr
Yes, going to the qualified domain name is not applying the loopback
port, so you are access restricted. MAke sure that in
dspace-solr-search.cfg and dspace.cfg that the solr server urls are
configured to use localhost.
Mark
On Thu, Mar 31, 2011
Ah...my local server is a BIG AIX power6 box. No monitor on it or web
software. :-)
So, you really can't http://localhost:8080/solr on it.
And I dont' have a dspace-solr-search.cfg file anywhere.
The plot thickens.
--Jeff
On Mar 31, 2011, at 1:53 PM, Mark Diggory wrote:
Jeff,
Can't
do you have wget on the server? that would be a good tool to have in
place for testing connections.
On Thu, Mar 31, 2011 at 11:00 AM, Jeffrey Trimble jatrim...@ysu.edu wrote:
Ah...my local server is a BIG AIX power6 box. No monitor on it or web
software. :-)
So, you really can't
Yep...couldn't live without it!
On Mar 31, 2011, at 2:39 PM, Mark Diggory wrote:
do you have wget on the server? that would be a good tool to have in
place for testing connections.
On Thu, Mar 31, 2011 at 11:00 AM, Jeffrey Trimble jatrim...@ysu.edu wrote:
Ah...my local server is a BIG AIX
Hi folks
We're running DSpace 1.7.0 here now (fresh install, but we upgraded our
old 1.3.2 db). Everything seems to be working well, except that I'd like
to customize our displayed item metadata and
[dspace-source]/config/language-packs/Messages.properties does not exist.
I've tried creating
We need to delete the some custom metadata that was created. We believe that
we have deleted all the spots where that metadata was referenced, yet when
attempting to delete the entire schema, this message is returned:
org.postgresql.util.PSQLException: ERROR: update or delete on table
Hi Sisay,
On 31/03/11 20:32, Webshet, Sisay (ILRI) wrote:
In dspace 1.6. I want to move a collection(3377) from a community(231)
to another community(310)
I used a dspace command sudo /home/dspace/bin/dspace community-filiator
--set --parent=10568/310 --child=10568/3377.
But Error, child
Hi
I had a similar problem and it turned out I still had custom metadata
hanging around in one my records.
You could dump your metadata out of DSpace and search the exported
metadata to check that all your custom field values have been deleted.
ItemExport is a good tool for exporting from
24 matches
Mail list logo
