[dspace-tech] DSpace-CRIS 5.10 Update JQuery

2020-08-26 Thread Sean Carte 
What would be involved in updating jquery on DSpace-CRIS 5.10 to something
more recent?

I ask because our network security has identified vulnerabilities in
jquery-1.11 currently in use in DSpace-CRIS 5.10.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhMM%2BjzDuHQzwcHkOGsbnrz7tgFJUx8_qM4am4mY811B2A%40mail.gmail.com.

Re: [dspace-tech] Thumbnails error

2020-08-26 Thread stefanabr...@gmail.com 
Thanks to you both for your help!

On Friday, August 7, 2020 at 7:16:11 AM UTC-4 alan...@gmail.com wrote:

> Original poster is using Windows. Recursively change the permissions of 
> the assetstore to your Windows user and try filter-media again.
>
> Regards,
>
> On Fri, Jul 31, 2020, 17:25 Mark H. Wood  wrote:
>
>> On Tue, Jul 28, 2020 at 01:57:39PM -0700, stefanabr...@gmail.com wrote:
>> > Thanks for your response, Mark. Do you know if how to check/update 
>> > assetstore permissions is documented anywhere?
>>
>> I can't think of any place where this is documented, but it's really
>> simple:  everything in and below [dspace]/assetstore (and any
>> additional assetstores that you may have) should be owned by the user
>> that runs Tomcat and should grant read/write permission to that user.
>>
>> I ran a quick experiment on a test instance of DSpace.  On this system
>> Tomcat is run by the user 'tomcat'.  I am using GNU 'find'.  This
>> command should list all files in 'assetstore' NOT owned by the user
>> 'tomcat', *provided* that your current directory is the [dspace]
>> directory and the assetstore is a subdirectory named "assetstore":
>>
>>   find assetstore -not -user tomcat
>>
>> This command should list all files under 'assetstore' that are not
>> read/write for the owner, regardless of other permissions:
>>
>>   find assetstore -not -perm -600
>>
>> -- 
>> Mark H. Wood
>> Lead Technology Analyst
>>
>> University Library
>> Indiana University - Purdue University Indianapolis
>> 755 W. Michigan Street
>> Indianapolis, IN 46202
>> 317-274-0749 <(317)%20274-0749>
>> www.ulib.iupui.edu
>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/20200731142551.GC3259%40IUPUI.Edu
>> .
>>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c4b2896b-b343-4e4a-b82a-f30167a6377an%40googlegroups.com.

Re: [dspace-tech] Additional workflow before submission?

2020-08-26 Thread schul...@effective-webwork.de 
Hi Tim,

thanks a lot for your detailed answer! We are currently trying if that idea 
will work for us, and I will get back to you with our results shortly.

Johannes

Tim Donohue schrieb am Dienstag, 25. August 2020 um 17:20:56 UTC+2:

> Hi Johannes,
>
> This is not supported in DSpace out-of-the-box and may be complex to 
> implement.  In DSpace terminology, deposit *always* begins with a 
> "WorkspaceItem" object (which is an active submission). That object by 
> default sits in a single user's "workspace" until submitted...at which 
> point it becomes a "WorkflowItem".  That is where the approval process is 
> triggered...and once approved, it becomes an (archived) "Item".
>
> So, the flow is generally:
>
> WorkspaceItem <-> WorkflowItem -> (Archived) Item
>
> As implied by the double arrows between WorkspaceItem and WorkflowItem, a 
> submission may move *between* those states one or more times prior to 
> becoming "accepted" and archived.
>
> Because of this nature, you may want to consider whether small tweaks to 
> your internal process could allow you to use DSpace mostly "as-is".  One 
> (perhaps simplified) idea might be:
>
>1. Author creates a publication idea as a (partially filled out) 
>Submission (i.e. a new WorkspaceItem).  They submit this new idea (making 
>it a WorkflowItem), perhaps even to a "Submission Ideas" Collection 
>tailored for this initial approval.
>2. Superior reviews the idea (now a WorkflowItem), and provide 
>feedback by "rejecting" the submission (you could rename the reject button 
>as needed to "provide feedback").  (This turns the WorkflowItem back into 
> a 
>WorkspaceItem & sends it back to the Author for changes or enhancements, 
>along with the superior's feedback.)
>3. Author then looks at feedback and either cancels/deletes the 
>Submission (if not a good idea) or enhances it (if it was approved).  They 
>potentially resubmit for full approval (either to the same Collection, or 
>maybe different one, depending on needs)
>
> I realize that flow is slightly odd, but it'd allow you to do a 
> WorkspaceItem (draft idea) -> WorkflowItem (initial approval) -> 
> WorkspaceItem (enhanced) -> WorkflowItem (final approval).   It may also be 
> easier to customize the DSpace UI to support this flow of data, as it's a 
> more "natural" flow for the DSpace object model & submission/workflow 
> process. You also can customize submission flows per Collection, so you 
> could have one flow for the "draft idea" (in a private, draft Collection, 
> perhaps with limited metadata fields required and an uploaded file 
> optional) and another for the "final idea/paper" (in a public/private final 
> Collection, perhaps with more metadata fields required & an uploaded file 
> required).
>
> Just something to consider here.  You also could do a heavier 
> customization here to try to add Workflow Approval *first*. But, it seems 
> (to me) like there will need to be something to approve (which implies to 
> me that you may need a WorkspaceItem first anyhow, even if it's just a 
> partially filled out one).
>
> Tim 
>
> *--*
>
> *Tim Donohue*
>
> Technical Lead, DSpace
>
> tim.d...@lyrasis.org
>
> Lyrasis.org  | DSpace.org 
>
>
>
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of J 
> *Sent:* Thursday, August 20, 2020 3:38 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Additional workflow before submission? 
>  
> Hi all,
>
> we need an additional workflow in which authors can present a publication 
> idea to their superiors and get it approved. This additional workflow 
> should happen before the submission process, so instead of [Submission -> 
> Workflow] we need [Additional Workflow -> Submission -> Workflow].
>
> At first glance we would try to implement this functionality as a custom 
> submission step, but are unsure if the assignment of others users during 
> the submission process would work. Or is there an extension available that 
> already would support our use case?
>
> Regards
> Johannes
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> --- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/6f301637-f584-4c19-967b-dc8a186d6d50n%40googlegroups.com
>  
> 
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this m

[dspace-tech] dspace oai listsets returns error java.lang.IllegalArgumentException: No such column 'name'

2020-08-26 Thread Konstantinos Koumoutsos 

Hello Team.

I come across the following error when i request dspace oai listsets 
https://nemertes.library.upatras.gr/oai/request?verb=ListSets 

*description* *The server encountered an internal error () that prevented 
it from fulfilling this request.*

*exception* 
org.springframework.web.util.NestedServletException: Request processing 
failed; nested exception is java.lang.IllegalArgumentException: No such 
column 'name' 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:894)
 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
 
javax.servlet.http.HttpServlet.service(HttpServlet.java:617) 
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 

*root cause* 
java.lang.IllegalArgumentException: No such column 'name' 
org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:585) 
org.dspace.storage.rdbms.TableRow.getStringColumn(TableRow.java:249) 
org.dspace.content.Community.getMetadata(Community.java:395) 
org.dspace.content.Community.getName(Community.java:446) 
org.dspace.xoai.services.impl.xoai.DSpaceSetRepository.community(DSpaceSetRepository.java:103)
 
org.dspace.xoai.services.impl.xoai.DSpaceSetRepository.retrieveSets(DSpaceSetRepository.java:170)
 
com.lyncode.xoai.dataprovider.data.internal.SetRepositoryHelper.getSets(SetRepositoryHelper.java:48)
 
com.lyncode.xoai.dataprovider.handlers.ListSetsHandler.handle(ListSetsHandler.java:48)
 
com.lyncode.xoai.dataprovider.OAIDataProvider.handle(OAIDataProvider.java:201) 
com.lyncode.xoai.dataprovider.OAIDataProvider.handle(OAIDataProvider.java:229) 
org.dspace.xoai.controller.DSpaceOAIDataProvider.contextAction(DSpaceOAIDataProvider.java:107)
 
sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
java.lang.reflect.Method.invoke(Method.java:606) 
org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:213)
 
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:126)
 
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96)
 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:617)
 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:578)
 
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)
 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
 
javax.servlet.http.HttpServlet.service(HttpServlet.java:617) 
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 

whereas ListMetadataFormats is working OK as per the following link.
https://nemertes.library.upatras.gr/oai/driver?verb=ListMetadataFormats

Any help is much appreciated.

I tried to import oai but also i am getting the following error

[/bin/dspace oai import -c
OAI 2.0 manager action started
Clearing index
Index cleared
Using full import.
Full import
100 items imported so far...
200 items imported so far...
300 items imported so far...
400 items imported so far...
500 items imported so far...
600 items imported so far...
700 items imported so far...
800 items imported so far...
900 items imported so far...
1000 items imported so far...
1100 items imported so far...
1200 items imported so far...
1300 items imported so far...
1400 items imported so far...
1500 items imported so far...
1600 items imported so far...
1700 items imported so far...
1800 items imported so far...
1900 items imported so far...
2000 items imported so far...
2100 items imported so far...
2200 items imported so far...
2300 items imported so far...
2400 items imported so far...
2500 items imported so far...
2600 items imported so far...
2700 items imported so far...
2800 items imported so far...
2900 items imported so far...
3000 items imported so far...
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: 
Unexpected end of stream while reading trailer headers for chunked request
at 
org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
at 
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
at 
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
at 
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:124)
at org.apache.solr.client.solrj.Solr