[dspace-tech] NullPointerException when creating a root community

2017-10-31 Thread karma . sometimes . hurts 
Hi,

We're running DSpace 6.2 and we're having an issue creating root 
communities (on the top of the hierarchy). Immediately after hitting the 
"Create" button, a NullPointerException is shown. The strange thing is that 
there are no logs anywhere in the 'logs' directory nor in the tomcat logs 
when the exception pops-up. I could get Cocoon and Java logs though from 
the web browser, which I'm attaching.

We can just reproduce it when it comes to create a root community, no 
issues when creating subcommunities nor collections.

Could someone give some pointers on why is this happening and possibly how 
to solve it?

Thanks in advance

James

-- 
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.
org.apache.cocoon.ProcessingException: Sitemap: error calling continuation
at  - resource://aspects/Administrative/sitemap.xmap:254:38
at  - 
resource://aspects/Administrative/sitemap.xmap:253:67
at  - resource://aspects/Administrative/sitemap.xmap:252:43
at  - 
resource://aspects/Administrative/sitemap.xmap:128:45
at  - jndi:/localhost/xmlui/aspects/aspects.xmap:89:72
at  - 
jndi:/localhost/xmlui/aspects/aspects.xmap:79:34
at  - 
jndi:/localhost/xmlui/aspects/aspects.xmap:78:36
at  - jndi:/localhost/xmlui/sitemap.xmap:498:100
at  - jndi:/localhost/xmlui/sitemap.xmap:497:49
at  - 
resource://aspects/EPerson/sitemap.xmap:302:31
at  - 
resource://aspects/EPerson/sitemap.xmap:107:38
at  - resource://aspects/EPerson/sitemap.xmap:96:19
at  - 
resource://aspects/Submission/sitemap.xmap:251:38
at  - 
resource://aspects/Submission/sitemap.xmap:107:45
at  - resource://aspects/Submission/sitemap.xmap:104:26
at  - 
resource://aspects/Statistics/sitemap.xmap:236:36
at  - resource://aspects/Statistics/sitemap.xmap:36:19
at  - 
resource://aspects/Workflow/sitemap.xmap:139:38
at  - resource://aspects/Workflow/sitemap.xmap:76:26
at  - 
jndi:/localhost/xmlui/aspects/aspects.xmap:85:34
at  - 
jndi:/localhost/xmlui/aspects/aspects.xmap:84:43
at  - jndi:/localhost/xmlui/aspects/aspects.xmap:83:22
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:165:56
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:162:58
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:156:48
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:152:53
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:141:55
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:139:58
at  - 
jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:134:67
at  - jndi:/localhost/xmlui/themes/STIC/sitemap.xmap:131:37
at  - jndi:/localhost/xmlui/themes/themes.xmap:33:45
at  - 
jndi:/localhost/xmlui/themes/themes.xmap:32:35
at  - jndi:/localhost/xmlui/sitemap.xmap:711:94
at 
org.apache.cocoon.ProcessingException.throwLocated(ProcessingException.java:111)
at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:96)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(Tr

[dspace-tech] solr statistics export incomplete

2017-10-31 Thread Francis Brouns 
Hi all,

we are having problems with our solr indexes, not sure what the cause is. 
In an attempt to restore statistics, I am trying to export the data. 
However, after running solr-export-statistics only some csv files for 
December 2015, some for 2016 and 2017 are created. There should be 
statistics data from 2003 onward. How can I check that the export is 
complete?

We are running DSpace 5.4 jspui on tomcat 7 and java 7. We had converted 
old log files (2003 - 2015) and imported these when upgrading from DSpace 
1.8 to DSpace 5.0 in 2015. At that time and export of statistics seemed to 
export all data. We have not yet sharded core by year.

best wishes,
Francis Brouns
Open Universiteit of the Netherlands


-- 
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] Re: NullPointerException when creating a root community

2017-10-31 Thread karma . sometimes . hurts 
As per what I could see, the exception happens in 
the aspect/administrative/FlowContainerUtils.java file, in the line marked 
with bold:

public static FlowResult processCreateCommunity(Context context, 
> UUID communityID, Request request)
> throws AuthorizeException, IOException, SQLException
> {
> FlowResult result = new FlowResult();
> Community newCommunity;
> if (communityID != null)
> {
> newCommunity = communityService.createSubcommunity(context, 
> communityService.find(context, communityID));
> }
> else
> {
> *newCommunity = communityService.create(null, context);*
> }


Any hints?

Thanks

El martes, 31 de octubre de 2017, 11:47:53 (UTC), karma.some...@gmail.com 
escribió:
>
> Hi,
>
> We're running DSpace 6.2 and we're having an issue creating root 
> communities (on the top of the hierarchy). Immediately after hitting the 
> "Create" button, a NullPointerException is shown. The strange thing is that 
> there are no logs anywhere in the 'logs' directory nor in the tomcat logs 
> when the exception pops-up. I could get Cocoon and Java logs though from 
> the web browser, which I'm attaching.
>
> We can just reproduce it when it comes to create a root community, no 
> issues when creating subcommunities nor collections.
>
> Could someone give some pointers on why is this happening and possibly how 
> to solve it?
>
> Thanks in advance
>
> James
>

-- 
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] Error dspace Jspui/Xmlui

2017-10-31 Thread Leidy Madroñero 
Buenos días a todos

Tengo un problema con las interfaces de dspace que es el siguiente:

SolrCore Initialization Failures

   - *search:* 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/search/data/index
   - *oai:* 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/oai/data/index
   - *authority:* 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/authority/data/index
   - *statistics:* 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/statistics/data/index 

Alguien tuvo este mismo problema? Como se soluciona?


Agradezco sus respuestas.




-- 
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] Replacing a bitstream in DSpace 6.2 using REST

2017-10-31 Thread Evgeni Dimitrov 
I may be wrong, but I expected to replace a bitstream with this line:

curl -v --cookie "JSESSIONID=9EB449E3FCC173204AB14AD189911324" -T mets.xml
http://localhost:8080/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data

It did not happen and I got in different places the following messages:

-
HTTP Status 500 - Internal Server Error

-
127.0.0.1 - - [31/Oct/2017:22:14:38 +0200] "PUT
/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data HTTP/1.1" 500
1082

-
2017-10-31 22:14:38,463 INFO  org.dspace.rest.BitstreamResource @ Updating
bitstream(id=5a286ddc-f138-43ac-afca-3d0a761f5149) data.
2017-10-31 22:14:38,712 INFO  org.dspace.content.BitstreamServiceImpl @
e...@nomail.xx
::update_bitstream:bitstream_id=5a286ddc-f138-43ac-afca-3d0a761f5149
2017-10-31 22:14:38,728 ERROR org.dspace.rest.Resource @ Something get
wrong. Aborting context in finally statement.

Any advice is welcome.



Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
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] Re: Replacing a bitstream in DSpace 6.2 using REST

2017-10-31 Thread Evgeni Dimitrov 
Looks like this is a known bug:

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


and has been fixed on 19.09.2017 - after the release of 6.2 . . .


On Tuesday, October 31, 2017 at 10:32:10 PM UTC+2, Evgeni Dimitrov wrote:
>
> I may be wrong, but I expected to replace a bitstream with this line:
>
> curl -v --cookie "JSESSIONID=9EB449E3FCC173204AB14AD189911324" -T mets.xml 
> http://localhost:8080/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data
>
> It did not happen and I got in different places the following messages:
>
> -
> HTTP Status 500 - Internal Server Error
>
> -
> 127.0.0.1 - - [31/Oct/2017:22:14:38 +0200] "PUT 
> /rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data HTTP/1.1" 500 
> 1082
>
> -
> 2017-10-31 22:14:38,463 INFO  org.dspace.rest.BitstreamResource @ Updating 
> bitstream(id=5a286ddc-f138-43ac-afca-3d0a761f5149) data.
> 2017-10-31 22:14:38,712 INFO  org.dspace.content.BitstreamServiceImpl @ 
> e...@nomail.xx::update_bitstream:bitstream_id=5a286ddc-f138-43ac-afca-3d0a761f5149
> 2017-10-31 22:14:38,728 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
>
> Any advice is welcome.
>
>
>
> 
>  Virus-free. 
> www.avg.com 
> 
>  
> <#CAJc2bOzQr_sGE7k_So_qMGMM1wx8zR1dm+W2LKhgzHLYXLZagQ@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
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] Re: StartSubmissionLookupStep : DOI look up no results

2017-10-31 Thread Jeffrey Turman 
I figured out the problem, at least for my Dspace: 

1. You need an "API key" from Crossref for the OpenURL API. Go here 
, register with the email of 
your organization (where you want to be alerted if bots use your crossref 
form). Now this email address is your API key. You'll get an email 
verification at that email that needs to be opened and a URL for 
verification. 

2. Add the email you just registered to the 
[dspace]/dspace/config/spring/api/bte.xml file in the 
crossRefOnlineDataLoader property "apiKey" value. (at the moment of this 
writing this is line 439.)

3. Rebuild, and the form should work. 

Cheers!


On Monday, November 28, 2016 at 4:57:11 AM UTC-7, infov...@gmail.com wrote:
>
> Hello All
>
> I tried the submission using the Look up and DOI but no results. I tried 
> PubMedID and this works fine. If I do this with an article that has DOI and 
> also PubMedID and I do a DOI look up then it will find it but from PubMed. 
> Do I need to do something to make the DOI look up working? As of now, seems 
> to work only for documents that have DOI and PubmedID
> Cheers
>
>

-- 
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] colection error

2017-10-31 Thread Alejandra Leyvas 
hi, when I try to create a new collection show this error
Excepción:
java.sql.SQLException: Invalid metadata field: [dc.provenance]

I thought that the metadata was missing, but is not the case

What can I do ??? :(

-- 
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.