[dspace-tech] Re: [dspace-community] Multi language description OAI handling

[SamuelOPH]

​Hi Helix,

Thanks a lot for your help.​

2016-02-23 22:08 GMT-03:00 helix84 :

> Please, don't cross-post your questions to multiple mailing lists. Pick
> one mailing list and post only there.

​
I'm sorry, it wasn't my intent at all, this email got sent about two days
ago, when I sent both emails i didn't get any response (it wasn't appearing
on the history). I think something was wrong with the list, that's why i
sent to both, actually it was a surprise seeing that both my emails got
sent two days latter.

Samuel Henrique O. P. [samueloph]
Técnico em Informática - UTFPR [2012].
Estudante de Engenharia de Computação - UTFPR.

-- 
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: [dspace-community] Multi language description OAI handling

[helix84]

Please, don't cross-post your questions to multiple mailing lists. Pick one
mailing list and post only there.

I filed a bug here:
https://jira.duraspace.org/browse/DS-3077

And prepared a fix here:
https://github.com/DSpace/DSpace/pull/1318

If you just want to grab the fixed qdc.xml file, you can get it here:
https://raw.githubusercontent.com/DSpace/DSpace/c8ed890f3ed79de039c05210f1b30672658d0e82/dspace/config/crosswalks/oai/metadataFormats/qdc.xsl


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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] does Dspace track changes in deposited items?

[ibraheem alsadi]

Thank you helix84 very much , you reply really helpful , thanks again 
Ibraheem

On Friday, February 19, 2016 at 11:13:41 PM UTC, helix84 wrote:
>
> DSpace does not track changes. 
>
> It does take a brief note of _some_ changes and record them in the 
> dc.description.provenance field which you can only see when logged in 
> as administrator. 
>
> There is also a possibility to create a new version of an item, 
> keeping both the old and the new one, but this is done through an 
> explicit user action. See [1]. 
>
> [1] https://wiki.duraspace.org/display/DSDOC5x/Item+Level+Versioning 
>
>
> Regards, 
> ~~helix84 
>
> Compulsory reading: DSpace Mailing List Etiquette 
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette 
>

-- 
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: Something wrong with REST API - DSpace 5.4

[Evgeni Dimitrov]

Well, not literary this - it will not be executed there - but this is the 
idea - to close the context after normal execution.

On Tuesday, February 23, 2016 at 11:37:15 PM UTC+2, Faiyaz Ahmed wrote:
>
> I was just about to submit this post and you done it. 
>
> I'm facing same while access via REST API. URL for the rest api is :  
> http://localhost:8080/rest/handle/3015/23
>
> Tomcat Logs : 
>
> 192.168.163.1 - - [24/Feb/2016:00:34:33 +0300] "GET /rest/handle/3015/23 
> HTTP/1.1" 500 -
> 192.168.163.1 - - [24/Feb/2016:00:34:36 +0300] "GET /rest/handle/3015/23 
> HTTP/1.1" 500 -
>
> Dspace 5.4 version logs :
>
>
> 2016-02-24 00:34:33,783 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
> 2016-02-24 00:34:36,643 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
>
>
> Please update if any one have idea on this error.
>
>
>
> On Tuesday, February 23, 2016 at 9:03:39 PM UTC+5, Evgeni Dimitrov wrote:
>>
>> I have used REST API with DSpace 5.2 and Windows. Now I am trying with 
>> DSpace 5.4 and Linux. Doing not the same but very similar thing. Trying to 
>> get a community by handle.
>>
>> I am getting in the DSpace log
>>
>> 2016-02-23 17:24:12,947 INFO  org.dspace.rest.RestIndex @ REST Login 
>> Success for user: @
>> 2016-02-23 17:24:12,973 INFO  org.dspace.rest.HandleResource @ DSO Lookup 
>> by handle: [nls] / [94] got result of: COMMUNITY_17
>> 2016-02-23 17:24:13,091 ERROR org.dspace.rest.Resource @ Something get 
>> wrong. Aborting context in finally statement.
>> 2016-02-23 17:24:13,104 INFO  org.dspace.rest.RestIndex @ REST Logout: 
>> @
>>
>> In the Tomcat log there is more - see bellow.
>>
>> Has anybody any ideas?
>>
>> 
>> 23-Feb-2016 17:24:13.091 SEVERE [http-nio-8080-exec-4] 
>> com.sun.jersey.spi.container.ContainerResponse.logException Mapped 
>> exception to response: 500 (Internal Server Error)
>>  javax.ws.rs.WebApplicationException
>> at org.dspace.rest.Resource.processFinally(Resource.java:169)
>> at org.dspace.rest.HandleResource.getObject(HandleResource.java:74)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at 
>> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>> at 
>> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>> at 
>> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>> at 
>> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>> at 
>> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>> at 
>> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>> at 
>> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>> at 
>> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> at 
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> at 
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
>> at 
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:10

[dspace-tech] Re: Something wrong with REST API - DSpace 5.4

[Evgeni Dimitrov]

Yes, see my other post "A bug in REST API introduced in 5.3 or 5.4"
I think the fix is in org.dspace.rest.HandleResource in the following code 
to add context.complete()
after the switch.

if(AuthorizeManager.authorizeActionBoolean(context, dso, 
org.dspace.core.Constants.READ)) {
switch(dso.getType()) {
case Constants.COMMUNITY:
return new Community((org.dspace.content.Community) dso, 
expand, context);
case Constants.COLLECTION:
return new Collection((org.dspace.content.Collection) dso, 
expand, context, null, null);
case Constants.ITEM:
return new Item((org.dspace.content.Item) dso, expand, context);
default:
return new DSpaceObject(dso);
}
} else {


On Tuesday, February 23, 2016 at 11:37:15 PM UTC+2, Faiyaz Ahmed wrote:
>
> I was just about to submit this post and you done it. 
>
> I'm facing same while access via REST API. URL for the rest api is :  
> http://localhost:8080/rest/handle/3015/23
>
> Tomcat Logs : 
>
> 192.168.163.1 - - [24/Feb/2016:00:34:33 +0300] "GET /rest/handle/3015/23 
> HTTP/1.1" 500 -
> 192.168.163.1 - - [24/Feb/2016:00:34:36 +0300] "GET /rest/handle/3015/23 
> HTTP/1.1" 500 -
>
> Dspace 5.4 version logs :
>
>
> 2016-02-24 00:34:33,783 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
> 2016-02-24 00:34:36,643 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
>
>
> Please update if any one have idea on this error.
>
>
>
> On Tuesday, February 23, 2016 at 9:03:39 PM UTC+5, Evgeni Dimitrov wrote:
>>
>> I have used REST API with DSpace 5.2 and Windows. Now I am trying with 
>> DSpace 5.4 and Linux. Doing not the same but very similar thing. Trying to 
>> get a community by handle.
>>
>> I am getting in the DSpace log
>>
>> 2016-02-23 17:24:12,947 INFO  org.dspace.rest.RestIndex @ REST Login 
>> Success for user: @
>> 2016-02-23 17:24:12,973 INFO  org.dspace.rest.HandleResource @ DSO Lookup 
>> by handle: [nls] / [94] got result of: COMMUNITY_17
>> 2016-02-23 17:24:13,091 ERROR org.dspace.rest.Resource @ Something get 
>> wrong. Aborting context in finally statement.
>> 2016-02-23 17:24:13,104 INFO  org.dspace.rest.RestIndex @ REST Logout: 
>> @
>>
>> In the Tomcat log there is more - see bellow.
>>
>> Has anybody any ideas?
>>
>> 
>> 23-Feb-2016 17:24:13.091 SEVERE [http-nio-8080-exec-4] 
>> com.sun.jersey.spi.container.ContainerResponse.logException Mapped 
>> exception to response: 500 (Internal Server Error)
>>  javax.ws.rs.WebApplicationException
>> at org.dspace.rest.Resource.processFinally(Resource.java:169)
>> at org.dspace.rest.HandleResource.getObject(HandleResource.java:74)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at 
>> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>> at 
>> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>> at 
>> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>> at 
>> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>> at 
>> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>> at 
>> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>> at 
>> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>> at 
>> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>> at 
>> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>> at 
>> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat

[dspace-tech] Re: Something wrong with REST API - DSpace 5.4

[Faiyaz Ahmed]

I was just about to submit this post and you done it. 

I'm facing same while access via REST API. URL for the rest api is : 
 http://localhost:8080/rest/handle/3015/23

Tomcat Logs : 

192.168.163.1 - - [24/Feb/2016:00:34:33 +0300] "GET /rest/handle/3015/23 
HTTP/1.1" 500 -
192.168.163.1 - - [24/Feb/2016:00:34:36 +0300] "GET /rest/handle/3015/23 
HTTP/1.1" 500 -

Dspace 5.4 version logs :


2016-02-24 00:34:33,783 ERROR org.dspace.rest.Resource @ Something get 
wrong. Aborting context in finally statement.
2016-02-24 00:34:36,643 ERROR org.dspace.rest.Resource @ Something get 
wrong. Aborting context in finally statement.


Please update if any one have idea on this error.



On Tuesday, February 23, 2016 at 9:03:39 PM UTC+5, Evgeni Dimitrov wrote:
>
> I have used REST API with DSpace 5.2 and Windows. Now I am trying with 
> DSpace 5.4 and Linux. Doing not the same but very similar thing. Trying to 
> get a community by handle.
>
> I am getting in the DSpace log
>
> 2016-02-23 17:24:12,947 INFO  org.dspace.rest.RestIndex @ REST Login 
> Success for user: @
> 2016-02-23 17:24:12,973 INFO  org.dspace.rest.HandleResource @ DSO Lookup 
> by handle: [nls] / [94] got result of: COMMUNITY_17
> 2016-02-23 17:24:13,091 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
> 2016-02-23 17:24:13,104 INFO  org.dspace.rest.RestIndex @ REST Logout: 
> @
>
> In the Tomcat log there is more - see bellow.
>
> Has anybody any ideas?
>
> 
> 23-Feb-2016 17:24:13.091 SEVERE [http-nio-8080-exec-4] 
> com.sun.jersey.spi.container.ContainerResponse.logException Mapped 
> exception to response: 500 (Internal Server Error)
>  javax.ws.rs.WebApplicationException
> at org.dspace.rest.Resource.processFinally(Resource.java:169)
> at org.dspace.rest.HandleResource.getObject(HandleResource.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at 
> org.apache.catalina.valves.A

Re: [dspace-tech] A bug in REST API introduced in 5.3 or 5.4

[Evgeni Dimitrov]

Perhaps the idea was to have context.complete() after normal execution. 
Which is missing.

On Tuesday, February 23, 2016 at 10:29:30 PM UTC+2, Peter Dietz wrote:
>
> Look at Git Blame to find out why things changed:
>
> https://github.com/DSpace/DSpace/blame/dspace-5_x/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java
>
> And that line leads to:
> https://github.com/DSpace/DSpace/pull/1007
>
> So, adding that was intending to prevent stale connections / contexts from 
> being held open for a very long time, and behave like other endpoints. The 
> problem was that you could view /rest/handle, and get data, then change 
> that object, and the next time you view that /rest/handle, the data would 
> not have changed. 
>
> If you have a stack trace, please consider investigating the root of the 
> bug for 5x. In the upcoming DSpace 6x, contexts are completely different 
> with the services refactor, and changes here would have limited utility.
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Tue, Feb 23, 2016 at 3:19 PM, Evgeni Dimitrov  > wrote:
>
>> Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after 
>> the line:
>>
>> return new Community((org.dspace.content.Community) dso, expand, context);
>>
>> some lines are added:
>>
>> } finally{
>> processFinally(context);
>> }
>>
>> Because context is not null and valid, processFinally generates 500 
>> "INTERNAL_SERVER_ERROR"
>>
>> What was the intention for adding "finally" there? What should be the 
>> fix? I can just delete these lines . . .
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@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.

Re: [dspace-tech] Enable Citation at Dspace 5.4

[Faiyaz Ahmed]

Hi Susan,

Thank you so much for this code and working GREAT .. 

You saved my time :)

Regards,
Faiyaz Ahmed

On Wednesday, February 24, 2016 at 1:55:19 AM UTC+5, Susan Borda wrote:
>
> HI-
> Here’s what I added to the item-view.xsl file:
>   
>
>  
>
>  
> 
> 
> 
> 
> xmlui.dri2xhtml.METS-1.0.item-citation
> 
> 
> 
> 
> 
>  test="count(following-sibling::dim:field[@element='identifier' and 
> @qualifier='degreeDiscipline' ]) != 0">
> 
> 
> 
> 
> 
> 
> — 
> Susan Borda
> Digital Technologies Development Librarian
> Montana State University Library
> 406-994-1873
>
>
>
> From: > on behalf of Faiyaz Ahmed 
> >
> Date: Tuesday, February 23, 2016 at 12:02 PM
> To: DSpace Technical Support >
> Subject: [dspace-tech] Enable Citation at Dspace 5.4
>
> Hello All, 
>
> Does any one have idea that how I can enable "CITATION" after description 
> as in this link : https://openknowledge.worldbank.org/handle/10986/23746
>
> Regards,
> Faiyaz Ahmed
>
> -- 
> 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...@googlegroups.com .
> To post to this group, send email to dspac...@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.

Re: [dspace-tech] Enable Citation at Dspace 5.4

[Borda, Susan]

HI-
Here's what I added to the item-view.xsl file:
  

   



 




xmlui.dri2xhtml.METS-1.0.item-citation












-
Susan Borda
Digital Technologies Development Librarian
Montana State University Library
406-994-1873



From: mailto:dspace-tech@googlegroups.com>> on 
behalf of Faiyaz Ahmed 
mailto:faiyazahmed...@gmail.com>>
Date: Tuesday, February 23, 2016 at 12:02 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] Enable Citation at Dspace 5.4

Hello All,

Does any one have idea that how I can enable "CITATION" after description as in 
this link : https://openknowledge.worldbank.org/handle/10986/23746

Regards,
Faiyaz Ahmed

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

Re: [dspace-tech] A bug in REST API introduced in 5.3 or 5.4

[Evgeni Dimitrov]

I am not getting this. Now processFinally is called always - after 
exception and after normal execution - and it always generates 500 
"INTERNAL_SERVER_ERROR".
It is true that in addition it aborts the context, but . . .

On Tuesday, February 23, 2016 at 10:29:30 PM UTC+2, Peter Dietz wrote:
>
> Look at Git Blame to find out why things changed:
>
> https://github.com/DSpace/DSpace/blame/dspace-5_x/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java
>
> And that line leads to:
> https://github.com/DSpace/DSpace/pull/1007
>
> So, adding that was intending to prevent stale connections / contexts from 
> being held open for a very long time, and behave like other endpoints. The 
> problem was that you could view /rest/handle, and get data, then change 
> that object, and the next time you view that /rest/handle, the data would 
> not have changed. 
>
> If you have a stack trace, please consider investigating the root of the 
> bug for 5x. In the upcoming DSpace 6x, contexts are completely different 
> with the services refactor, and changes here would have limited utility.
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Tue, Feb 23, 2016 at 3:19 PM, Evgeni Dimitrov  > wrote:
>
>> Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after 
>> the line:
>>
>> return new Community((org.dspace.content.Community) dso, expand, context);
>>
>> some lines are added:
>>
>> } finally{
>> processFinally(context);
>> }
>>
>> Because context is not null and valid, processFinally generates 500 
>> "INTERNAL_SERVER_ERROR"
>>
>> What was the intention for adding "finally" there? What should be the 
>> fix? I can just delete these lines . . .
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@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.

Re: [dspace-tech] A bug in REST API introduced in 5.3 or 5.4

[Peter Dietz]

Look at Git Blame to find out why things changed:
https://github.com/DSpace/DSpace/blame/dspace-5_x/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java

And that line leads to:
https://github.com/DSpace/DSpace/pull/1007

So, adding that was intending to prevent stale connections / contexts from
being held open for a very long time, and behave like other endpoints. The
problem was that you could view /rest/handle, and get data, then change
that object, and the next time you view that /rest/handle, the data would
not have changed.

If you have a stack trace, please consider investigating the root of the
bug for 5x. In the upcoming DSpace 6x, contexts are completely different
with the services refactor, and changes here would have limited utility.



Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Tue, Feb 23, 2016 at 3:19 PM, Evgeni Dimitrov 
wrote:

> Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after
> the line:
>
> return new Community((org.dspace.content.Community) dso, expand, context);
>
> some lines are added:
>
> } finally{
> processFinally(context);
> }
>
> Because context is not null and valid, processFinally generates 500
> "INTERNAL_SERVER_ERROR"
>
> What was the intention for adding "finally" there? What should be the fix?
> I can just delete these lines . . .
>
> --
> 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] A bug in REST API introduced in 5.3 or 5.4

[Evgeni Dimitrov]

Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after
the line:

return new Community((org.dspace.content.Community) dso, expand, context);

some lines are added:

} finally{
processFinally(context);
}

Because context is not null and valid, processFinally generates 500
"INTERNAL_SERVER_ERROR"

What was the intention for adding "finally" there? What should be the fix?
I can just delete these lines . . .

-- 
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] Enable Citation at Dspace 5.4

[Faiyaz Ahmed]

Hello All,

Does any one have idea that how I can enable "CITATION" after description 
as in this link : https://openknowledge.worldbank.org/handle/10986/23746

Regards,
Faiyaz Ahmed

-- 
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] Indexing Solr index-lucene-init -- Error table view does not exists

[Faiyaz Ahmed]

Thanks Helix for reply ...

I updated my answer below after your questions..

If you make a search query from the /discovery URL, do you see results?

*Can you please let me know how to do that ...*

If you click on any Browse index (by author, by title, by issue date),
do you see any items?

*I can see author name but no data I can see ...*

Which URL did you use for search?

*I clicked on advance search and it is showing data : *

To debug the problem with an item page not showing any content, watch
the log file:
tail -f [dspace]/log/dspace.log.2016-xx-xx
and then load any item page. Do you see any message added to the log?

Only info logs printed :
*2016-02-23 21:28:35,714 INFO  org.dspace.usage.LoggerUsageEventListener @
anonymous:session_id=:ip_addr=192.168.163.1:view_item:handle=123456789/117*


Regards,



Faiyaz Ahmed

On Tue, Feb 23, 2016 at 10:49 PM, helix84  wrote:

> The "bi_1", "bi_2" etc tables missing are meant to be used with legacy
> DB-based browse. They don't exist because DSpace 5 doesn't create them
> anymore.
>
> > 2016-02-22 21:01:28,816 INFO  org.dspace.search.DSIndexer @ Writing
> Community: 123456789/99 to Index
>
> From these log lines, I see that index-init (Lucene-based search)
> completed successfully. The question is whether you changed your
> configuration to use the legacy Lucene search and DB-based browse or
> you did no changes and are using the Discovery (Solr) based
> search&browse.
>
> If you click on any Browse index (by author, by title, by issue date),
> do you see any items?
> Which URL did you use for search?
>
> If you make a search query from the /discovery URL, do you see results?
>
> To debug the problem with an item page not showing any content, watch
> the log file:
> tail -f [dspace]/log/dspace.log.2016-xx-xx
>
> and then load any item page. Do you see any message added to the log?
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>

-- 
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] Indexing Solr index-lucene-init -- Error table view does not exists

[helix84]

The "bi_1", "bi_2" etc tables missing are meant to be used with legacy
DB-based browse. They don't exist because DSpace 5 doesn't create them
anymore.

> 2016-02-22 21:01:28,816 INFO  org.dspace.search.DSIndexer @ Writing 
> Community: 123456789/99 to Index

>From these log lines, I see that index-init (Lucene-based search)
completed successfully. The question is whether you changed your
configuration to use the legacy Lucene search and DB-based browse or
you did no changes and are using the Discovery (Solr) based
search&browse.

If you click on any Browse index (by author, by title, by issue date),
do you see any items?
Which URL did you use for search?

If you make a search query from the /discovery URL, do you see results?

To debug the problem with an item page not showing any content, watch
the log file:
tail -f [dspace]/log/dspace.log.2016-xx-xx

and then load any item page. Do you see any message added to the log?


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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] Indexing Solr index-lucene-init -- Error table view does not exists

[Faiyaz Ahmed]

Thanks Tim for Reply.. However, I have done the same but the data is not
showing, however at advance search it is showing but when I click on view
item then only blank page appears.

Regards,
Faiyaz Ahmed

Faiyaz Ahmed

On Tue, Feb 23, 2016 at 1:19 AM, Tim Donohue  wrote:

> Hello Faiyaz,
>
> Just a quick note. If you are trying to reindex DSpace in *Solr*, then you
> are running the wrong command.
>
> Assuming you mean to be using Discovery / Solr:
> https://wiki.duraspace.org/display/DSDOC5x/Discovery
>
> Then the correct reindex command is:
> [dspace]/bin/dspace index-discovery -b
>
> The old "index-lucene-init" command is ONLY used if you are using the
> legacy, deprecated Lucene Search & DBMS Browse systems. If you are not
> using those systems (which it sounds like you are not), then the command
> will likely throw errors.
>
> - Tim
>
>
> On 2/22/2016 12:04 PM, Faiyaz Ahmed wrote:
>
> Dear All,
>
> I have installed the Dspace 5.4 and put too much data but
>
> When I run below command, I'm getting follow error:
>
> Command:
> /usr/local/dspace/bin/dspace index-lucene-init
>
> Error:
>
> 2016-02-22 21:01:21,159 INFO  org.dspace.core.ConfigurationManager @
> Loading from classloader: file:/usr/local/dspace/config/dspace.cfg
> 2016-02-22 21:01:21,173 INFO  org.dspace.core.ConfigurationManager @ Using
> dspace provided log configuration (log.init.config)
> 2016-02-22 21:01:21,173 INFO  org.dspace.core.ConfigurationManager @
> Loading: /usr/local/dspace/config/log4j.properties
> 2016-02-22 21:01:25,199 INFO  org.dspace.storage.rdbms.DatabaseManager @
> DBMS is 'Oracle'
> 2016-02-22 21:01:25,200 INFO  org.dspace.storage.rdbms.DatabaseManager @
> DBMS driver version is 'Oracle Database 11g Express Edition Release
> 11.2.0.2.0 - 64bit Production'
> 2016-02-22 21:01:25,243 INFO  org.dspace.storage.rdbms.DatabaseUtils @
> Loading Flyway DB migrations from: filesystem:/usr/local/dspace/etc/oracle,
> classpath:org.dspace.storage.rdbms.sqlmigration.oracle,
> classpath:org.dspace.storage.rdbms.migration
> 2016-02-22 21:01:25,329 INFO
>  org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database:
> jdbc:oracle:thin:@//libdb:1521/xe (Oracle 11.2)
> 2016-02-22 21:01:25,414 INFO  org.dspace.storage.rdbms.DatabaseUtils @
> DSpace database schema is up to date
> 2016-02-22 21:01:25,434 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL query exec Error -
> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
>
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)
> at
> oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:886)
> at
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1175)
> at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1296)
>
> Does any one have idea which table or view is missing?
>
> Regards,
> Faiyaz Ahmed
>
> --
> 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 a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/yhmMsFJ-KhU/unsubscribe.
> To unsubscribe from this group and all its topics, 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] Bug in Dspace 5.4

[Faiyaz Ahmed]

Dear All,

Following case has been produced. 

1 - Login at demo site URL and go to 
: http://demo.dspace.org/xmlui/admin/epeople
2 - Change the language from the top drop down any, then URL changed to 
: http://demo.dspace.org/xmlui/admin/epeople/main?locale-attribute=de
3 - However, if you 
put http://demo.dspace.org/xmlui/admin/epeople?locale-attribute=de ... it 
will work.

The same is happening at Registration form.

Does any one have quick fix for this please.

Regards,
Faiyaz Ahmed

-- 
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] Something wrong with REST API - DSpace 5.4

[Evgeni Dimitrov]

I have used REST API with DSpace 5.2 and Windows. Now I am trying with
DSpace 5.4 and Linux. Doing not the same but very similar thing. Trying to
get a community by handle.

I am getting in the DSpace log

2016-02-23 17:24:12,947 INFO  org.dspace.rest.RestIndex @ REST Login
Success for user: @
2016-02-23 17:24:12,973 INFO  org.dspace.rest.HandleResource @ DSO Lookup
by handle: [nls] / [94] got result of: COMMUNITY_17
2016-02-23 17:24:13,091 ERROR org.dspace.rest.Resource @ Something get
wrong. Aborting context in finally statement.
2016-02-23 17:24:13,104 INFO  org.dspace.rest.RestIndex @ REST Logout:
@

In the Tomcat log there is more - see bellow.

Has anybody any ideas?


23-Feb-2016 17:24:13.091 SEVERE [http-nio-8080-exec-4]
com.sun.jersey.spi.container.ContainerResponse.logException Mapped
exception to response: 500 (Internal Server Error)
 javax.ws.rs.WebApplicationException
at org.dspace.rest.Resource.processFinally(Resource.java:169)
at org.dspace.rest.HandleResource.getObject(HandleResource.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:521)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1096)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:674)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1500)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1456)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

-- 
You received this message because 

[dspace-tech] Multi language field's OAI xml

[SamuelOPH]

Currently DSpace returns (through OAI) multi language fields as multiple
fields with the same tag

Practical example; I have an article with two descriptions, one in english
and one in portuguese.
When I get this article's xml through OAI, i get the descriptions in the
following format:

...
 Here be description
 Here be portuguese description
...

I believe this is problematic because it makes very difficult to detect the
language of the field and harvest both (for example, VuFind only gets the
first description. see [1]).

Also, please correct me if i'm wrong, but is a fault in DSpace on complying
with Dublin Core guidelines, see Recommendation 9:
*Where the language of the value is indicated, it should be encoded using
the 'xml:lang' attribute.*From
http://dublincore.org/documents/dc-xml-guidelines/.

I know that, by default, it's not obligatory to have a language field, but
shouldn't be the case when you have fields with more than one language?

Can somebody confirm that? I was afraid that the problem was on VuFind
side, i was looking at the article's xml returned from OAI stored in VuFind
folders, but i believe thesse XMLs are exact ones returned by DSpace, and
directly searching through DSpace OAI interface (dspacedomain/oai/request)
gave me conffidence that its DSpace whos returning these XMLs.

[1]https://sourceforge.net/p/vufind/mailman/message/34785485/

Samuel Henrique O. P. [samueloph]
Técnico em Informática - UTFPR [2012].
Estudante de Engenharia de Computação - UTFPR.

-- 
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] Multi language field's OAI XML

[Samuel Henrique]

Currently DSpace returns (through OAI) multi language fields as multiple 
fields with the same tag 

Practical example; I have an article with two descriptions, one in english 
and one in portuguese.
When I get this article's xml through OAI, i get the descriptions in the 
following format:

...
 Here be description
 Here be portuguese description
...

I believe this is problematic because it makes very difficult to detect the 
language of the field and harvest both (for example, VuFind only gets the 
first description. see [1]).

Also, please correct me if i'm wrong, but is a fault in DSpace on complying 
with Dublin Core guidelines, see Recommendation 9: 
*Where the language of the value is indicated, it should be encoded using 
the 'xml:lang' attribute.*From 
http://dublincore.org/documents/dc-xml-guidelines/.

I know that, by default, it's not obligatory to have a language field, but 
shouldn't be the case when you have fields with more than one language?

Can somebody confirm that? I was afraid that the problem was on VuFind 
side, i was looking at the article's xml returned from OAI stored in VuFind 
folders, but i believe thesse XMLs are exact ones returned by DSpace, and 
directly searching through DSpace OAI interface (dspacedomain/oai/request) 
gave me conffidence that its DSpace whos returning these XMLs.

[1]https://sourceforge.net/p/vufind/mailman/message/34785485/

-- 
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: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload

[Ilja Sidoroff]

I changed dspace.cfg not to require uploads

webui.submit.upload.required = false

And I didn't get stuck on the "Upload" page anymore. However, Sherpa/Romeo 
information still gets printed in the wrong page. Also, upload page doesn't 
display any possibilities to actually upload any files, so it still seems 
to be broken.


-- 
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] Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload

[Ilja Sidoroff]

Hello, 

I have encountered a possible bug in DSpace in workflow's edit metadata 
phase, where editing metadata gets stuck in "upload" phase. Here's how I 
get the error:

1) I have created a collection, and assigned groups to Administrators, 
Submitters and Accept/Reject/Edit metadata step.

2) I upload new metadata from csv file, with --workflow -option and 
Submissions pool shows the imported items correctly

3) When I take an item from the pool and select "Edit metadata", first two 
"Describe" pages work as intended, but "Access Settings" page does not show 
Sherpa/Romeo information -
I have configured embargo and Sherpa/Romeo integration, but haven't 
otherwise modified the submission process.

4) When proceeding to the "Upload" page, I get the Sherpa/Romeo information 
and list of Files Uploaded, which is empty. Now Previous/Save&Exit/Next 
buttons, nor the Item submission page buttons don't work anymore. When 
clicking them I get back to the "Upload" page, but the browser URL changes, 
for example:

http:
//localhost:8080/handle/123456789/2/submit/7c6e545d25467463746a2e197e0d073357374e8c.continue
http:
//localhost:8080/handle/123456789/2/submit/1f243c8b11525c2e11387d6e280e1d737a5e0d55.continue

I.e. some sort of cookie stored in the URL changes.

dspace.cfg option for file upload is the default, I'll try with false here 
soon, but it seems that there might be also some other problems, at least 
the Sherpa/Romeo information showing up in the wrong place might suggest so.

webui.submit.upload.required = true

Does anyone have similar experiences? Should I file a bug report or might 
this be some misconfiguration related to BTE import, 
Sherpa/Romeo-integration or something else?

br,

Ilja Sidoroff
Information Specialist
University of Eastern Finland, Library

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