Re: [dspace-tech] general_jspui_error

[Freddy Guerrero]

Hi Tim

It happens that a collection was not opened, reviewing the items I found 
that I had a file on that item that was corrupt, delete the file and the 
collection was already displayed. Then I have two questions:

1.- How can I detect corrupt files in other items?
2.- I have configured in my local.cfg file like this:
assetstore.dir = ${dspace.dir}/assetstore
assetstore.dir.1 = ${dspace.dir}/assetstore2

What change should I make in the file:

 DSPACE/config/spring/api/bitstore.xml 





Please help

Freddy




El lunes, 24 de septiembre de 2018, 10:52:17 (UTC-5), Tim Donohue escribió:
>
> Hi Freddy,
>
> According to the line numbers in that error message, DSpace cannot seem to 
> find your "collection-home.jsp".  Here's the line where the error seems to 
> be occurring:
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-jspui/src/main/java/org/dspace/app/webui/servlet/HandleServlet.java#L773
>
> If you have renamed or moved this JSP, that could be the cause.  
> Otherwise, you might want to look at whether there's something else you may 
> have changed in DSpace that could be causing this error to occur.
>
> I'm not entirely sure why this error would be happening, as that JSP is 
> provided by DSpace (and is required).  Unfortunately, I'm not as well 
> versed in the JSPUI these days (as I know the XMLUI a bit better).  But, 
> I'm hoping maybe this will give you a clue as to what the cause could be -- 
> or maybe someone else on this list will have seen this problem before.
>
> Another thing you might want to look around for is any other errors that 
> appear in the logs (if any).  It's possible something else in your JSPUI is 
> not working properly and it ends up causing this odd error.
>
> - Tim
>
> On Mon, Sep 24, 2018 at 10:33 AM Freddy Guerrero  > wrote:
>
>> Thanks Tim for answering my email, copy the lines of my LOG file this is 
>> what I get:
>>
>> 2018-09-24 10:24:04,287 WARN  org.dspace.app.webui.servlet.DSpaceServlet 
>> @ 
>> anonymous:session_id=53741F36891CF45C93CC7CCB64877589:ip_addr=54.38.255.116:general_jspui_error:javax.servlet.ServletException\colon;
>>  
>> org.apache.jasper.JasperException\colon; java.lang.NullPointerException
>> javax.servlet.ServletException: org.apache.jasper.JasperException: 
>> java.lang.NullPointerException
>> at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:71)
>> at 
>> org.dspace.app.webui.servlet.HandleServlet.collectionHome(HandleServlet.java:773)
>> at 
>> org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:305)
>> at 
>> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126)
>> at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at 
>> org.dspace.rdf.negotiation.NegotiationFilter.doFilter(NegotiationFilter.java:52)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at 
>> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at 
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
>> at 
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
>> at 
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
>> at 
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
>> at 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>> at 
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:1025)
>> at 
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at 
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445)
>> at 
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1136)
>> at 
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
>> at 
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

[dspace-tech] EPrint to DSpace Migration

[Bhala]

Hi All,

Greeting of the day,

We are planing to migrate EPrint to DSpace, from my side,I tried 
combinations of work to migrate metadata from Eprint to Dsapce, but till 
couldn't  succeed. (we have around 1000 records Dspace installed in  
windows)

kindly request your help in these regard.

Regards
Bhala

-- 
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 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: Problems with Orcid in dspace 6.3

[mmorris]

Hi,

The fix in DS-3999  worked for 
me when using the Author field (dc.contrinbutor.author) but when using the 
editor field (dc.contributor.editor) a new id is generated, am i missing 
something?

Thanks,
Mike

On Sunday, September 16, 2018 at 5:37:20 AM UTC-4, Stefanie Behnke wrote:
>
> Dear all,
>
> we use Dspace 6.3, XMLUI Interface and ORCID enabled.
>
> Submitting a new item with 2 authors works. The result in the authority 
> shows: (example for one author)
>
>   {
>
> "id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf",
>
> "field": "dc_contributor_author",
>
> "value": "Behnke, Stefanie",
>
> "deleted": false,
>
> "creation_date": "2018-09-16T09:01:40.474Z",
>
> "last_modified_date": "2018-09-16T09:01:40.474Z",
>
> "authority_type": "orcid",
>
> "first_name": "Stefanie",
>
> "last_name": "Behnke",
>
> "orcid_id": "-0001-5923-423X"
>
>   },
>
>  
>
> Trying to add a third author with ORCID to this item make the “orcid_id” 
> for the existing authors vanish from the authority:
>
>   {
>
> "id": "75e2dd03-7cdf-4e21-9b1d-293f02d3c0cf",
>
> "field": "dc_contributor_author",
>
> "value": "Behnke, Stefanie",
>
> "deleted": false,
>
> "creation_date": "2018-09-16T09:01:40.474Z",
>
> "last_modified_date": "2018-09-16T09:01:40.474Z",
>
> "authority_type": "orcid",
>
> "first_name": "Stefanie",
>
> "last_name": "Behnke"
>
>   },
>
>  
>
> I cannot imagine that this should be the intended behaviour, so I think 
> this is a bug.
>
> Any help is much appreciated.
>
> Best regards
>
> Stefanie
>

-- 
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 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] Request Document Copy Large Files – DSpace 6 XMLUI

[eneshukic via DSpace Technical Support]

Hi Tim and Adan,

Thanks for your input.  We have considered using an Embargo, but it would 
not meet our requirements.

We would probably need to handle the mail server error message  and add 
another button that will notify the requester that the file is too large to 
be sent by mail (and offer them other methods to get the document).

We would probably need to implement something similar to Adan.

Regards,
Enes

On Monday, September 24, 2018 at 5:21:54 PM UTC+2, Adan Roman Ruiz wrote:
>
> We solved using other method. Although it needs changes in the source 
> code. 
> First we alter the request-copy to send links with a generated 
> token  (very long), instead of the file. We store into the database the 
> token, related file, date and uses.
> Then we added a point of access to dspace similar to /bitstream called 
> /itemRequestFileDownload. This access point checks that the token exists, 
> and returns the related file ignoring permissions.
> In addition you can record the number of uses, or use the time passed from 
> its generated, to make expire the link.
>
> Best luck
> Adán Roman
>
> El lun., 24 sept. 2018 a las 16:35, Tim Donohue ( >) escribió:
>
>> Hi Enes,
>>
>> If you are willing to create a DSpace *group* to provide access to the 
>> document, then you could manage this access similar to a DSpace Embargo:
>>
>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality
>>
>> In DSpace, an Embargo is simply provides temporary access and/or 
>> restrictions on an entire Item or a specific file (Bitstream).  However, 
>> those temporary access rights are only available to be set at the Group 
>> level (not at an individual EPerson).  But, if you are willing to create a 
>> Group for this scenario, then you could Edit the Item, and add a new 
>> "authorization policy (also known as a "Resource Policy") (on either the 
>> entire Item, or a single Bitstream). You'd want to define a new policy that 
>> provides READ access to a specific Group, and add an "End Date" of one 
>> day/week/month from now.  Once the "End Date" passes, the policy will 
>> expire, and the access rights provided by the policy will no longer be 
>> valid.
>>
>> I hope that gives you an idea of another way to provide temporary access 
>> rights.  Let us know on this list if you have other questions.
>>
>> Tim
>>
>>
>>
>> On Mon, Sep 24, 2018 at 6:17 AM eneshukic via DSpace Technical Support <
>> dspac...@googlegroups.com > wrote:
>>
>>> If a registered user is requesting a copy of large bitstream document, 
>>> mail server will return an error message.
>>>
>>>
>>> What are the other way of distributing large documents? We can export 
>>> the item (zip file) and place it into shared folder, but that is not the 
>>> most efficient and secure way to do it. Can we grant a temporary user 
>>> access to the bitstream?
>>>
>>>
>>> Regards,
>>>
>>> Enes 
>>>
>>> -- 
>>> 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 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.
>>>
>> -- 
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
>> -- 
>> 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 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.
>>
>
>
> -- 
> Adán Román Ruiz
> adan@gmail.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 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] Help Handle Server

[Leidy Madroñero]

good morning

I am configuring the handle server in dspace 6.

The server was validated by the CNRI. The problem arises when I try to test 
the prefix changes assigned to me in my repository by creating a new item, 
which continues to appear with the prefix that comes by default in the 
installation.

I have modified the following line in the local.cfg file because of the 
prefix assigned to me:

handle.prefix = 123456789

In addition to the previous one, there are other additional lines that I am 
not sure of changing, for example:

By default it appears:
handle.canonical.prefix = $ {dspace.url} / handle /

Is it correct to change it in this way?

handle.canonical.prefix = $ {dspace.url} /http://hdl.handle.net/

After this, it is necessary to rebuild dspace or restart the server to 
visualize the changes of the prefix in the repository ?.

I appreciate your collaboration.

Greetings, lady.

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