[dspace-tech] xmlui issue: port 80 is working but port 6060 not working

[Sneha]

On Wednesday, August 22, 2018 at 7:33:49 PM UTC+5:30, Sneha wrote:
>
> Hi,
>
> My dspace service was working perfectly.  However, some issues with my IBM 
> server occurred which was resolved.  Now all my services are working 
> perfectly except xmlui interface (503 Service Unavailable).  Other services 
> configured on my localhost work perfectly.  However, the xmlui interface 
> which runs on port 6060 is not responding and is giving following error: 
>
> Service Unavailable
>
> The server is temporarily unable to service your request due to 
> maintenance downtime or capacity problems. Please try again later.
> --
> Apache/2.4.18 (Ubuntu) Server at dl.bhu.ac.in Port 80
>
> Also, the cocoon file has no log report since the day server error 
> occurred.
>
> Version: DSpace 6.0
> xmlui interface uri: localhost:6060/xmlui
>
> Please help as my service was running a live repository of my institution.
>
> Thanks.
>
>
>
>
>
>

-- 
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] Re: Notification "DSpace: Submission Approved and Archived" on email

[repozitorybntu]

Hello.
Thank you for the answer! I hope one day we can configure all of email 
notifications.

среда, 22 августа 2018 г., 17:45:51 UTC+3 пользователь Tim Donohue написал:
>
> Hello,
>
> Unfortunately, at this time, you can only turn off the entire mail server, 
> and not individual notifications.
>
> If you want DSpace to no longer send any emails, you can uncomment this 
> configuration (in dspace.cfg or local.cfg) and set it to "true"
>
> mail.server.disabled = false 
>
> Here's where it exists in the dspace.cfg file:
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L163
>
> Disabling an individual notification like that "Submission Approved and 
> Archived" email would require changing the Java code in DSpace.
>
> Here's the DSpace 6.x Java class where that specific email is sent:  
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/workflowbasic/BasicWorkflowServiceImpl.java#L802
>
> - Tim
>
> On Mon, Aug 20, 2018 at 2:12 AM > 
> wrote:
>
>> So? No one knows how to turn off this function?
>>
>> среда, 8 августа 2018 г., 17:03:29 UTC+3 пользователь 
>> repozit...@gmail.com написал:
>>
>>> Hello. Can you help us please to understand how to turn off email 
>>> message notifications like "DSpace: Submission Approved and Archived" in 
>>> DSpace configuration? 
>>> Thanks alot.
>>>
>> -- 
>> 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+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] handles, isreplacedby, and withdrawn items

[Fitchett, Deborah]

Hi all,

I finally got around to trying this out on our dev server: updated the “handle” 
table to point two different handles to the one resource_id (and none to the 
withdrawn resource_id). It seemed in the first instance to work – following the 
links did what I expected.

Then I tried running the index-discovery -b job. That kept stopping 
mysteriously in the middle of it – no obvious errors in the solr or dspace 
logs, just stopped. (I don’t know, maybe our dev server’s just slow and ran out 
of memory or got distracted or something.) But running index-discovery with no 
options picked up where it left off, and after a couple of repetitions of this 
it finally indexed the item in question and all my search/browse tests worked 
as expected too.

So I was on the verge of declaring victory – and then I ran an oai import -c -v 
job. To my tremendous disappointment that failed partway through with:

Item with handle null indexed
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Document 
is missing mandatory uniqueKey field: item.handle
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.SolrServer.add(SolrServer.java:116)
at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
at org.dspace.xoai.app.XOAI.index(XOAI.java:213)
at org.dspace.xoai.app.XOAI.indexAll(XOAI.java:200)
at org.dspace.xoai.app.XOAI.index(XOAI.java:131)
at org.dspace.xoai.app.XOAI.main(XOAI.java:495)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)

This makes sense in retrospect: the OAI feed includes withdrawn items (in order 
to publish a “record status: deleted” record) but identifies them by their 
handles (so obviously requires a handle).

This is highly disappointing, but at least now we know. It looks like it would 
work for a repository which didn’t publish an OAI feed, but sadly that’s vital 
for us.

Our fall-back will be to follow Claudia’s suggestion of adjusting the Item 
Withdrawn page and using the metadata to point to the new item.

Deborah


From: Tim Donohue 
Sent: Friday, 15 June 2018 2:42 AM
To: Fitchett, Deborah 
Cc: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] handles, isreplacedby, and withdrawn items

Hi Deborah,

I'll admit, I've never tried this myself, but your suggestion to simply update 
the old "handle" table entries to point at the new "resource_id" seems like it 
*should work*.  The "handle" table in DSpace is really just used to 
resolve/assign Handles to Objects.  So, at least conceptually, it should 
support pointing two handles at the same object (Item).

That said, I'd recommend first trying this out on a test or development server. 
 I think it should work, but it'd be worth testing more thoroughly how DSpace 
behaves when one Item object has multiple Handles (and for example, whether 
both handles appear on the Item splash page, etc).  I'd recommend testing basic 
functionality like browse/search/reindex. I suspect they all should work, but 
as this isn't a documented feature, it's worth double checking.

Let us know how it goes (please report back on this list), as this seems like 
it might be of interest to others.

- Tim


On Wed, Jun 13, 2018 at 11:51 PM Fitchett, Deborah 
mailto:deborah.fitch...@lincoln.ac.nz>> wrote:
Kia ora all,

We’re occasionally getting duplicate records created in Dspace with no way to 
resolve the issue other than to withdraw the earlier record and go forward with 
the more recent one.(1)

But of course we don’t really want the handle of the earlier record to result 
in a dead-end – we’d like it to resolve to the new record, or at least be 
redirected there.

We have metadata fields dc.relation.isreplacedby and dc.relation.replaces. 
These seem to have no functional purpose in Dspace (ie it doesn’t do any 
automatic redirects), it’s just information. If the item is *not* withdrawn, I 
could add some javascript to the page to accomplish the redirect that way. But 
I’m not sure it’s the cleanest way.

I’m looking at the handle table in the database and wondering – what if I 
simply find the row with the handle that’s currently linked to the old record, 
and update it to point 

[dspace-tech] DSpace Dev Show and Tell - Aug 28 - DSpace and Docker

[Terry Brady]

In the last month, the DSpace project has created Docker images for the 4
active branches of DSpace and DSpace-angular.  These images will be
automatically rebuilt as changes are merged onto each branch.

The August 28 DSpace Developer Show and Tell will be a demonstration
of the DSpace
Docker Tutorial .  If
you are unfamiliar with Docker, this session will provide an introduction
using DSpace as a sample application.  Meeting logistics are here.

   -
   
https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+Aug+28%2C+2018+-+1500UTC+-+DSpace+On+DockerHub

I hope you will be able to attend.  If you are unable to attend, a meeting
recording will be made available after the session.

Please send me your suggested topic ideas for future DSpace Developer Show
and Tell Meetings.  I will schedule additional meetings as agenda items are
discovered.

Terry
-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
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] SWORDv2 configuration error- Help!

[Andrea Schweer]

And further to that (having tripped over this myself about five minutes
ago) - the url property in that file doesn't carry over to the
collection.url and servicedocument.url properties, so if you use a non
standard "url" value then (as stated in the comments of the file) you'll
have to adjust those two properties as well.

cheers,
Andrea

On Thu, 23 Aug 2018 at 09:23, Andrea Schweer 
wrote:

> Hi,
>
> check what you have configured as the service document URL - probably in
> [dspace]/config/modules/swordv2-server.cfg. It's the first property in that
> file "url". The default is {dspace.url}/swordv2 and the base URL you use in
> your sword deposit must match that exactly.
>
> cheers,
> Andrea
>
> On Thu, 23 Aug 2018 at 09:21,  wrote:
>
>>
>>
>> We're attempting to enable the SWORDv2 endpoint in our DSpace instance
>> for use in a DSpace-Symplectic Elements Repository Tools 2 integration.
>> The service document gives this error: "Unable to recognise URL as a
>> valid service document:..."
>>
>> Does anyone have any insight into what could be causing this error?
>>
>> Here's the full message:
>>
>> http://purl.org/net/sword/terms/; href="
>> http://www.dspace.org/ns/sword/2.0/errors/BadUrl;>
>> http://www.w3.org/2005/Atom;>ERROR
>> http://www.w3.org/2005/Atom;>
>> 2018-08-22T17:05:38Z
>> http://www.w3.org/2005/Atom; uri="
>> http://www.dspace.org/ns/sword/2.0/; version="2.0">[EmailRedacted]
>> 
>> Processing failed
>> http://www.w3.org/2005/Atom;>
>> Unable to recognise URL as a valid service document:
>> http://155.247.166.104:8080/swordv2/servicedocument
>> 
>> 
>> org.swordapp.server.SwordError: Unable to recognise URL as a valid
>> service document: http://155.247.166.104:8080/swordv2/servicedocument at
>> org.dspace.sword2.SwordUrlManager.extractDSpaceObject(SwordUrlManager.java:323)
>> at
>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:169)
>> at
>> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:74)
>> at org.swordapp.server.ServiceDocumentAPI.get(ServiceDocumentAPI.java:56)
>> at
>> org.swordapp.server.servlets.ServiceDocumentServletDefault.doGet(ServiceDocumentServletDefault.java:32)
>> 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.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
>> 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:1087)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> 
>> http://www.w3.org/2005/Atom; rel="alternate" type
>> ="text/html" href="http://localhost:8080/contact"/>
>> 
>>
>> Thanks for any help you can give us!
>>
>> -GG
>>
>> --
>> 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.
>>
>
>
> --
> Dr Andrea Schweer
> Research 

Re: [dspace-tech] SWORDv2 configuration error- Help!

[Andrea Schweer]

Hi,

check what you have configured as the service document URL - probably in
[dspace]/config/modules/swordv2-server.cfg. It's the first property in that
file "url". The default is {dspace.url}/swordv2 and the base URL you use in
your sword deposit must match that exactly.

cheers,
Andrea

On Thu, 23 Aug 2018 at 09:21,  wrote:

>
>
> We're attempting to enable the SWORDv2 endpoint in our DSpace instance for
> use in a DSpace-Symplectic Elements Repository Tools 2 integration.  The
> service document gives this error: "Unable to recognise URL as a valid
> service document:..."
>
> Does anyone have any insight into what could be causing this error?
>
> Here's the full message:
>
> http://purl.org/net/sword/terms/; href="
> http://www.dspace.org/ns/sword/2.0/errors/BadUrl;>
> http://www.w3.org/2005/Atom;>ERROR
> http://www.w3.org/2005/Atom;>
> 2018-08-22T17:05:38Z
> http://www.w3.org/2005/Atom; uri="
> http://www.dspace.org/ns/sword/2.0/; version="2.0">[EmailRedacted]
> 
> Processing failed
> http://www.w3.org/2005/Atom;>
> Unable to recognise URL as a valid service document:
> http://155.247.166.104:8080/swordv2/servicedocument
> 
> 
> org.swordapp.server.SwordError: Unable to recognise URL as a valid service
> document: http://155.247.166.104:8080/swordv2/servicedocument at
> org.dspace.sword2.SwordUrlManager.extractDSpaceObject(SwordUrlManager.java:323)
> at
> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:169)
> at
> org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:74)
> at org.swordapp.server.ServiceDocumentAPI.get(ServiceDocumentAPI.java:56)
> at
> org.swordapp.server.servlets.ServiceDocumentServletDefault.doGet(ServiceDocumentServletDefault.java:32)
> 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.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
> 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:1087)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
> 
> http://www.w3.org/2005/Atom; rel="alternate" type="
> text/html" href="http://localhost:8080/contact"/>
> 
>
> Thanks for any help you can give us!
>
> -GG
>
> --
> 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.
>


-- 
Dr Andrea Schweer
Research Technologies Manager, ITS Programme & Commercial
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120

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

[dspace-tech] SWORDv2 configuration error- Help!

[tuf04742]

We're attempting to enable the SWORDv2 endpoint in our DSpace instance for 
use in a DSpace-Symplectic Elements Repository Tools 2 integration.  The 
service document gives this error: "Unable to recognise URL as a valid 
service document:..." 

Does anyone have any insight into what could be causing this error?  

Here's the full message: 

http://purl.org/net/sword/terms/; href="
http://www.dspace.org/ns/sword/2.0/errors/BadUrl;>
http://www.w3.org/2005/Atom;>ERROR
http://www.w3.org/2005/Atom;>2018-08-22T17:05:38Z

http://www.w3.org/2005/Atom; uri="
http://www.dspace.org/ns/sword/2.0/; version="2.0">[EmailRedacted]

Processing failed
http://www.w3.org/2005/Atom;>
Unable to recognise URL as a valid service document: 
http://155.247.166.104:8080/swordv2/servicedocument


org.swordapp.server.SwordError: Unable to recognise URL as a valid service 
document: http://155.247.166.104:8080/swordv2/servicedocument at 
org.dspace.sword2.SwordUrlManager.extractDSpaceObject(SwordUrlManager.java:323) 
at 
org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:169)
 
at 
org.dspace.sword2.ServiceDocumentManagerDSpace.getServiceDocument(ServiceDocumentManagerDSpace.java:74)
 
at org.swordapp.server.ServiceDocumentAPI.get(ServiceDocumentAPI.java:56) 
at 
org.swordapp.server.servlets.ServiceDocumentServletDefault.doGet(ServiceDocumentServletDefault.java:32)
 
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.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
 
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
 
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
 
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) 
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) 
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962) 
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:1087)
 
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
 
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 
at java.lang.Thread.run(Thread.java:748)

http://www.w3.org/2005/Atom; rel="alternate" type="
text/html" href="http://localhost:8080/contact"/>


Thanks for any help you can give us!  

-GG

-- 
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] Bug in ORCID v2 implementation?

[Darryl Friesen]

I was happy to see the return of ORCID in 6.3, however I'm experiencing 
some odd behavior which I think may be a bug.

Using the Lookup button, the initial interaction with the OCRID v2 API 
seems to work great

[image: orcid_bug_01.png] 



A match is found, I can see the ORCID and I can add that person as an 
author. An entry is written in the Solr autority database.


[image: orcid_bug_02.png] 

However, if the Lookup button is used again with that same author's name, 
not only is the current entry from authority control returned, but an 
additional hit from OCRID appears (shown in yellow in the image below).  To 
add to the confusion, the current hit from authority control does *not* show 
the ORCID, even though is it recorded in the Solr database.


[image: orcid_bug_03.png] 


This differs from the previous behavior with DSpace and the ORCID v1 API.  
I'm sure matches from the local authority control database *would* display 
the ORCID, and if a hit from the ORCID API matched an existing entry in 
authority control, it would not be displayed in italics as a new author.


If I go ahead and select the new italicized author in the above scenario, 
DSpace will create a duplicate entry in the authority control database.  
The records will have different record IDs, but the data, including the 
ORCID ID, is the same.


[image: orcid_bug_04.png] 



This process can repeat; each time you lookup an author, an additional new 
entry from ORCID will appear as new, and if selected, and additional 
authority control record will be created.

I'm seeing this behavior on my test server (running DSpace 6.4-SNAPSHOT 
checked out of GitHub lat week) but I also see the same behavior on the 
DSpace 6.3 demo site, so I don't believe it's an issue with my 
configuration.

Does this sound like a bug?  Is anyone else using ORCID v2 integration 
experiencing this behavior?

- Darryl


--

Darryl Friesen, B.Sc., Programmer/Analystdarryl.frie...@usask.ca

Library Systems & Information Technology,http://library.usask.ca/

University of Saskatchewan Library

--

"Go not to the Elves for counsel, for they will say both no and yes"

-- 
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] Should I upgrade my DSpace?

[Tim Donohue]

Hello,

Whether you upgrade is really a local decision. It recent years, DSpace
Developers have put significant effort into ensuring your *data*
(files/database) upgrades automatically.

So, moving your data to the latest version of DSpace is vastly simplified
(and usually completely automated, assuming you haven't modified the
underlying database structure). See
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace

As for what DSpace 6 provides over DSpace 5, you should check out the 6.0
Release Notes:
https://wiki.duraspace.org/display/DSDOC6x/Release+Notes#ReleaseNotes-6.0ReleaseNotes


Besides just moving to Hibernate, there's a brand new Configuration System
(which makes local configuration easier to manage, via a local.cfg file),
and some new features to the REST API, XMLUI, etc.

That all said, you are also welcome to wait and upgrade from 5.x to 7.x
directly.  Just keep in mind, you would still need to adopt the new
Configuration System (introduced in 6.x)...it's just a matter of whether
you adopt that now or later.

- Tim

On Tue, Aug 21, 2018 at 9:01 AM Brendow Adriel  wrote:

> Currently we use version 5.x of dspace and how much should I upgrade to
> version 6.x? Or should I expect REST version 7.x?
> I realize that the architectural change is considerable because they use
> Hibernate and the removal of some resources.
> Is the upgrade process favorable to version 5.x?
> Remembering also that specific features have been built to meet the needs
> of our organization.
> Some features that I believe are favorable even for the communities and in
> the near future I will share with the community when I have time.
>
> --
> 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.
>
-- 
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+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] how can I use metadata in a data repository

[Tim Donohue]

Hello Habibi,

Here's the metadata schemas/fields that come out of the box with DSpace:
https://wiki.duraspace.org/display/DSDOC6x/Metadata+and+Bitstream+Format+Registries

You can add custom schemas/fields, but they must be of the same general
format as Qualified Dublin Core.  That format is
[schema].[element].[qualifier].

If there are fields you wish to store which do NOT fit well into Dublin
Core, we usually recommend creating a "local" schema (you can name it
whatever you want). You can then define any elements and qualifiers you
want within that schema.  For more information on the "local" schema and
other general metadata recommendations, see
https://wiki.duraspace.org/display/DSDOC6x/Metadata+Recommendations

Good luck, and let us know on this mailing list if you have other specific
questions.

Tim

On Mon, Aug 13, 2018 at 4:00 AM shafi' Habibi  wrote:

> I'm going to launch a data repositoryusing Dspace. I have a few questions
> that I would appreciated if you answer:
> 1- Which metadata can be used?
> 2. If I use Dublincore, how can I define, for example the type of data,
> variables type, and the number of samples and ...?
>
> Habibi
> Tabriz University of Medical Sciences
>
> --
> 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.
>
-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Notification "DSpace: Submission Approved and Archived" on email

[Tim Donohue]

Hello,

Unfortunately, at this time, you can only turn off the entire mail server,
and not individual notifications.

If you want DSpace to no longer send any emails, you can uncomment this
configuration (in dspace.cfg or local.cfg) and set it to "true"

mail.server.disabled = false

Here's where it exists in the dspace.cfg file:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L163

Disabling an individual notification like that "Submission Approved and
Archived" email would require changing the Java code in DSpace.

Here's the DSpace 6.x Java class where that specific email is sent:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/workflowbasic/BasicWorkflowServiceImpl.java#L802

- Tim

On Mon, Aug 20, 2018 at 2:12 AM  wrote:

> So? No one knows how to turn off this function?
>
> среда, 8 августа 2018 г., 17:03:29 UTC+3 пользователь repozit...@gmail.com
> написал:
>
>> Hello. Can you help us please to understand how to turn off email message
>> notifications like "DSpace: Submission Approved and Archived" in DSpace
>> configuration?
>> Thanks alot.
>>
> --
> 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.
>
-- 
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+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] Deleting item using REST API results in restrictions on reading parent community/collections

[MALMQUIST Hrafn]

Hi there


Running DSpace 6.2.


After deleting a number of items using the REST API

DELETE {rest_url}/items/{item id} - Delete item.


Some of which were in a collection with restricted read access.


I find that neither it's parent community nor collections can be viewed (read) 
unless I am logged in.


2018-08-22 15:20:15,060 INFO  org.dspace.usage.LoggerUsageEventListener @ 
anonymous:session_id=6799FEA4BF071AC1393F768B8913A8E9:ip_addr=129.215.240.52:view_community:community_id=ae51bb74-5cb0-47c6-80be-8818db8b3d12
2018-08-22 15:20:26,576 ERROR 
org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter @ Client closed the 
connection before file download was complete

resulting in a 502

but if I'm logged in:

2018-08-22 15:19:54,519 INFO  org.dspace.usage.LoggerUsageEventListener @ 
u...@address.com:session_id=6119E1EDE735C30EF0D8D17C82F0A550:ip_addr=129.215.240.52:view_community:community_id=ae51bb74-5cb0-47c6-80be-8818db8b3d12

and the community is displayed

I don't understand what's happening.

Any help greatly appreciated.

Hrafn Malmquist

-- 
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.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

-- 
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] Cascading Dropdowns in submission

[Tim Donohue]

Hello Abhishek,

Unfortunately, DSpace doesn't support cascading dropdowns out-of-the-box.
You'd likely need to look for a third-party library (perhaps a Javascript
library) to help you achieve this sort of customization.

Hopefully, if others have done this locally they will respond to this
thread.

Tim

On Tue, Aug 21, 2018 at 9:37 PM Abhishek Madas  wrote:

> Hi
> we are using dspace 1.8.2 and I am trying to modify our submission flow to
> include inter-dependent dropdown fields (cascading)
> such as if I Select Fruits: I see the next dropdown option display :
> Apples, Oranges,avocados and if I select Vegetables I see: Spinach, Kale,
> Cabbage
> How can I achieve such a behavior.
> Thanks.,
> Abhishek
>
> --
> 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.
>
-- 
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+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] How to edit a bitstream?

[Tim Donohue]

Hi Evgeni,

I *think* that's why DS-3979 exists...cause it's a bug. I admit, though, I
haven't had a chance to review that ticket or the PR associated myself.
So, I'd recommend commenting directly on the ticket or PR and ask how to
reproduce this problem.  It might clarify to you (and me) what the actual
bug is.

- Tim

On Wed, Aug 22, 2018 at 9:24 AM Evgeni Dimitrov 
wrote:

> Thank you Tim,
>
> I really did not know this. But still I don't see why change of the
> filename or the format should affect the authorization policy of the
> bitstream.
>
> Best regards
> Evgeni
>
> On Wednesday, August 22, 2018 at 5:09:04 PM UTC+3, Tim Donohue wrote:
>
>> Hi Evgeni,
>>
>> This DS-3979 issue is referring to editing a bitstream's *metadata* (not
>> the actual file associated with the bitstream).  A bitstream's metadata is
>> editable from the UI, but the file itself is not editable (you can only
>> upload a new file).
>>
>> Here's how you get to the edit a bitstream's metadata in XMLUI:
>> * Login, and browse to the Item
>> * Edit the Item
>> * Click on "Item Bitstreams" tab
>> * Click on the Bitstream name. You'll then be on the "Edit Bitstream" page
>>
>> - Tim
>>
>> On Wed, Aug 22, 2018 at 4:01 AM Evgeni Dimitrov 
>> wrote:
>>
> In issue DS-3979 I noticed a comment:
>>>
>>> Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM
>>>
>>> Without this in place, if DEFAULT_ITEM_READ is Anonymous and
>>> DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will
>>> add an Anonymous READ policy, making the bitstream public again.
>>>
>>> I don't know how to "edit a bitstream" and how editing can add a policy
>>> to it. Can somebody shed some light on this?
>>>
>>>
>>> --
>>> 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+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

-- 
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] How to edit a bitstream?

[Evgeni Dimitrov]

Thank you Tim,

I really did not know this. But still I don't see why change of the 
filename or the format should affect the authorization policy of the 
bitstream.

Best regards
Evgeni

On Wednesday, August 22, 2018 at 5:09:04 PM UTC+3, Tim Donohue wrote:
>
> Hi Evgeni,
>
> This DS-3979 issue is referring to editing a bitstream's *metadata* (not 
> the actual file associated with the bitstream).  A bitstream's metadata is 
> editable from the UI, but the file itself is not editable (you can only 
> upload a new file).
>
> Here's how you get to the edit a bitstream's metadata in XMLUI:
> * Login, and browse to the Item
> * Edit the Item
> * Click on "Item Bitstreams" tab
> * Click on the Bitstream name. You'll then be on the "Edit Bitstream" page
>
> - Tim
>
> On Wed, Aug 22, 2018 at 4:01 AM Evgeni Dimitrov  > wrote:
>
>> In issue DS-3979 I noticed a comment:
>>
>> Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM
>>
>> Without this in place, if DEFAULT_ITEM_READ is Anonymous and 
>> DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will 
>> add an Anonymous READ policy, making the bitstream public again.
>>
>> I don't know how to "edit a bitstream" and how editing can add a policy 
>> to it. Can somebody shed some light on this?
>>
>>
>> -- 
>> 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+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] How to edit a bitstream?

[Tim Donohue]

Hi Evgeni,

This DS-3979 issue is referring to editing a bitstream's *metadata* (not
the actual file associated with the bitstream).  A bitstream's metadata is
editable from the UI, but the file itself is not editable (you can only
upload a new file).

Here's how you get to the edit a bitstream's metadata in XMLUI:
* Login, and browse to the Item
* Edit the Item
* Click on "Item Bitstreams" tab
* Click on the Bitstream name. You'll then be on the "Edit Bitstream" page

- Tim

On Wed, Aug 22, 2018 at 4:01 AM Evgeni Dimitrov 
wrote:

> In issue DS-3979 I noticed a comment:
>
> Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM
>
> Without this in place, if DEFAULT_ITEM_READ is Anonymous and
> DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will
> add an Anonymous READ policy, making the bitstream public again.
>
> I don't know how to "edit a bitstream" and how editing can add a policy to
> it. Can somebody shed some light on this?
>
>
> --
> 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.
>
-- 
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+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] xmlui issue: port 80 and 8080 is working but 6060 issues server not working

[Sneha]

Hi,

My dspace service was working perfectly.  However, some issues with my IBM 
server occurred which was resolved.  Now all my services are working 
perfectly except xmlui interface (503 Service Unavailable).  Other services 
are configured on 8080 and they work perfectly.  However, the xmlui 
interface which runs on port 6060 is not responding and is giving following 
error: 

Service Unavailable

The server is temporarily unable to service your request due to maintenance 
downtime or capacity problems. Please try again later.
--
Apache/2.4.18 (Ubuntu) Server at dl.bhu.ac.in Port 80

Also, the cocoon file has no log report since the day server error occurred.

Version: DSpace 6.0
xmlui interface uri: localhost:6060/xmlui

Please help as my service was running a live repository of my institution.

Thanks.





-- 
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] ORCID Confidence

[Shaun donovan]

Hi all.

I have noticed that when an author is added using the ORCID lookup 
during the submission process (and choosing an Orcid author), a 
confidence is attributed to that metadata entry (600), but if one edits 
the metadata after submission and adds an author (also using the ORCID 
lookup), no confidence is attributed (0).


This is on version 6.3.

Is this a bug?

Kind Regards.
Shaun

--
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] How to edit a bitstream?

[Evgeni Dimitrov]

In issue DS-3979 I noticed a comment:

Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM

Without this in place, if DEFAULT_ITEM_READ is Anonymous and
DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will
add an Anonymous READ policy, making the bitstream public again.

I don't know how to "edit a bitstream" and how editing can add a policy to
it. Can somebody shed some light on this?

-- 
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] Export a collection

[emilio lorenzo]

Hi Freddy

either a SIP export  (and then Import)   or an AIP export  (small 
differences in the behaviour), followed by an import into the new 
repository wold serve


See in 
https://wiki.duraspace.org/display/DSDOC6x/Exchanging+Content+Between+Repositories 



1. Transferring Content via Export and Import
2. Transferring Items using Simple Archive Format

Beware of export options (duplication of handles, etc...)

Best

Emilio



El 22/08/2018 a las 9:14, Freddy Guerrero escribió:
Hello friends, I need to export a collection with more than 2000 items 
and their files (bitstream), and then import into another repository, 
what would the procedure be?.  I have administrator profile in both 
repositories (origin and destination)


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


--
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] Export a collection

[Freddy Guerrero]

Hello friends, I need to export a collection with more than 2000 items and 
their files (bitstream), and then import into another repository, what 
would the procedure be?.  I have administrator profile in both repositories 
(origin and destination)

Freddy

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