date:20110331

Re: [Dspace-tech] custom metadata deletion question

2011-03-31 Thread Hayden Young


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 the command line:

/path/to/dspace/bin/dspace dsrun org.dspace.app.itemexport.ItemExport -h

or you can export from the DSpace UI by selecting a collection then 
selecting export metadata from the context menu.


There's also a batch editing tool by Stuart Lewis floating around as 
well which (I think) allows you to edit metadata from a CSV file.


Cheers


Hayden

On 01/04/11 04:40, Paul Go wrote:


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 "metadatafieldregistry" violates foreign key constraint
"metadatavalue_metadata_field_id_fkey" on table "metadatavalue"

Detail: Key (metadata_field_id)=(72) is still referenced from
table "metadatavalue".


How can we delete this entirely?

Thanks!

Paul Go

Systems Librarian /
Library Technology Manager
Paul V. Galvin Library
35 West 33rd Street
Chicago, IL  60616
312.567.7997
p...@iit.edu 


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf


___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


--
Hayden Young
Managing Director
Wijiti Pty Ltd
p. +61 (0) 8 6102 1198
m. +61 (0) 405 520 778
e. haydenyo...@wijiti.com
w. www.wijiti.com
vcard. www.wijiti.com/vcard/haydenyoung.vcf

NOTICE
This e-mail and any attachments are intended for the addressee(s) only and may 
be confidential. They may contain legally privileged or copyright material. You 
should not read, copy, use or disclose them without authorization. If you are 
not the intended recipient please contact the sender as soon as possible by 
return e-mail and then please delete both messages. This notice should not be 
removed.

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] (no subject)

2011-03-31 Thread Andrea Schweer

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 community cannot be found: 10568/3377.

The documentation states that the community filiator works only to
re-parent a *community*, not a collection. Whenever I have to move a
collection to a new parent community, I do it directly in the database.
The following sql statement should work (make a backup of your database
first!):

update community2collection set community_id = (select resource_id from
handle where handle = '10568/310') where community_id = (select
resource_id from handle where community_id = resource_id and handle =
'10568/231') and collection_id = (select resource_id from handle where
collection_id = resource_id and handle = '10568/3377');

This assumes that collection 10568/3377 is currently a direct child of
community 10568/231 and you want it to be a direct child of 10568/310
instead.

I've found that on xmlui, this change won't be reflected in the
breadcrumb trail at the top of the page (probably due to Cocoon
caching). Editing the description of the collection (eg adding a space
to the end of the description) resolves that problem.

I've been meaning to write code that allows an administrator to do this
via the web interface but I haven't had the time for that yet.

Again, make sure to have a current backup of your database before you
try this on a production machine!

cheers,
Andrea

-- 
Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] custom metadata deletion question

2011-03-31 Thread Paul Go

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
"metadatafieldregistry" violates foreign key constraint
"metadatavalue_metadata_field_id_fkey" on table "metadatavalue"

Detail: Key (metadata_field_id)=(72) is still referenced from table
"metadatavalue".


How can we delete this entirely?

Thanks!

Paul Go

Systems Librarian /
Library Technology Manager
Paul V. Galvin Library
35 West 33rd Street
Chicago, IL  60616
312.567.7997
p...@iit.edu
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Messages.properties doesn't exist

2011-03-31 Thread Sarah Ryder


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 a Messages.properties w/ just a few items in it that 
we want customized. If I create the language-packs directory w/ this file 
in it and rebuild, it doesn't do anything. If I put the file into 
[dspace-source]/modules/jspui/src/main/resources, then it seems to 
completely overwrite all default item displays as blank and only shows the 
custom items that in the file.

Am I missing something here? How does one customize meta display in 
version 1.7 without an existing Messages.properties file? Any help would 
be much appreciated.

Thanks!

-Sarah Ryder
Web Development
Hampshire College
413.559.5477

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Jeffrey Trimble

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  wrote:
>> 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 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 at 9:57 AM, Jeffrey Trimble  wrote:
 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
 messages
 description  ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN
 Apache Tomcat /6.0.18

 Perhaps I forgot to do something.  But below is my dspace.cfg sections.
 I'm running 1.6.2 currently.
 # Usage Logging #
 # set this to be the port you run the dspace "solr" webapp
 # on, by default, we are assuming a test configuration with
 # tomcat still running on port 8080
 #solr.log.server = http://localhost:8080/solr/statistics
 solr.log.server = http://127.0.0.1:8080/solr/statistics
 # The location for the Geo Database retrieved on update/installation
 solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
 # If enabled the statistics system will look for an X-Forward header
 # if it finds it, it will use this for the user IP Addrress
 # it is enabled by default
 useProxies = true
 # Control if the statistics pages should be only shown to authorized users
 # If enabled, only the administrators for the DSpaceObject will be able to
 # view the statistics.
 # If disabled, anyone with READ permissions on the DSpaceObject will be 
 able
 # to view the statistics.
 statistics.item.authorization.admin=true
 # Usage Logging #
 # set this to be the port you run the dspace "solr" webapp
 # on, by default, we are assuming a test configuration with
 # tomcat still running on port 8080
 #solr.log.server = http://localhost:8080/solr/statistics
 solr.log.server = http://127.0.0.1:8080/solr/statistics
 # The location for the Geo Database retrieved on update/installation
 solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
 # If enabled the statistics system will look for an X-Forward header
 # if it finds it, it will use this for the user IP Addrress
 # it is enabled by default
 useProxies = true
 # Control if the statistics pages should be only shown to authorized users
 # If enabled, only the administrators for the DSpaceObject will be able to
 # view the statistics.
 # If disabled, anyone with READ permissions on the DSpaceObject will be 
 able
 # to view the statistics.
 statistics.item.authorization.admin=true

 statistics.item.authorization.admin=true
 # control solr statistics querying to filter out spider IPs
 # false by default
 # solr.statistics.query.filter.spiderIp = false
 # control solr statistics querying to look at "isBot" field to determine
 # if record is a bot. true by default.
 # solr.statistics.query.filter.isBot = true
 # Solr Event fields indexed
 statistics.items.dc.1=dc.identifier
 statistics.items.dc.2=dc.dateaccession
 statistics.items.type.1=dcinput
 statistics.items.type.2=date
 statistics.default.start.datepick = 01/01/1977
 # URLs to download IP addresses of search engine spiders from
 solr.spiderips.urls = http://iplists.com/google.txt, \
   http://iplists.com/inktomi.txt, \
   http://iplists.com/lycos.txt, \
   http://iplists.com/infoseek.txt, \
   http://iplists.com/altavista.txt, \
 http://iplists.com/excite.txt, \
   http://iplists.com/misc.txt, \
   http://iplists.com/non_engines.txt

 Dspace is running: [dspace]/webapps  (We are using "Technique B" from the
 documentation.  We've
 referred it from [catalina]/conf/server.xml]
 Everything is running on the same physical server.
 Something is amiss in my knowledge, I am sure of.  So, take aim and shoot
 me.  :-)

 On Mar 31, 2011, at 11:12 A

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Mark Diggory

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  wrote:
> 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 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 at 9:57 AM, Jeffrey Trimble  wrote:
>>> 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
>>> messages
>>> description  ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN
>>> Apache Tomcat /6.0.18
>>>
>>> Perhaps I forgot to do something.  But below is my dspace.cfg sections.
>>> I'm running 1.6.2 currently.
>>> # Usage Logging #
>>> # set this to be the port you run the dspace "solr" webapp
>>> # on, by default, we are assuming a test configuration with
>>> # tomcat still running on port 8080
>>> #solr.log.server = http://localhost:8080/solr/statistics
>>> solr.log.server = http://127.0.0.1:8080/solr/statistics
>>> # The location for the Geo Database retrieved on update/installation
>>> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
>>> # If enabled the statistics system will look for an X-Forward header
>>> # if it finds it, it will use this for the user IP Addrress
>>> # it is enabled by default
>>> useProxies = true
>>> # Control if the statistics pages should be only shown to authorized users
>>> # If enabled, only the administrators for the DSpaceObject will be able to
>>> # view the statistics.
>>> # If disabled, anyone with READ permissions on the DSpaceObject will be able
>>> # to view the statistics.
>>> statistics.item.authorization.admin=true
>>> # Usage Logging #
>>> # set this to be the port you run the dspace "solr" webapp
>>> # on, by default, we are assuming a test configuration with
>>> # tomcat still running on port 8080
>>> #solr.log.server = http://localhost:8080/solr/statistics
>>> solr.log.server = http://127.0.0.1:8080/solr/statistics
>>> # The location for the Geo Database retrieved on update/installation
>>> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
>>> # If enabled the statistics system will look for an X-Forward header
>>> # if it finds it, it will use this for the user IP Addrress
>>> # it is enabled by default
>>> useProxies = true
>>> # Control if the statistics pages should be only shown to authorized users
>>> # If enabled, only the administrators for the DSpaceObject will be able to
>>> # view the statistics.
>>> # If disabled, anyone with READ permissions on the DSpaceObject will be able
>>> # to view the statistics.
>>> statistics.item.authorization.admin=true
>>>
>>> statistics.item.authorization.admin=true
>>> # control solr statistics querying to filter out spider IPs
>>> # false by default
>>> # solr.statistics.query.filter.spiderIp = false
>>> # control solr statistics querying to look at "isBot" field to determine
>>> # if record is a bot. true by default.
>>> # solr.statistics.query.filter.isBot = true
>>> # Solr Event fields indexed
>>> statistics.items.dc.1=dc.identifier
>>> statistics.items.dc.2=dc.dateaccession
>>> statistics.items.type.1=dcinput
>>> statistics.items.type.2=date
>>> statistics.default.start.datepick = 01/01/1977
>>> # URLs to download IP addresses of search engine spiders from
>>> solr.spiderips.urls = http://iplists.com/google.txt, \
>>>                       http://iplists.com/inktomi.txt, \
>>>                       http://iplists.com/lycos.txt, \
>>>                       http://iplists.com/infoseek.txt, \
>>>                       http://iplists.com/altavista.txt, \
>>>         http://iplists.com/excite.txt, \
>>>                       http://iplists.com/misc.txt, \
>>>                       http://iplists.com/non_engines.txt
>>>
>>> Dspace is running: [dspace]/webapps  (We are using "Technique B" from the
>>> documentation.  We've
>>> referred it from [catalina]/conf/server.xml]
>>> Everything is running on the same physical server.
>>> Something is amiss in my knowledge, I am sure of.  So, take aim and shoot
>>> me.  :-)
>>>
>>> On Mar 31, 2011, at 11:12 AM, Mark Diggory wrote:
>>>
>>> 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

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Jeffrey Trimble

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 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 at 9:57 AM, Jeffrey Trimble  wrote:
>> 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
>> messages
>> description  ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN
>> Apache Tomcat /6.0.18
>> 
>> Perhaps I forgot to do something.  But below is my dspace.cfg sections.
>> I'm running 1.6.2 currently.
>> # Usage Logging #
>> # set this to be the port you run the dspace "solr" webapp
>> # on, by default, we are assuming a test configuration with
>> # tomcat still running on port 8080
>> #solr.log.server = http://localhost:8080/solr/statistics
>> solr.log.server = http://127.0.0.1:8080/solr/statistics
>> # The location for the Geo Database retrieved on update/installation
>> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
>> # If enabled the statistics system will look for an X-Forward header
>> # if it finds it, it will use this for the user IP Addrress
>> # it is enabled by default
>> useProxies = true
>> # Control if the statistics pages should be only shown to authorized users
>> # If enabled, only the administrators for the DSpaceObject will be able to
>> # view the statistics.
>> # If disabled, anyone with READ permissions on the DSpaceObject will be able
>> # to view the statistics.
>> statistics.item.authorization.admin=true
>> # Usage Logging #
>> # set this to be the port you run the dspace "solr" webapp
>> # on, by default, we are assuming a test configuration with
>> # tomcat still running on port 8080
>> #solr.log.server = http://localhost:8080/solr/statistics
>> solr.log.server = http://127.0.0.1:8080/solr/statistics
>> # The location for the Geo Database retrieved on update/installation
>> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
>> # If enabled the statistics system will look for an X-Forward header
>> # if it finds it, it will use this for the user IP Addrress
>> # it is enabled by default
>> useProxies = true
>> # Control if the statistics pages should be only shown to authorized users
>> # If enabled, only the administrators for the DSpaceObject will be able to
>> # view the statistics.
>> # If disabled, anyone with READ permissions on the DSpaceObject will be able
>> # to view the statistics.
>> statistics.item.authorization.admin=true
>> 
>> statistics.item.authorization.admin=true
>> # control solr statistics querying to filter out spider IPs
>> # false by default
>> # solr.statistics.query.filter.spiderIp = false
>> # control solr statistics querying to look at "isBot" field to determine
>> # if record is a bot. true by default.
>> # solr.statistics.query.filter.isBot = true
>> # Solr Event fields indexed
>> statistics.items.dc.1=dc.identifier
>> statistics.items.dc.2=dc.dateaccession
>> statistics.items.type.1=dcinput
>> statistics.items.type.2=date
>> statistics.default.start.datepick = 01/01/1977
>> # URLs to download IP addresses of search engine spiders from
>> solr.spiderips.urls = http://iplists.com/google.txt, \
>>   http://iplists.com/inktomi.txt, \
>>   http://iplists.com/lycos.txt, \
>>   http://iplists.com/infoseek.txt, \
>>   http://iplists.com/altavista.txt, \
>> http://iplists.com/excite.txt, \
>>   http://iplists.com/misc.txt, \
>>   http://iplists.com/non_engines.txt
>> 
>> Dspace is running: [dspace]/webapps  (We are using "Technique B" from the
>> documentation.  We've
>> referred it from [catalina]/conf/server.xml]
>> Everything is running on the same physical server.
>> Something is amiss in my knowledge, I am sure of.  So, take aim and shoot
>> me.  :-)
>> 
>> On Mar 31, 2011, at 11:12 AM, Mark Diggory wrote:
>> 
>> 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  wrote:
>> 
>> 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 t

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Mark Diggory

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 at 9:57 AM, Jeffrey Trimble  wrote:
> 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
> messages
> description  ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN
> Apache Tomcat /6.0.18
>
> Perhaps I forgot to do something.  But below is my dspace.cfg sections.
> I'm running 1.6.2 currently.
> # Usage Logging #
> # set this to be the port you run the dspace "solr" webapp
> # on, by default, we are assuming a test configuration with
> # tomcat still running on port 8080
> #solr.log.server = http://localhost:8080/solr/statistics
> solr.log.server = http://127.0.0.1:8080/solr/statistics
> # The location for the Geo Database retrieved on update/installation
> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
> # If enabled the statistics system will look for an X-Forward header
> # if it finds it, it will use this for the user IP Addrress
> # it is enabled by default
> useProxies = true
> # Control if the statistics pages should be only shown to authorized users
> # If enabled, only the administrators for the DSpaceObject will be able to
> # view the statistics.
> # If disabled, anyone with READ permissions on the DSpaceObject will be able
> # to view the statistics.
> statistics.item.authorization.admin=true
> # Usage Logging #
> # set this to be the port you run the dspace "solr" webapp
> # on, by default, we are assuming a test configuration with
> # tomcat still running on port 8080
> #solr.log.server = http://localhost:8080/solr/statistics
> solr.log.server = http://127.0.0.1:8080/solr/statistics
> # The location for the Geo Database retrieved on update/installation
> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
> # If enabled the statistics system will look for an X-Forward header
> # if it finds it, it will use this for the user IP Addrress
> # it is enabled by default
> useProxies = true
> # Control if the statistics pages should be only shown to authorized users
> # If enabled, only the administrators for the DSpaceObject will be able to
> # view the statistics.
> # If disabled, anyone with READ permissions on the DSpaceObject will be able
> # to view the statistics.
> statistics.item.authorization.admin=true
>
> statistics.item.authorization.admin=true
> # control solr statistics querying to filter out spider IPs
> # false by default
> # solr.statistics.query.filter.spiderIp = false
> # control solr statistics querying to look at "isBot" field to determine
> # if record is a bot. true by default.
> # solr.statistics.query.filter.isBot = true
> # Solr Event fields indexed
> statistics.items.dc.1=dc.identifier
> statistics.items.dc.2=dc.dateaccession
> statistics.items.type.1=dcinput
> statistics.items.type.2=date
> statistics.default.start.datepick = 01/01/1977
> # URLs to download IP addresses of search engine spiders from
> solr.spiderips.urls = http://iplists.com/google.txt, \
>                       http://iplists.com/inktomi.txt, \
>                       http://iplists.com/lycos.txt, \
>                       http://iplists.com/infoseek.txt, \
>                       http://iplists.com/altavista.txt, \
>         http://iplists.com/excite.txt, \
>                       http://iplists.com/misc.txt, \
>                       http://iplists.com/non_engines.txt
>
> Dspace is running: [dspace]/webapps  (We are using "Technique B" from the
> documentation.  We've
> referred it from [catalina]/conf/server.xml]
> Everything is running on the same physical server.
> Something is amiss in my knowledge, I am sure of.  So, take aim and shoot
> me.  :-)
>
> On Mar 31, 2011, at 11:12 AM, Mark Diggory wrote:
>
> 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  wrote:
>
> 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 thoughts?
>
> Thanks,
>
>
> Jeffrey Trimble
>
> System LIbrarian
>
> William F.  Maag Library
>
> Youngstown State University
>
> 330.941.2483 (Office)
>
> jatrim...@ysu.edu
>
> http://www.maag.ysu.edu
>
> http://digital.maag.ysu.edu
>
> ""For he is the Kwisatz Haderach..."
>
>
>

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Jeffrey Trimble

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
messages
description  ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN

Apache Tomcat /6.0.18

Perhaps I forgot to do something.  But below is my dspace.cfg sections.

I'm running 1.6.2 currently.

# Usage Logging #
# set this to be the port you run the dspace "solr" webapp
# on, by default, we are assuming a test configuration with
# tomcat still running on port 8080
#solr.log.server = http://localhost:8080/solr/statistics
solr.log.server = http://127.0.0.1:8080/solr/statistics

# The location for the Geo Database retrieved on update/installation
solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat

# If enabled the statistics system will look for an X-Forward header
# if it finds it, it will use this for the user IP Addrress
# it is enabled by default
useProxies = true

# Control if the statistics pages should be only shown to authorized users
# If enabled, only the administrators for the DSpaceObject will be able to
# view the statistics.
# If disabled, anyone with READ permissions on the DSpaceObject will be able
# to view the statistics.
statistics.item.authorization.admin=true
# Usage Logging #
# set this to be the port you run the dspace "solr" webapp
# on, by default, we are assuming a test configuration with
# tomcat still running on port 8080
#solr.log.server = http://localhost:8080/solr/statistics
solr.log.server = http://127.0.0.1:8080/solr/statistics

# The location for the Geo Database retrieved on update/installation
solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat

# If enabled the statistics system will look for an X-Forward header
# if it finds it, it will use this for the user IP Addrress
# it is enabled by default
useProxies = true

# Control if the statistics pages should be only shown to authorized users
# If enabled, only the administrators for the DSpaceObject will be able to
# view the statistics.
# If disabled, anyone with READ permissions on the DSpaceObject will be able
# to view the statistics.
statistics.item.authorization.admin=true

statistics.item.authorization.admin=true

# control solr statistics querying to filter out spider IPs
# false by default
# solr.statistics.query.filter.spiderIp = false

# control solr statistics querying to look at "isBot" field to determine
# if record is a bot. true by default.
# solr.statistics.query.filter.isBot = true

# Solr Event fields indexed
statistics.items.dc.1=dc.identifier
statistics.items.dc.2=dc.dateaccession
statistics.items.type.1=dcinput
statistics.items.type.2=date
statistics.default.start.datepick = 01/01/1977

# URLs to download IP addresses of search engine spiders from
solr.spiderips.urls = http://iplists.com/google.txt, \
  http://iplists.com/inktomi.txt, \
  http://iplists.com/lycos.txt, \
  http://iplists.com/infoseek.txt, \
  http://iplists.com/altavista.txt, \
  http://iplists.com/excite.txt, \
  http://iplists.com/misc.txt, \
  http://iplists.com/non_engines.txt

Dspace is running: [dspace]/webapps  (We are using "Technique B" from the 
documentation.  We've
referred it from [catalina]/conf/server.xml] 

Everything is running on the same physical server.

Something is amiss in my knowledge, I am sure of.  So, take aim and shoot me.  
:-)

On Mar 31, 2011, at 11:12 AM, Mark Diggory wrote:

> 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  wrote:
>> 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 thoughts?
>> 
>> Thanks,
>> 
>> 
>> Jeffrey Trimble
>> System LIbrarian
>> William F.  Maag Library
>> Youngstown State University
>> 330.941.2483 (Office)
>> jatrim...@ysu.edu
>> http://www.maag.ysu.edu
>> http://digital.maag.ysu.edu
>> ""For he is the Kwisatz Haderach..."
>> 
>> 
>> --
>> Create and publish websites with WebMatrix
>> Use the most popular FREE web apps or write code yourself;
>> WebMatrix provides all the features you need to develop and
>> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>> ___
>> DSpace-tech mailing list
>> DSpace-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinf

Re: [Dspace-tech] Enable Metadata Import Menu under Admin Login

2011-03-31 Thread Peter Dietz

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  wrote:

> Hi, Dietz
>
>   Thank you very much for your help.
>
> I logged as a administrator group 1 which i created using
> create-administrator.
> http://localhost/xmlui/DRI/  when i click this i will get below given xml
> file which does not contain 
> Import Metadata
> 
>
> 
> −
> 
> −
> 
> DSpace/Manakin Repository
> −
> 
> Welcome to the new Manakin interface to the DSpace digital repository.
> DSpace is a digital service that collects, preserves, and distributes
> digital material. Repositories are important tools for preserving an
> organization's legacy; they facilitate digital preservation and scholarly
> communication.
> 
> 
> −
>  interactive="yes" rend="primary" action="/xmlui/search"
> n="front-page-search" method="get">
> Search DSpace
> Enter some text in the box below to search DSpace.
> −
> 
> −
>  type="text">
> 
> 
> −
>  type="button">
> 
> Go
> 
> 
> 
> −
>  rend="primary" n="comunity-browser">
> Communities in DSpace
> Select a community to browse its collections.
> −
>  id="aspect.artifactbrowser.CommunityBrowser.referenceSet.community-browser"
> rend="hierarchy" n="community-browser" type="summaryList">
>  url="/metadata/handle/123456789/2/mets.xml"/>
> 
> 
> 
> −
> 
> −
> 
> Browse
> −
> 
> All of DSpace
> −
> 
> Communities & Collections
> 
> −
> 
> By Issue Date
> 
> −
> 
> Authors
> 
> −
> 
> Titles
> 
> −
> 
> Subjects
> 
> 
> 
> 
> −
> 
> My Account
> −
> 
> Logout
> 
> −
> 
> Profile
> 
> −
> 
> Submissions
> 
> 
> 
> −
>  n="administrative">
> Administrative
> −
> 
> Access Control
> −
> 
> People
> 
> −
> 
> Groups
> 
> −
> 
> Authorizations
> 
> 
> −
> 
> Registries
> −
> 
> Metadata
> 
> −
> 
> Format
> 
> 
> −
> 
> Items
> 
> −
> 
> Withdrawn Items
> 
> −
> 
> Control Panel
> 
> −
> 
> Statistics
> 
> 
> 
> −
> 
> −
> 
> 2
> 
> manjunayak1...@yahoo.co.in
> mn
> n
>  qualifier="logoutURL">/xmlui/logout
> /xmlui/profile
> /xmlui/login
> en_US
> en
> 
> −
> 
> /xmlui
> 
> http
> 80
> localhost
> 
> /xmlui/search
>  qualifier="advancedURL">/xmlui/advanced-search
> query
> /xmlui/contact
> /xmlui/feedback
> DSpace Home
>  qualifier="rss+xml">/xmlui/feed/rss_1.0/site
>  qualifier="rss+xml">/xmlui/feed/rss_2.0/site
> DSpace Home
> 
> −
> 
>  url="/metadata/internal/repository/123456789/mets.xml"/>
> 
> 
> 
>
>
>
> On 31 March 2011 21:13, Peter Dietz  wrote:
>
>> 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. Try
>> visiting http://demo.dspace.org/xmlui/admin/metadataimport while logged
>> in as a non-admin user, and you get an insufficient privileges warning.
>>
>> For your instance that you have installed, either check that your user is
>> a site admin (i.e. member of group 1), or check that any customizations that
>> you've made haven't broken this feature.
>>
>> If your user can visit the admin/metadataimport page, and it has a file
>> box to upload metadata, then steps to debug the would be to up your logging
>> level to debug, and watch the logs while the page is rendered. Also, check
>> the DRI, i.e. http://demo.dspace.org/xmlui/DRI/ while logged in, and see
>> if 
>> Import Metadata
>>  exists.
>>
>> You can trace that backwards to see if you've customized
>> dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/aspect/administrative/Navigation.javathat
>>  is has a line:
>>
>>
>> admin.addItemXref(contextPath+ "/admin/metadataimport", 
>> T_administrative_import_metadata);
>>
>>
>> Hope that helps,
>> #1.7.0, #xmlui, #metadata-import
>>
>>
>> Peter Dietz
>>
>>
>>
>> On Thu, Mar 31, 2011 at 11:08 AM, Manju N wrote:
>>
>>> 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 Metadata
>>> Import menu.
>>>
>>> Context
>>>
>>> * Edit Community
>>> * Export Community
>>> * Create Collection
>>> * Create Sub-community
>>>
>>> Administrative
>>>
>>> *
>>>   Access Control
>>>   o People
>>>   o Groups
>>>   o Authorizations
>>> *
>>>   Registries
>>>   o Metadata
>>>   o Format
>>> * Items
>>> * Withdrawn Items
>>> * Control Panel
>>> * Statistics
>>>
>>>
>>> Thanks
>>> Manju Naika
>>> IIT Bombay
>>>
>>>
>>>
>>>
>>>
>>>
>>> -

Re: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection pool(resultSetTTL)

2011-03-31 Thread Kocisky

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 it seems that even with
ResultTTL = 0 the connection pool is not freed right away, and if the
connection pool is small it finishes its resources, does that make sense?
I've tried also with db.maxconnection = 500 and resultTTL=300: after 20
queries or so (2 queries per sec) i get the 404.

from the last troubleshoot (db.maxconnection = 500 and resultTTL=300) it
seems that the 2 parameters are just a secondary factor, it doesn't make
much sense to me.
again i dont know the infrastructure/implementation to understand it, how do
you see it?

Kocisky

On 29 March 2011 11:25, LeVan,Ralph  wrote:

> Have you been able to make any progress on this?
>
>
>
> Ralph
>
>
>
> *From:* LeVan,Ralph
> *Sent:* Thursday, March 24, 2011 4:42 PM
> *To:* Kocisky
> *Cc:* dspace-tech@lists.sourceforge.net
>
> *Subject:* RE: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection
> pool(resultSetTTL)
>
>
>
> With the resultSetTTL set to zero, how many requests can you make before
> you get an error?  How long do you have to wait until you can continue
> searching?
>
>
>
> Everyone else using the SRW interface has the same issues and you’re the
> first to report a problem.  You might try increasing the size of your
> connection pool.
>
>
>
> Ralph
>
>
>
> *From:* Kocisky [mailto:koci...@autistici.org]
> *Sent:* Thursday, March 24, 2011 4:33 PM
> *To:* LeVan,Ralph
> *Cc:* dspace-tech@lists.sourceforge.net
> *Subject:* Re: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection
> pool(resultSetTTL)
>
>
>
> Ralph,
>
> the problem reported in my last email was generated by this URL:
>
>
> http://10.0.102.11:8280/SRW/search/DSpace?query=dc.creator+%3D+%22smith%22&version=1.1&operation=searchRetrieve&recordSchema=info%3Asrw%2Fschema%2F1%2Fdc-v1.1&maximumRecords=10&startRecord=1&resultSetTTL=0&recordPacking=xml&recordXPath=&sortKeys=
>
> this is another example:
>
> Links:<< Back to Search 
> Results for Search: dc.creator = "smith"
>
> Records found: 3
> Record: 1 of 3
>
> Schema: Dublin Core
> Record: 2 of 3
>
> Schema: Dublin Core
> Record: 3 of 3
>
> Schema: Dublin Core
>
> I have to say that with resultSetTTL=0 it happens less frequently, but if
> you make a request each second i think you will definitely experience the
> problem.
> I was thinking to use SRW for making the queries from a client web
> application to a dspace instance.
>
> I guess that you aren't experiencing this issue, can i ask you what is your
> environment?
> thank you!
>
> Kociscky
>
>
>
> On 22 March 2011 14:17, LeVan,Ralph  wrote:
>
> The more I think about this, the more I am convinced that the problem is
> confusion at your end.  The fact that the searching problem clears up
> after 3 minutes is pretty much proof that the cache is being cleared
> appropriately.  The issue is how to get it cleared out more quickly.
>
> I think the root problem is the resultSetTTL parameter in your request.
> Through it, you are explicitly asking the server to keep the result set
> for 300 seconds.  No matter what you set the default value to, your
> explicit request will override that.  You need to omit that parameter
> for the default to take effect.  Better yet, you should explicitly
> specify a resultSetTTL=0 to let the server know you do not want any
> caching of results.
>
> Let me know if this helps.
>
> Ralph
>
>
> > -Original Message-
> > From: LeVan,Ralph
> > Sent: Tuesday, March 22, 2011 11:42 AM
> > To: 'Kocisky'; dspace-tech@lists.sourceforge.net
> > Subject: RE: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection
> > pool(resultSetTTL)
> >
> > Kocisky, does that search actually return records when it doesn't
> return the 404
> > response?
> >
> > The root problem is that the search opens a connection to the DSpace
> database
> > and SRU caches that connection for the life of the search result.
> Typically,
> > those result sets are cleared from the cache after a configurable
> period of
> > idleness.  That configuration happen through the specification of a
> default value
> > in the database configuration file, but can be overridden in the
> request through
> > the resultSetTTL parameter (which I note you still have set to 300
> seconds in the
> > request you have shared.)
> >
> > I have spotted a path in my code where the result set would not be
> freed if no
> > records had be found as the result of the query.
> >
> > So, does that search for creator=smith actually find documents?
> >
> > Ralph
> >
> > > -Original Message-
> > > From: Kocisky [mailto:koci...@autistici.org]
> > > Sent: Monday, March 21, 2011 4:04 PM
> > > To: dspace-tech@lists.sourceforge.net
>
> > > Subject: [Dspace-tech] SRW Dspace 1.7 Cannot g

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Peter Dietz

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, #403


Peter Dietz



On Thu, Mar 31, 2011 at 11:12 AM, Mark Diggory  wrote:

> 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 
> wrote:
> > 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 thoughts?
> >
> > Thanks,
> >
> >
> > Jeffrey Trimble
> > System LIbrarian
> > William F.  Maag Library
> > Youngstown State University
> > 330.941.2483 (Office)
> > jatrim...@ysu.edu
> > http://www.maag.ysu.edu
> > http://digital.maag.ysu.edu
> > ""For he is the Kwisatz Haderach..."
> >
> >
> >
> --
> > Create and publish websites with WebMatrix
> > Use the most popular FREE web apps or write code yourself;
> > WebMatrix provides all the features you need to develop and
> > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> > ___
> > DSpace-tech mailing list
> > DSpace-tech@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/dspace-tech
> >
>
>
>
> --
> Mark R. Diggory
> @mire - www.atmire.com
> 2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
> Technologielaan 9 - 3001 Heverlee - Belgium
>
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Enable Metadata Import Menu under Admin Login

2011-03-31 Thread Peter Dietz

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. Try visiting
http://demo.dspace.org/xmlui/admin/metadataimport while logged in as a
non-admin user, and you get an insufficient privileges warning.

For your instance that you have installed, either check that your user is a
site admin (i.e. member of group 1), or check that any customizations that
you've made haven't broken this feature.

If your user can visit the admin/metadataimport page, and it has a file box
to upload metadata, then steps to debug the would be to up your logging
level to debug, and watch the logs while the page is rendered. Also, check
the DRI, i.e. http://demo.dspace.org/xmlui/DRI/ while logged in, and see if

Import Metadata
 exists.

You can trace that backwards to see if you've customized
dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/aspect/administrative/Navigation.javathat
is has a line:

admin.addItemXref(contextPath+ "/admin/metadataimport",
T_administrative_import_metadata);

Hope that helps,
#1.7.0, #xmlui, #metadata-import

Peter Dietz

On Thu, Mar 31, 2011 at 11:08 AM, Manju N  wrote:

> 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 Metadata
> Import menu.
>
> Context
>
> * Edit Community
> * Export Community
> * Create Collection
> * Create Sub-community
>
> Administrative
>
> *
>   Access Control
>   o People
>   o Groups
>   o Authorizations
> *
>   Registries
>   o Metadata
>   o Format
> * Items
> * Withdrawn Items
> * Control Panel
> * Statistics
>
>
> Thanks
> Manju Naika
> IIT Bombay
>
>
>
>
>
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Solr and 403s

2011-03-31 Thread Mark Diggory

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  wrote:
> 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 thoughts?
>
> Thanks,
>
>
> Jeffrey Trimble
> System LIbrarian
> William F.  Maag Library
> Youngstown State University
> 330.941.2483 (Office)
> jatrim...@ysu.edu
> http://www.maag.ysu.edu
> http://digital.maag.ysu.edu
> ""For he is the Kwisatz Haderach..."
>
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>



-- 
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Technologielaan 9 - 3001 Heverlee - Belgium

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Enable Metadata Import Menu under Admin Login

2011-03-31 Thread Manju N

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 Metadata
Import menu.

Context

* Edit Community
* Export Community
* Create Collection
* Create Sub-community

Administrative

*
  Access Control
  o People
  o Groups
  o Authorizations
*
  Registries
  o Metadata
  o Format
* Items
* Withdrawn Items
* Control Panel
* Statistics


Thanks
Manju Naika
IIT Bombay
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Solr and 403s

2011-03-31 Thread Jeffrey Trimble

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 thoughts?

Thanks,


Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
jatrim...@ysu.edu
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
""For he is the Kwisatz Haderach..."


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] login page trigger ..

2011-03-31 Thread helix84

On Thu, Mar 31, 2011 at 14:51, Kevin P. Foote  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 DSpace-specific).

Regards,
~~helix84

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] login page trigger ..

2011-03-31 Thread Kevin P. Foote


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, helix84 wrote:

-> You can try to clean the Cocoon cache, too:
-> 
-> 1.) First, don't forget to shutdown Tomcat.
-> 2.) cd ${tomcat6.home}/work/Catalina/{appropriate.domain.dir}/_/
-> 3.) rm -rf cache-dir
-> 4.) Start Tomcat again.
-> 
-> Regards,
-> ~~helix84
-> 

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] FW: DSpace: Internal Server Error

2011-03-31 Thread amutsikiwa

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 internal server error occurred on http://ir.uz.ac.zw:8080/jspui:

Date:   3/30/11 8:49 PM
Session ID: B870EEAD5BADCC6F892503A11C400FA3
User:   Anonymous
IP address: 66.249.71.46

-- URL Was:
http://ir.uz.ac.zw:8080/jspui/handle/10646/184/browse?type=title&sort_by=1&o
rder=ASC&rpp=15&etal=25&submit_browse=Update
-- Method: GET
-- Parameters were:
-- etal: "25"
-- order: "ASC"
-- submit_browse: "Update"
-- sort_by: "1"
-- type: "title"
-- rpp: "15"

Exception:
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
error Timeout waiting for idle object
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.ja
va:114)
at
org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:
588)
at org.dspace.core.Context.(Context.java:95)
at org.dspace.app.webui.util.UIUtil.obtainContext(UIUtil.java:98)
at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java
:100)
at
org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206)
at
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServ
letFilter.java:78)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102
)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPoo
l.java:958)
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.ja
va:106)
... 22 more

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Moving collection

2011-03-31 Thread Claudia Jürgen

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:
update community2collection set community_id=NewCommunityID where 
community_id=OldCommunityID and collection_id=CollectionID;
The run [dspace]/bin/dspace -index-update.

Hope that helps

Claudia Jürgen


Am 31.03.2011 09:33, schrieb Webshet, Sisay (ILRI):
> 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 anybody assists me.
>
>
>
> Thanks you
>
> Sisay
>
>
>
>
>
>
>
>
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>
>
>
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech

-- 
Claudia Juergen
Universitaetsbibliothek Dortmund
Eldorado
0231/755-4043
https://eldorado.tu-dortmund.de/

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] ERROR org.dspace.kernel.DSpaceKernelManager

2011-03-31 Thread Mark Diggory

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  wrote:
> Hi all,
>
> I 've intalled dspace 1.7.0 and I get this error in the logs file
>
> ERROR org.dspace.kernel.DSpaceKernelManager @ WARN Failed to unregister the
> MBean:
> org.dspace:name=6178ac5f-319b-4945-83a7-5f3bda7291d6,type=DSpaceKernel
>
> did somebody knows the cause?
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>



-- 
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Technologielaan 9 - 3001 Heverlee - Belgium

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Moving collection

2011-03-31 Thread Webshet, Sisay (ILRI)

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 anybody assists me.

 

Thanks you

Sisay

 

 

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] (no subject)

2011-03-31 Thread Webshet, Sisay (ILRI)

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 anybody assists me.

 

Thanks you

Sisay

 

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] Okay to use PostgreSQL 8.4.7 with DSpace 1.6.2?

2011-03-31 Thread Bram Luyten

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 - Carlsbad, CA 92010 - USA

atmire.com - Institutional Repository Solutions


On Wed, Mar 30, 2011 at 7:24 PM, Jim Coble  wrote:

> We are currently running DSpace 1.6.2 and PostgreSQL 8.1.22.  In
> preparation for upgrading DSpace to 1.7.1, I see that we also need to
> upgrade PostgreSQL (since PostgreSQL versions prior to 8.2 are not supported
> for DSpace 1.7.1).  If possible, I'd like to go ahead and upgrade PostgreSQL
> as a separate step prior to the DSpace 1.7.1 upgrade if PostgreSQL 8.4.7
> works okay with DSpace 1.6.2.  Anyone have any experience with DSpace 1.6.2
> and PostgreSQL 8.4.7?
> Thanks.
> --Jim
>
> 
> Jim Coble
> Core Services Technical Lead and Program Coordinator
> Information Technology Services
> Perkins Library
> Email: jim.co...@duke.edu
> Voice: 919-660-5974  Fax: 919-668-2578
> Box 90196, Duke University
> Durham, NC 27708-0196
> 
>
>
>
>
> --
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Re: [Dspace-tech] custom metadata deletion question

Re: [Dspace-tech] (no subject)

[Dspace-tech] custom metadata deletion question

[Dspace-tech] Messages.properties doesn't exist

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Enable Metadata Import Menu under Admin Login

Re: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection pool(resultSetTTL)

Re: [Dspace-tech] Solr and 403s

Re: [Dspace-tech] Enable Metadata Import Menu under Admin Login

Re: [Dspace-tech] Solr and 403s

[Dspace-tech] Enable Metadata Import Menu under Admin Login

[Dspace-tech] Solr and 403s

Re: [Dspace-tech] login page trigger ..

Re: [Dspace-tech] login page trigger ..

[Dspace-tech] FW: DSpace: Internal Server Error

Re: [Dspace-tech] Moving collection

Re: [Dspace-tech] ERROR org.dspace.kernel.DSpaceKernelManager

[Dspace-tech] Moving collection

[Dspace-tech] (no subject)

Re: [Dspace-tech] Okay to use PostgreSQL 8.4.7 with DSpace 1.6.2?

24 matches

Site Navigation

Mail list logo

Footer information