Re: [dspace-tech] Error Upgrading DSPACE 5.2 to 6.2

[Tim Donohue]

Hello,

The error sounds as though the libraries (JARs) from DSpace 6 are not
properly installed... OR  possibly you have some DSpace 5 related libraries
that are conflicting with DSpace 6 libraries.

You may wish to look to ensure the "dspace-api-6.2.jar" exists in your
DSpace "lib" directory ([dspace]/lib/), and the "dspace-api-5.2.jar" does
*not* exist.   It's also possible that your "mvn -U clean package" rebuild
of DSpace 6.2 did complete successfully (step #5 in the upgrade process) in
some manner. So, you may wish to try and rebuild DSpace 6.2 and run "ant
update" again.

https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace

Good luck. Let us know if you figure out the issue.

- Tim

On Thu, Jan 11, 2018 at 11:52 AM Tadeu Alves  wrote:

> *Hello Everyone,*
>
> *Following the documentation from:
> "https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
> " and
> "https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2
> "*
>
> *After doing an ant update i got the following errors:*
>
>
>
> [java] Failure during kernel init: Failed to startup the DSpace Service
> Manager: failure starting up spring service manager: Error creating bean
> with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor':
> Injection of autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: protected org.dspace.content.service.ItemService
> org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type [org.dspace.content.service.ItemService] found for
> dependency: expected at least 1 bean which qualifies as autowire candidate
> for this dependency. Dependency annotations:
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>  [java] java.lang.RuntimeException: Failed to startup the DSpace
> Service Manager: failure starting up spring service manager: Error creating
> bean with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor':
> Injection of autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: protected org.dspace.content.service.ItemService
> org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type [org.dspace.content.service.ItemService] found for
> dependency: expected at least 1 bean which qualifies as autowire candidate
> for this dependency. Dependency annotations:
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>  [java] at
> org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:231)
>  [java] at
> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:153)
>  [java] at
> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128)
>  [java] at
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49)
>  [java] Caused by: java.lang.IllegalStateException: failure starting
> up spring service manager: Error creating bean with name
> 'org.dspace.app.requestitem.RequestItemAuthorExtractor': Injection of
> autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: protected org.dspace.content.service.ItemService
> org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type [org.dspace.content.service.ItemService] found for
> dependency: expected at least 1 bean which qualifies as autowire candidate
> for this dependency. Dependency annotations:
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>  [java] at
> org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:215)
>  [java] ... 3 more
>  [java] Caused by:
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor':
> Injection of autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: protected org.dspace.content.service.ItemService
> org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type [org.dspace.content.service.ItemService] found for
> dependency: expected at least 1 bean which qualifies as autowire candidate
> for this dependency. Dependency annotations:
> {@

Re: [dspace-tech] Re: IOException in yearly Solr sharding

[Terry Brady]

Alan,

The issue that you are reporting does not sound like the same issue that
was addressed in DSpace 5.7 and 6.1.

In DSpace 6.0, running the sharding process prevented tomcat from starting
up properly.  While addressing that serious bug, a number of smaller issues
related to statistics import and export were addressed.  It was very
difficult to re-test the sharding process without first fixing the
statistics import and export tools.  I ported the fixes to those tools into
DSpace 5.7.

It is interesting that you see that a new shard is created.  Does that new
shard contain any records?  Are you able to query it in the solr admin
console?

The following fix https://jira.duraspace.org/browse/DS-3458 might make the
process more tolerant if you attempt to re-run the sharding process after a
new shard is in place.

Terry


On Wed, Jan 10, 2018 at 11:50 PM, Alan Orth  wrote:

> Hi, Christian. I just tried again with 4096m heap size and the error is
> the same. I think the problem is indeed related to the Solr optimistic
> concurrency version conflicts that are addressed in DSpace 5.7 and DSpace
> 6.1.
>
> - 5.7: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.7+Status
> - 6.1: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+6.1+Status
>
> Thanks,
>
> On Thu, Jan 11, 2018 at 9:13 AM Christian Scheible <
> christian.schei...@uni-konstanz.de> wrote:
>
>> Hi Alan,
>>
>> have you tried increasing the Java Heap Space?
>> On my local development machine (DSpace 6.2) the command did not run when
>> Heap Space was only 1 GB but did work with 4GB.
>>
>> Like this:
>> sudo -u tomcat7 JAVA_OPTS="-Xmx4024M -Xms1024M -Dfile.encoding=UTF-8"
>> /opt/dspace-kops/bin/dspace stats-util -s
>>
>> Regards
>>
>> Christian
>>
>>
>> Am 11.01.2018 um 08:04 schrieb Alan Orth:
>>
>> @Mark, I looked in DSpace's solr.log and see that the new Solr core is
>> created, then it does some stuff and eventually closes it without an error.
>> Neither Tomcat's catalina.out nor localhost.log have any errors around the
>> time I attempted to shard on my local development machine. There might be a
>> hint here in Tomcat's localhost_access_log, though:
>>
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET /solr/statistics/select?q=
>> type%3A2+AND+id%3A1&wt=javabin&version=2 HTTP/1.1" 200 107
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET
>> /solr/statistics/select?q=*%3A*&rows=0&facet=true&facet.
>> range=time&facet.range.start=NOW%2FYEAR-18YEARS&facet.
>> range.end=NOW%2FYEAR%2B0YEARS&facet.range.gap=%2B1YEAR&
>> facet.mincount=1&wt=javabin&version=2 HTTP/1.1" 200 447
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET /solr/admin/cores?action=
>> STATUS&core=statistics-2016&indexInfo=true&wt=javabin&version=2
>> HTTP/1.1" 200 76
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET /solr/admin/cores?action=
>> CREATE&name=statistics-2016&instanceDir=statistics&
>> dataDir=%2FUsers%2Faorth%2Fdspace%2Fsolr%2Fstatistics-
>> 2016%2Fdata&wt=javabin&version=2 HTTP/1.1" 200 63
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET
>> /solr/statistics/select?csv.mv.separator=%7C&q=*%3A*&fq=
>> time%3A%28%5B2016%5C-01%5C-01T00%5C%3A00%5C%3A00Z+TO+
>> 2017%5C-01%5C-01T00%5C%3A00%5C%3A00Z%5D+NOT+2017%5C-01%5C-
>> 01T00%5C%3A00%5C%3A00Z%29&rows=1&wt=csv HTTP/1.1" 200 2137630
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "GET
>> /solr/statistics/admin/luke?show=schema&wt=javabin&version=2 HTTP/1.1"
>> 200 16253
>> 127.0.0.1 - - [10/Jan/2018:10:51:19 +0200] "POST
>> /solr//statistics-2016/update/csv?commit=true&softCommit=
>> false&waitSearcher=true&f.previousWorkflowStep.split=
>> true&f.previousWorkflowStep.separator=%7C&f.previousWorkflowStep.
>> encapsulator=%22&f.actingGroupId.split=true&f.
>> actingGroupId.separator=%7C&f.actingGroupId.encapsulator=%
>> 22&f.containerCommunity.split=true&f.containerCommunity.separator=%7C&f.
>> containerCommunity.encapsulator=%22&f.range.
>> split=true&f.range.separator=%7C&f.range.encapsulator=%22&f.
>> containerItem.split=true&f.containerItem.separator=%7C&f.
>> containerItem.encapsulator=%22&f.p_communities_map.split=
>> true&f.p_communities_map.separator=%7C&f.p_communities_
>> map.encapsulator=%22&f.ngram_query_search.split=true&f.
>> ngram_query_search.separator=%7C&f.ngram_query_search.encapsulator=%22&f.
>> containerBitstream.split=true&f.containerBitstream.separator=%7C&f.
>> containerBitstream.encapsulator=%22&f.owningItem.split=true&f.owningItem.
>> separator=%7C&f.owningItem.encapsulator=%22&f.actingGroupParentId.split=
>> true&f.actingGroupParentId.separator=%7C&f.actingGroupParentId.
>> encapsulator=%22&f.text.split=true&f.text.separator=%7C&f.
>> text.encapsulator=%22&f.simple_query_search.split=
>> true&f.simple_query_search.separator=%7C&f.simple_query_
>> search.encapsulator=%22&f.owningComm.split=true&f.
>> owningComm.separator=%7C&f.owningComm.encapsulator=%22&f.
>> owner.split=true&f.owner.separator=%7C&f.owner.encapsulator=%22&f.
>> filterquery.split=true&f.filterquery.separator=%7

[dspace-tech] Error Upgrading DSPACE 5.2 to 6.2

[Tadeu Alves]

*Hello Everyone,*

*Following the documentation from: 
"https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace"; and 
"https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2"*

*After doing an ant update i got the following errors:*



[java] Failure during kernel init: Failed to startup the DSpace Service 
Manager: failure starting up spring service manager: Error creating bean 
with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor': 
Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire 
field: protected org.dspace.content.service.ItemService 
org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested 
exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
qualifying bean of type [org.dspace.content.service.ItemService] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: 
{@org.springframework.beans.factory.annotation.Autowired(required=true)}
 [java] java.lang.RuntimeException: Failed to startup the DSpace 
Service Manager: failure starting up spring service manager: Error creating 
bean with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor': 
Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire 
field: protected org.dspace.content.service.ItemService 
org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested 
exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
qualifying bean of type [org.dspace.content.service.ItemService] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: 
{@org.springframework.beans.factory.annotation.Autowired(required=true)}
 [java] at 
org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:231)
 [java] at 
org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:153)
 [java] at 
org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128)
 [java] at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49)
 [java] Caused by: java.lang.IllegalStateException: failure starting up 
spring service manager: Error creating bean with name 
'org.dspace.app.requestitem.RequestItemAuthorExtractor': Injection of 
autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire 
field: protected org.dspace.content.service.ItemService 
org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested 
exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
qualifying bean of type [org.dspace.content.service.ItemService] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: 
{@org.springframework.beans.factory.annotation.Autowired(required=true)}
 [java] at 
org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:215)
 [java] ... 3 more
 [java] Caused by: 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'org.dspace.app.requestitem.RequestItemAuthorExtractor': 
Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire 
field: protected org.dspace.content.service.ItemService 
org.dspace.app.requestitem.RequestItemMetadataStrategy.itemService; nested 
exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
qualifying bean of type [org.dspace.content.service.ItemService] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: 
{@org.springframework.beans.factory.annotation.Autowired(required=true)}
 [java] at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:298)
 [java] at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1148)
 [java] at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
 [java] at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
 [java] at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
 [java] at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
 [j

[dspace-tech] RE: initial questions step

[Graham Faulkner]

Hi again,

Just getting back to this after a few month hiatus.  Re: the second idea I 
outline below, I understand that I need to assign a metadata schema, element 
(and optional qualifier) for any checkbox.

Is it possible to create a page where it is just text and the submitter can 
then just click on proceed to continue, and not have to save the decision in 
the database?

My goal is to have a page where the author/submitter sees the link to the 
official pre-submission checklist for their submission content type (thesis, 
article, etc.) before they start the submission.

Any pointers are appreciated.

Cheers,

Graham

From: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] On 
Behalf Of Graham Faulkner
Sent: November 14, 2017 2:03 PM
To: dspace-tech@googlegroups.com
Subject: [dspace-tech] initial questions step

Hi there,

[We’re running DSpace 5.5 XMLUI Mirage2 on Linux.]

Re: the Initial Questions Step, it seems like there is only one set of 
questions that can optionally be used for any submission workflow.  Is there a 
way to have a custom set of questions that is tailored for a workflow?

Or would it be better to create a new Page 1 for the respective collection 
workflows (i.e. faculty article submission; grad theses) and have required 
checkboxes that indicate the user has completed the various required tasks 
before submitting their item?

This second option sounds a lot simpler, but I may be missing something that 
would make it a terrible idea!

Cheers,

Graham


-
Graham Faulkner
Information Technology Specialist/Developer
Digital Initiatives, Library
University of Waterloo
Waterloo, Ontario N2L 3G1 CANADA
519-888-4567 x32461
graham.faulk...@uwaterloo.ca

--
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Pubmed and Web of Science citations

[gonzalo perl]

Hello everybody

I am trying to get the citacions of Pubmed and wos of science. I run the 
scripts

dspace dsrun org.dspace.app.cris.metrics.pmc.script.RetrieveCitationInPMC

dspace dsrun org.dspace.app.cris.metrics.wos.script.ScriptRetrieveCitation

The scripts run without problems, but i can not get the badges

I have checked the database cris_metrics and and i have content in 
metriccount column. I can see the 937 citations in Scopus that i can see 
the badge in Dspace. I can also see the 211 citations of pubmed in 
metriccount column, but i can not see the badge.


Cris.cfg configuration

### METRICS ###
##SCOPUS##
ametrics.elsevier.scopus.enabled = true 
ametrics.elsevier.scopus.endpoint = 
http://api.elsevier.com/content/search/scopus
ametrics.elsevier.scopus.apikey = *my apikey*
##
##WOS##
ametrics.thomsonreuters.wos.enabled = true
ametrics.thomsonreuters.wos.endpoint = https://ws.isiknowledge.com/cps/xrpc
##
##GOOGLE SCHOLAR##
ametrics.google.scholar.enabled = true
##
##ALTMETRIC##
ametrics.altmetric.enabled = true
##GOOGLE SCHOLAR##
ametrics.google.scholar.enabled = true
##
## the following settings are used to retrieve item on solr search engine
ametrics.identifier.pmid = dc.identifier.pmid
#scopus id
ametrics.identifier.eid = dc.identifier.scopus
ametrics.identifier.doi = dc.identifier.doi
#wos id
ametrics.identifier.ut = dc.identifier.isi
###

### PUBMED ###
pmc.enabled = true 
pmc.server = http://localhost:8080/solr/pmc


Any idea?

Cheers
Gonzalo

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Submission Problem in DSpace 6.2

[Tim Donohue]

Hi George,

Glad to hear you've been able to verify this.  We've been analyzing DS-3775
for possible inclusion in 6.3...but needed verification that others are
seeing this same behavior.  So, it's helpful that you've verified the issue.

I'll add this to our to-do list for 6.3. I don't have a volunteer lined up
to fix it yet, so if any here is "listening" and interested, please let us
know and/or create a PR to fix it (and we'll review and merge it).  All
development in DSpace happens via volunteers, so it's now just a matter of
finding someone interested in digging in on this problem (I've already
linked some other related tickets to DS-3775 that may provide clues).

https://jira.duraspace.org/browse/DS-3775

- Tim

On Thu, Jan 11, 2018 at 8:30 AM George Kozak  wrote:

> Tim:
>
> That's it, exactly!  I was trying to narrow down the problem at my site,
> and thought it was tied to Collections with Default Read access restricted,
> but it turns out, those are collections with logos.  Once I removed the
> logos, the problem went away.  So, will
> https://jira.duraspace.org/browse/DS-3775 be fixed in DSpace 6.3?  And if
> so, when can we expect 6.3 or a patch?
> Thanks!
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924 <(607)%20255-8924>
> g...@cornell.edu
>
> On Wed, Jan 10, 2018 at 12:00 PM, Tim Donohue 
> wrote:
>
>> Hi George,
>>
>> Your description here sounds very similar (or very closely related) to
>> this ticket that has already been logged:
>> https://jira.duraspace.org/browse/DS-3775
>>
>> If this is the same (or similar) behavior to what you are seeing, could
>> you add comments to the ticket on how you've been able to reproduce this?
>> As you'll see in the ticket, we're still trying to narrow down how to
>> reproduce this, and whether it's now been fixed in the latest codebase
>> (pre-6.3 code).  So, more eyes / feedback could be very helpful here.
>>
>> - Tim
>>
>> On Tue, Jan 9, 2018 at 4:05 PM George Kozak  wrote:
>>
>>> Hi...
>>>
>>> Back in late November, I reported a problem with Submissions in DSpace
>>> 6.2.  The problem was that when someone submitted an item the following
>>> error appeared: "could not initialize proxy - no Session".  The item
>>> submission went through, but the submitter saw this error message appear.
>>>
>>> I think I may have figured out what is causing this error.  It appears
>>> from my testing that if someone submits to a collection that has restricted
>>> Default Read Access, then the error happens.  So far, I have been able to
>>> duplicate this error under those conditions.  If someone could verify my
>>> results, then a JIRA issue could be written up.
>>> Thanks!
>>>
>>> --
>>> ***
>>> George Kozak
>>> Digital Library Specialist
>>> Cornell University Library - IT
>>> 218 Olin Library
>>> Cornell University
>>> Ithaca, NY 14853
>>> 607-255-8924 <(607)%20255-8924>
>>> g...@cornell.edu
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech+unsubscr...@googlegroups.com.
>>> To post to this group, send email to dspace-tech@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924 <(607)%20255-8924>
> g...@cornell.edu
>


-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Submission Problem in DSpace 6.2

[George Kozak]

Tim:

That's it, exactly!  I was trying to narrow down the problem at my site,
and thought it was tied to Collections with Default Read access restricted,
but it turns out, those are collections with logos.  Once I removed the
logos, the problem went away.  So, will https://jira.duraspace.org/
browse/DS-3775 be fixed in DSpace 6.3?  And if so, when can we expect 6.3
or a patch?
Thanks!
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924 <(607)%20255-8924>
g...@cornell.edu

On Wed, Jan 10, 2018 at 12:00 PM, Tim Donohue 
wrote:

> Hi George,
>
> Your description here sounds very similar (or very closely related) to
> this ticket that has already been logged:
> https://jira.duraspace.org/browse/DS-3775
>
> If this is the same (or similar) behavior to what you are seeing, could
> you add comments to the ticket on how you've been able to reproduce this?
> As you'll see in the ticket, we're still trying to narrow down how to
> reproduce this, and whether it's now been fixed in the latest codebase
> (pre-6.3 code).  So, more eyes / feedback could be very helpful here.
>
> - Tim
>
> On Tue, Jan 9, 2018 at 4:05 PM George Kozak  wrote:
>
>> Hi...
>>
>> Back in late November, I reported a problem with Submissions in DSpace
>> 6.2.  The problem was that when someone submitted an item the following
>> error appeared: "could not initialize proxy - no Session".  The item
>> submission went through, but the submitter saw this error message appear.
>>
>> I think I may have figured out what is causing this error.  It appears
>> from my testing that if someone submits to a collection that has restricted
>> Default Read Access, then the error happens.  So far, I have been able to
>> duplicate this error under those conditions.  If someone could verify my
>> results, then a JIRA issue could be written up.
>> Thanks!
>>
>> --
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924 <(607)%20255-8924>
>> g...@cornell.edu
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] cli way of changing dc.identifier.uri for all items?

[Tony Brian Albers]

Darn, I think I was celebrating too soon.

In our dspace/log, cocoon.log files have increased from around 
150mbytes/day to 3,5gigs/day.

Errors are like these:

  2018-01-11 13:45:46,947 INFO  org.apache.cocoon.i18n.XMLResourceBundle 
  - Bundle 
 
not loaded: Source URI not found

2018-01-11 13:45:46,828 ERROR cocoon.handled  - Unable to locate sitemap
 at  - 
file:///data/dspace/webapps/ROOT/sitemap.xmap:595
:56
 at  - 
file:///data/dspace/webapps/ROOT/sitemap.xmap:594:50


What we have done is:

changed hostname in dspace's local.cfg
changed dc.identifier.uri in postgres as per below.

Any ideas?

/tony

On 01/09/2018 11:15 AM, Tony Brian Albers wrote:
> Hi Tom,
> 
> That worked like a charm.
> 
> Thanks!
> 
> /tony
> 
> On 01/09/2018 10:24 AM, Tom Desair wrote:
>> Hi Tony,
>>
>> I usually do this with a SQL query (for DSpace 5 or 6, on PostgreSQL):
>>
>>  update metadatavalue
>>  set text_value = regexp_replace(text_value, 'http://*my-old.url.org
>>  *', 'https://*my-new.url.org
>>  *') where metadata_field_id IN (select
>>  metadata_field_id from metadatafieldregistry where element =
>>  'identifier' and qualifier = 'uri');
>>
>> After the update you need to reindex the discovery search index and the
>> oai index:
>>
>>* bin/dspace index-discovery -f
>>* bin/dspace oai import -c
>>
>> Best regards,
>>
>> Tom
>>
>> logo Tom Desair
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>> Gaston Geenslaan 14, Leuven 3001, Belgium
>> www.atmire.com
>> 
>>
>>
>> 2018-01-09 9:29 GMT+01:00 Tony Brian Albers mailto:t...@kb.dk>>:
>>
>>  Thanks Christian, but it doesn't work.
>>
>>  When I change the dc.identifier.uri field and import, it just says: "
>>  There were no changes detected"
>>
>>  Really odd.
>>
>>  Any suggestions?
>>
>>  /tony
>>
>>
>>  On 01/08/2018 11:01 AM, Christian Scheible wrote:
>>  > Hi Tony,
>>  >
>>  > yes there is. Just export, edit and import again.
>>  > See : 
>> https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing
>>  
>>  > for details.
>>  >
>>  > Kind Regards
>>  > Christian
>>  >
>>  > Am 08.01.2018 um 10:58 schrieb Tony Brian Albers:
>>  >> Hi Guys,
>>  >>
>>  >> We've had to change domain name on one of our installations, is 
>> there a
>>  >> way using the command-line to change the metadata for all items? I'd
>>  >> like to change the dc.identifier.uri
>>  >>
>>  >> TIA,
>>  >>
>>  >> /tony
>>  >
>>  >
>>
>>
>>  --
>>  Tony Albers
>>  Systems administrator, IT-development
>>  Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark.
>>  Tel: +45 2566 2383  / +45 8946 2316
>>  
>>
>>  --
>>  You received this message because you are subscribed to the Google
>>  Groups "DSpace Technical Support" group.
>>  To unsubscribe from this group and stop receiving emails from it,
>>  send an email to dspace-tech+unsubscr...@googlegroups.com
>>  .
>>  To post to this group, send email to dspace-tech@googlegroups.com
>>  .
>>  Visit this group at https://groups.google.com/group/dspace-tech
>>  .
>>  For more options, visit https://groups.google.com/d/optout
>>  .
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to dspace-tech+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to dspace-tech@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 


-- 
Tony Albers
Systems administrator, IT-development
Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark.
Tel: +45 2566 2383 / +45 8946 2316

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Postgresql and metadatafields

[Paul Münch]

Hello,

a simple way to update metadata is using the "export metadata" (UI) from
a collection to csv, edit the csv file and reimport this. But you could
create a function collection2items alike the other functions, too.
For example:

CREATE OR REPLACE FUNCTION ds6_collectionhandle2item (varchar) RETURNS
setof uuid

AS 'SELECT item_id FROM collection2item

    WHERE collection2item.collection_id = (

          SELECT resource_id FROM handle

          WHERE handle.resource_type_id = 3 AND handle = $1)'

LANGUAGE SQL STABLE RETURNS NULL ON NULL INPUT;

Best regards,
Paul

Am 11.01.2018 um 10:15 schrieb cez.dsp...@gmail.com:
> Hello,
>
>
> I have a question is there any way to retrieve field like
> "dc.description.citation" from all items in specific collection ? 
> I need to update that field and other one with not static information,
> thats why I would refer a way in SQL.
>
> https://wiki.duraspace.org/display/DSPACE/Helper+SQL+functions+for+DSpace+6
> , found these helpers but I don't see any for collection2items function :/
>
> OS: Debian
> Dspace: 6.2
> Postgres: 9.4.1
>
>
> Thanks for any advice :)
> -- 
> You received this message because you are subscribed to the Google
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to dspace-tech+unsubscr...@googlegroups.com
> .
> To post to this group, send email to dspace-tech@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.

-- 
Philipps-Universität Marburg | UB
Digitale Dienste | Wilhelm-Röpke-Straße 6 | 08A09
Tel. 06421/28-24624 | 
--

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[dspace-tech] Re: [Dspace-tech] Start and close handle server

[Rukaya Johaadien]

Hi Manuel,

I have the same error:
"2018/01/11 09:45:32 CAT" 25 Started new run.
Saving global values to: C:\Users\johaadienr\.handle\root_info
"2018/01/11 09:45:36 CAT" 50 unspecified max_handlers count, using default: 
200
"2018/01/11 09:45:36 CAT" 50 unspecified max_handlers count, using default: 
200
"2018/01/11 09:45:36 CAT" 50 unspecified max_handlers count, using default: 
200
"2018/01/11 09:45:36 CAT" 25 Shutting down server at Thu Jan 11 09:45:36 
CAT 2018
"2018/01/11 09:45:36 CAT" 75 class net.handle.server.HdlUdpInterface: Error 
handling request: java.net.SocketException: socket closed
"2018/01/11 09:45:36 CAT" 75 class net.handle.server.HdlTcpInterface: Error 
handling request: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native 
Method)
at java.net.DualStackPlainDatagramSocketImpl.receive0(Unknown Source)
at java.net.AbstractPlainDatagramSocketImpl.receive(Unknown Source)
at java.net.DatagramSocket.receive(Unknown Source)


What did you do to get this fixed?
Thanks
Rukaya


On Wednesday, 26 August 2015 18:59:46 UTC+2, Manuel Hidalgo wrote:
>
> Dear, 
>
> We are running an instruction for start the handle server, but immediately 
> the close the server.  We are using windows server 2008 R2.
>
> [dspace]\bin\dspace dsrun net.handle.server.Main [dspace]\handle-server
>
> Someone know the problem with the ejecution of the handle server.
>
> This is the error log file.
>
> "2014/03/04 *01:59:38* CST" 25 *Started new run.*
> "2014/03/04 01:59:38 CST" 50 unspecified max_handlers count, using 
> default: 200
> "2014/03/04 01:59:38 CST" 50 unspecified max_handlers count, using 
> default: 200
> "2014/03/04 01:59:38 CST" 50 unspecified max_handlers count, using 
> default: 200
> *Saving global values to: C:\Users\mhidalgo\.handle\root_info*
> "2014/03/04 *01:59:38* CST" 25 *Shutting down server *at Tue Mar 04 
> 13:59:38 CST 2014
> "2014/03/04 01:59:38 CST" 75 class net.handle.server.HdlUdpInterface: 
> Error handling request: java.net.SocketException: socket closed
> Error (java.lang.ThreadDeath) writing "class 
> net.handle.server.HdlHttpInterface: Error handling request: 
> java.net.SocketException: socket closed" to error log.
> java.net.SocketException: socket closed
> at java.net.DualStackPlainSocketImpl.accept0(Native Method)
> at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
> at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
> at java.net.PlainSocketImpl.accept(Unknown Source)
> at java.net.ServerSocket.implAccept(Unknown Source)
> at java.net.ServerSocket.accept(Unknown Source)
> at 
> net.handle.server.HdlHttpInterface.serveRequests(HdlHttpInterface.java:217)
> at net.handle.server.NetworkInterface.run(NetworkInterface.java:150)
> at java.lang.Thread.run(Unknown Source)
>
> Thank you
> Manuel
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Postgresql and metadatafields

[cez . dspace]

Hello,


I have a question is there any way to retrieve field like 
"dc.description.citation" from all items in specific collection ? 
I need to update that field and other one with not static information, 
thats why I would refer a way in SQL.

https://wiki.duraspace.org/display/DSPACE/Helper+SQL+functions+for+DSpace+6 
, found these helpers but I don't see any for collection2items function :/

OS: Debian
Dspace: 6.2
Postgres: 9.4.1


Thanks for any advice :)

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Error build dspace CRIS 6RC2

[gonzalo perl]

Dear  Luigi Andrea

Yes. Now it ís running with out problems.

Regards
Gonzalo

El jueves, 4 de enero de 2018, 11:48:09 (UTC), Pascarelli Luigi Andrea 
escribió:
>
> Dear Gonzalo,
>
> instead download the zip file of the RC2 distribution please clone the 
> branch https://github.com/4Science/DSpace/tree/dspace-6_x_x-cris using 
> git tool. After clone the branch with git, rebuild using "mvn clean -U 
> package" and try the ant task.
>
> Let me know.
>
> Regards,
>
> Luigi Andrea
>
> Il 04/01/2018 12:37, gonzalo perl ha scritto:
>
> Hi Luigi Andrea
>
> When run "anf fresh_install" command, i get the following error:
>
> 
>
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 99.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 65.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 82.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 97.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 108.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,888 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 62.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,898 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 71.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 87.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 121.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 154.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 87.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 66.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 96.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 76.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,928 WARN  
> org.hibernate.hql.internal.ast.HqlSqlWalker @ [DEPRECATION] Encountered 
> positional parameter near line 1, column 99.  Positional parameter are 
> considered deprecated; use named parameters or JPA-style positional 
> parameters instead.
>  [java] 2018-01-04 11:33:11,938 WARN  
> org.hi