[dspace-tech] Re: HTTPS and SOLR

2019-02-28 Thread Freddy Guerrero
Hi, please help me, I just set up dspace with https, I use  apache tomcat 
7, and I have the following error:


2019-03-01 01:58:31,497 ERROR 
org.dspace.app.webui.components.RecentSubmissionsManager @ caught 
exception: 
org.dspace.browse.BrowseException: 
org.dspace.discovery.SearchServiceException: Server at 
http://localhost/solr/search sent back a redirect (302).
at org.dspace.browse.SolrBrowseDAO.getSolrResponse(SolrBrowseDAO.java:206)
at org.dspace.browse.SolrBrowseDAO.doQuery(SolrBrowseDAO.java:315)
at org.dspace.browse.BrowseEngine.browseMini(BrowseEngine.java:167)
at 
org.dspace.app.webui.components.RecentSubmissionsManager.getRecentSubmissions(RecentSubmissionsManager.java:90)
at 
org.dspace.app.webui.components.RecentCommunitySubmissions.process(RecentCommunitySubmissions.java:48)
at 
org.dspace.app.webui.servlet.HandleServlet.preProcessCommunityHome(HandleServlet.java:641)
at 
org.dspace.app.webui.servlet.HandleServlet.communityHome(HandleServlet.java:591)
at 
org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:329)
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:603)
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: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)
Caused by: org.dspace.discovery.SearchServiceException: Server at 
http://localhost/solr/search sent back a redirect (302).
at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1615)
at org.dspace.browse.SolrBrowseDAO.getSolrResponse(SolrBrowseDAO.java:201)
... 37 more
Caused by: org.apache.solr.client.solrj.SolrServerException: Server at 
http://localhost/solr/search sent back a redirect (302).
at 
org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:470)
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.QueryRequest.process(QueryRequest.java:91)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1610)
... 38 more
2019-03-01 01:58:31,497 ERROR org.dspace.app.webui.servlet.HandleServlet @ 
caught exception: 
org.dspace.plugin.PluginException: 
org.dspace.app.webui.components.RecentSubmissionsException: 
org.dspace.browse.BrowseException: 
org.dspace.discovery.SearchServiceException: Server at 
http://localhost/solr/search sent back a redirect (302).
at 

[dspace-tech] DSpace build Mirage2 issue

2019-02-28 Thread Sunita Barve
Even after building dspace successfully with mirage2 the screen looks like 
attached screen. 

Can someone help to solve the issue.


with reg

Dr. Sunita Barve
KRC/Library
CSIR-NCL, Pune

-- 
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: ERROR oai import

2019-02-28 Thread Freddy Guerrero
Thanks Tim for your answer, can someone provide us with a recommendation on 
how to identify the records that do not contain the license files?

Regards




El martes, 26 de febrero de 2019, 0:04:39 (UTC-5), Freddy Guerrero escribió:
>
> Hi, I use dspace v. 6.3, jspui, and when executing "dspace oai import ", 
> I get this error:
>
> java.lang.NullPointerException
> at org.dspace.storage.bitstore.BitstreamStorageServiceImpl.retr
> ieve(BitstreamStorageServiceImpl.java:216)
> at org.dspace.content.BitstreamServiceImpl.retrieve(BitstreamSe
> rviceImpl.java:309)
> at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.
> java:298)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:421)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:280)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:179)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:145)
> at org.dspace.xoai.app.XOAI.main(XOAI.java:560)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptL
> auncher.java:229)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.
> java:81)
>

-- 
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] Embargo Feature Does Not Work

2019-02-28 Thread Herminarto Nugroho
Hi Tim,

Thanks for the reply.

I am attempting to access the file after logging out (it means I am 
anonymous), and still able to access the file.

Indeed, as an Admin I can modify the access policy of an existing file such 
that that particular item can only be accessed after a certain date.

The problem is when the user wants to submit new files, and decided to set 
the embargo feature ON, the embargo feature in the submission process does 
not work well. I assume the problem is in the format of the date, but I am 
not sure. When I tried to submit a file and set the embargo,the date format 
does not match the accepted format. as you can see in the attached figure.

Then I try to use JSPUI as well. The embargo still does not work, and even 
I cannot specify the date at all.

[image: Screenshot_2.jpg] 
Best regards,

Herminarto

Pada Kamis, 28 Februari 2019 23.51.37 UTC+7, Tim Donohue menulis:
>
> Hello Herminarto,
>
> I'm not sure if this is the problem, but is it possible that you are 
> attempting to access the embargoed item *while you are logged in as an 
> Administrator*?
>
> Embargoes should take effect immediately. However, Administrative users 
> are *not* subject to those embargoes, and they will still be able to 
> download the items while they are logged in.  All other logged in users 
> (and anonymous users) should not be able to download the item.
>
> If this is not the problem, you might want to look more closely at the 
> "start_date" set on the policy for the embargoed Item.  Embargoes in DSpace 
> essentially act as an access policy that doesn't trigger until a particular 
> date has passed. You can see that "start_date" in the Admin Edit Item 
> screens.  Here's a guide on where to find this information: 
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems
>
> You also might want to verify in the DSpace logs that no errors are 
> occurring when you assign the embargo to a new Item.
>
> Please report back on this mailing list with anything you find or if you 
> discover what the problem is.
>
> Thanks,
>
> Tim
>
>
> On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho  > wrote:
>
>> Dear all,
>>
>> I tried to enable the embargo feature by following the instruction from 
>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
>>  
>> .
>> I am using dspace 6.3 with xmlui. It seems everything's going ok, but 
>> when I try to submit a document with embargo, I specified the date the 
>> embargo should be lifted long way on the future, my document can still be 
>> downloaded freely right after my submission complete (which means the 
>> embargo does not work). When I see the column in which I mention embargo 
>> until specific date, it seems the date format is not accepted. Is that 
>> really the cause? How can I solve this problem?
>>
>> Best regards,
>>
>> Herminarto Nugroho
>>
>> -- 
>> 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] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-02-28 Thread Tim Donohue
Hi David,

You are correct, this is related to the bug report in DS-2824.  The problem
is that you seem to have somehow created two Groups of the *same name*. In
your situation, the errors is saying you have two groups named
"COLLECTION_29_DEFAULT_READ".  Group Names are supposed to be unique (and
uniqueness is now guaranteed at the database level).  This is a very rare
scenario, as DSpace should have never allowed two groups of the same name
to be created. But, somehow this seems to have occurred at least a few
times (on your site, and on the site that reported bug DS-2824).

In any case, the fix should be to look for two groups named
COLLECTION_29_DEFAULT_READ (this group is named oddly because it is the
group that is providing DEFAULT_READ permissions to your Collection with
ID=29). Figure out which one is the correct one, and delete the other one.
If you rerun the migration it should now succeed (again assuming there are
no other duplicative groups -- but there hopefully should not be).

Good luck,

Tim



On Thu, Feb 28, 2019 at 2:29 PM David Baker  wrote:

> Anybody have any ideas why I'm running into this?
> I found this bug report https://jira.duraspace.org/browse/DS-2824 but
> don't understand how the issue was resolved in that case.
> Thanks.
>
>
> On Thursday, February 28, 2019 at 3:27:27 PM UTC-5, David Baker wrote:
>>
>> I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3
>>
>> Here's the output of bin\dspace database info:
>>
>> Using DSpace installation in: c:\dspace
>>
>> Database Type: postgres
>> Database URL: jdbc:postgresql://localhost:5432/dspace
>> Database Schema: public
>> Database Username: dspace
>> Database Software: PostgreSQL version 9.4.17
>> Database Driver: PostgreSQL JDBC Driver version 42.2.1
>> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>>
>>
>> ++-+-+-+
>> | Version| Description |
>> Installed on| State   |
>>
>> ++-+-+-+
>> | 1  | << Flyway Init >>   |
>> 2015-06-09 12:16:21 | Baselin |
>> | 1.1| Initial DSpace 1.1 database schema  |
>> 2015-06-09 12:16:22 | Success |
>> | 1.2| Upgrade to DSpace 1.2 schema|
>> 2015-06-09 12:16:22 | Success |
>> | 1.3| Upgrade to DSpace 1.3 schema|
>> 2015-06-09 12:16:22 | Success |
>> | 1.3.9  | Drop constraint for DSpace 1 4 schema   |
>> 2015-06-09 12:16:23 | Success |
>> | 1.4| Upgrade to DSpace 1.4 schema|
>> 2015-06-09 12:16:23 | Success |
>> | 1.5| Upgrade to DSpace 1.5 schema|
>> 2015-06-09 12:16:23 | Success |
>> | 1.5.9  | Drop constraint for DSpace 1 6 schema   |
>> 2015-06-09 12:16:24 | Success |
>> | 1.6| Upgrade to DSpace 1.6 schema|
>> 2015-06-09 12:16:24 | Success |
>> | 1.7| Upgrade to DSpace 1.7 schema|
>> 2015-06-09 12:16:24 | Success |
>> | 1.8| Upgrade to DSpace 1.8 schema|
>> 2015-06-09 12:16:24 | Success |
>> | 3.0| Upgrade to DSpace 3.x schema|
>> 2015-06-09 12:16:24 | Success |
>> | 4.0| Upgrade to DSpace 4.x schema|
>> 2015-06-09 12:16:24 | Success |
>> | 4.9.2015.10.26 | DS-2818 registry update
>> | | Ignored |
>> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy |
>> 2015-06-09 12:16:24 | Success |
>> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint|
>> 2015-06-09 12:16:24 | Success |
>> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects|
>> 2015-06-09 12:16:24 | Success |
>> | 5.6.2016.08.23 | DS-3097 |
>> 2019-02-28 14:52:18 | Success |
>> | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column |
>> 2019-02-28 14:52:20 | Success |
>> | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  |
>> 2019-02-28 14:52:21 | Success |
>> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  |
>> 2019-02-28 14:52:22 | Success |
>> | 6.0.2015.03.07 | DS-2701 Hibernate migration |
>> 2019-02-28 14:52:23 | Success |
>> | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration|
>> 2019-02-28 14:54:57 | Success |
>> | 6.0.2016.01.03 | DS-3024 |
>> 2019-02-28 14:54:57 | Success |
>> | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   |
>> 2019-02-28 14:54:58 | Success |
>> | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin
>> |  

[dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-02-28 Thread David Baker
Anybody have any ideas why I'm running into this?
I found this bug report https://jira.duraspace.org/browse/DS-2824 but don't 
understand how the issue was resolved in that case.
Thanks.


On Thursday, February 28, 2019 at 3:27:27 PM UTC-5, David Baker wrote:
>
> I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3
>
> Here's the output of bin\dspace database info:
>
> Using DSpace installation in: c:\dspace
>
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 9.4.17
> Database Driver: PostgreSQL JDBC Driver version 42.2.1
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>
>
> ++-+-+-+
> | Version| Description | 
> Installed on| State   |
>
> ++-+-+-+
> | 1  | << Flyway Init >>   | 
> 2015-06-09 12:16:21 | Baselin |
> | 1.1| Initial DSpace 1.1 database schema  | 
> 2015-06-09 12:16:22 | Success |
> | 1.2| Upgrade to DSpace 1.2 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3| Upgrade to DSpace 1.3 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
> 2015-06-09 12:16:23 | Success |
> | 1.4| Upgrade to DSpace 1.4 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5| Upgrade to DSpace 1.5 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
> 2015-06-09 12:16:24 | Success |
> | 1.6| Upgrade to DSpace 1.6 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.7| Upgrade to DSpace 1.7 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.8| Upgrade to DSpace 1.8 schema| 
> 2015-06-09 12:16:24 | Success |
> | 3.0| Upgrade to DSpace 3.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.0| Upgrade to DSpace 4.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.9.2015.10.26 | DS-2818 registry update 
> | | Ignored |
> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
> 2015-06-09 12:16:24 | Success |
> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
> 2015-06-09 12:16:24 | Success |
> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 
> 2015-06-09 12:16:24 | Success |
> | 5.6.2016.08.23 | DS-3097 | 
> 2019-02-28 14:52:18 | Success |
> | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 
> 2019-02-28 14:52:20 | Success |
> | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  | 
> 2019-02-28 14:52:21 | Success |
> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  | 
> 2019-02-28 14:52:22 | Success |
> | 6.0.2015.03.07 | DS-2701 Hibernate migration | 
> 2019-02-28 14:52:23 | Success |
> | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration| 
> 2019-02-28 14:54:57 | Success |
> | 6.0.2016.01.03 | DS-3024 | 
> 2019-02-28 14:54:57 | Success |
> | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   | 
> 2019-02-28 14:54:58 | Success |
> | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin 
> | | Pending |
> | 6.0.2016.04.01 | DS-1955 Increase embargo reason 
> | | Pending |
> | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix 
> | | Pending |
> | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights  
> | | Pending |
> | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column  
> | | Pending |
> | 6.0.2016.07.21 | DS-2775 
> | | Pending |
> | 6.0.2016.07.26 | DS-3277 fix handle assignment   
> | | Pending |
> | 6.0.2016.08.23 | DS-3097 
> | | Pending |
> | 6.1.2017.01.03 | DS 3431 Add Policies for BasicWorkflow  
> | | Pending |
>
> ++-+-+-+
>
>
> Then there's this in my dspace.log file:
>
>
> 2019-02-28 

[dspace-tech] Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-02-28 Thread David Baker
I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3

Here's the output of bin\dspace database info:

Using DSpace installation in: c:\dspace

Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 9.4.17
Database Driver: PostgreSQL JDBC Driver version 42.2.1
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)

++-+-+-+
| Version| Description | 
Installed on| State   |
++-+-+-+
| 1  | << Flyway Init >>   | 
2015-06-09 12:16:21 | Baselin |
| 1.1| Initial DSpace 1.1 database schema  | 
2015-06-09 12:16:22 | Success |
| 1.2| Upgrade to DSpace 1.2 schema| 
2015-06-09 12:16:22 | Success |
| 1.3| Upgrade to DSpace 1.3 schema| 
2015-06-09 12:16:22 | Success |
| 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
2015-06-09 12:16:23 | Success |
| 1.4| Upgrade to DSpace 1.4 schema| 
2015-06-09 12:16:23 | Success |
| 1.5| Upgrade to DSpace 1.5 schema| 
2015-06-09 12:16:23 | Success |
| 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
2015-06-09 12:16:24 | Success |
| 1.6| Upgrade to DSpace 1.6 schema| 
2015-06-09 12:16:24 | Success |
| 1.7| Upgrade to DSpace 1.7 schema| 
2015-06-09 12:16:24 | Success |
| 1.8| Upgrade to DSpace 1.8 schema| 
2015-06-09 12:16:24 | Success |
| 3.0| Upgrade to DSpace 3.x schema| 
2015-06-09 12:16:24 | Success |
| 4.0| Upgrade to DSpace 4.x schema| 
2015-06-09 12:16:24 | Success |
| 4.9.2015.10.26 | DS-2818 registry update 
| | Ignored |
| 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
2015-06-09 12:16:24 | Success |
| 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
2015-06-09 12:16:24 | Success |
| 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 
2015-06-09 12:16:24 | Success |
| 5.6.2016.08.23 | DS-3097 | 
2019-02-28 14:52:18 | Success |
| 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 
2019-02-28 14:52:20 | Success |
| 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  | 
2019-02-28 14:52:21 | Success |
| 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  | 
2019-02-28 14:52:22 | Success |
| 6.0.2015.03.07 | DS-2701 Hibernate migration | 
2019-02-28 14:52:23 | Success |
| 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration| 
2019-02-28 14:54:57 | Success |
| 6.0.2016.01.03 | DS-3024 | 
2019-02-28 14:54:57 | Success |
| 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   | 
2019-02-28 14:54:58 | Success |
| 6.0.2016.02.25 | DS-3004-slow-searching-as-admin 
| | Pending |
| 6.0.2016.04.01 | DS-1955 Increase embargo reason 
| | Pending |
| 6.0.2016.04.04 | DS-3086-OAI-Performance-fix 
| | Pending |
| 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights  
| | Pending |
| 6.0.2016.05.10 | DS-3168-fix-requestitem item id column  
| | Pending |
| 6.0.2016.07.21 | DS-2775 
| | Pending |
| 6.0.2016.07.26 | DS-3277 fix handle assignment   
| | Pending |
| 6.0.2016.08.23 | DS-3097 
| | Pending |
| 6.1.2017.01.03 | DS 3431 Add Policies for BasicWorkflow  
| | Pending |
++-+-+-+


Then there's this in my dspace.log file:


2019-02-28 14:54:58,834 INFO  org.flywaydb.core.internal.command.DbMigrate 
@ Migrating schema "public" to version 6.0.2016.02.25 - 
DS-3004-slow-searching-as-admin
2019-02-28 14:54:58,928 INFO  
org.flywaydb.core.internal.dbsupport.JdbcTemplate @ DB: column "name" of 
relation "epersongroup" does not exist, skipping
2019-02-28 14:54:59,537 ERROR org.flywaydb.core.internal.command.DbMigrate 
@ Migration of schema "public" to version 6.0.2016.02.25 - 

Re: [dspace-tech] ERROR oai import

2019-02-28 Thread Tim Donohue
Hi Freddy,

That error seems to be saying that one of your Item's License files is
missing. Here's the OAI code that is throwing the NullPointerException
(after the License bitstream cannot be retrieved):
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-oai/src/main/java/org/dspace/xoai/util/ItemUtils.java#L298

OAI import attempts to add the content of any License files to a "license"
field (for some metadata formats).  Here's an example from the demo site,
where you can see a "DSpaceDepositLicense" when you ask for
"metadataPrefix=mets":
http://demo.dspace.org/oai/request?verb=GetRecord=mets=oai:demo.dspace.org:10673/5


In any case, it sounds like one of your Item's has an associated Bitstream
object (that represents a License), but that Bitstream's content is missing
from your filesystem.  I'm not sure if there's an easy way to track down
the exact item, but you might look more closely at the log files *just
before* this error occurs to see if OAI is logging exactly which Item it is
attempting to import when this happens.

Good luck, and let us know on this list if you have further questions.

Tim



On Mon, Feb 25, 2019 at 11:04 PM Freddy Guerrero 
wrote:

> Hi, I use dspace v. 6.3, jspui, and when executing "dspace oai import ",
> I get this error:
>
> java.lang.NullPointerException
> at org.dspace.storage.bitstore.BitstreamStorageServiceImpl.retr
> ieve(BitstreamStorageServiceImpl.java:216)
> at org.dspace.content.BitstreamServiceImpl.retrieve(BitstreamSe
> rviceImpl.java:309)
> at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.
> java:298)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:421)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:280)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:179)
> at org.dspace.xoai.app.XOAI.index(XOAI.java:145)
> at org.dspace.xoai.app.XOAI.main(XOAI.java:560)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptL
> auncher.java:229)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.
> java:81)
>
> --
> 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] Embargo Feature Does Not Work

2019-02-28 Thread Tim Donohue
Hello Herminarto,

I'm not sure if this is the problem, but is it possible that you are
attempting to access the embargoed item *while you are logged in as an
Administrator*?

Embargoes should take effect immediately. However, Administrative users are
*not* subject to those embargoes, and they will still be able to download
the items while they are logged in.  All other logged in users (and
anonymous users) should not be able to download the item.

If this is not the problem, you might want to look more closely at the
"start_date" set on the policy for the embargoed Item.  Embargoes in DSpace
essentially act as an access policy that doesn't trigger until a particular
date has passed. You can see that "start_date" in the Admin Edit Item
screens.  Here's a guide on where to find this information:
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems

You also might want to verify in the DSpace logs that no errors are
occurring when you assign the embargo to a new Item.

Please report back on this mailing list with anything you find or if you
discover what the problem is.

Thanks,

Tim


On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho <
herminarto.nugr...@gmail.com> wrote:

> Dear all,
>
> I tried to enable the embargo feature by following the instruction from
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
> .
> I am using dspace 6.3 with xmlui. It seems everything's going ok, but when
> I try to submit a document with embargo, I specified the date the embargo
> should be lifted long way on the future, my document can still be
> downloaded freely right after my submission complete (which means the
> embargo does not work). When I see the column in which I mention embargo
> until specific date, it seems the date format is not accepted. Is that
> really the cause? How can I solve this problem?
>
> Best regards,
>
> Herminarto Nugroho
>
> --
> 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] Embargo Feature Does Not Work

2019-02-28 Thread Herminarto Nugroho
Dear all,

I tried to enable the embargo feature by following the instruction from 
https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings
 
.
I am using dspace 6.3 with xmlui. It seems everything's going ok, but when 
I try to submit a document with embargo, I specified the date the embargo 
should be lifted long way on the future, my document can still be 
downloaded freely right after my submission complete (which means the 
embargo does not work). When I see the column in which I mention embargo 
until specific date, it seems the date format is not accepted. Is that 
really the cause? How can I solve this problem?

Best regards,

Herminarto Nugroho

-- 
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] No Thumbnail for Items without files in Mirage 2. (Dspace 6.3)

2019-02-28 Thread Kev Evans
Hi 

Is there a generic image I can use for Items without a file that can be 
used in Mirage 2. Similar to the 'mime' image in Mirage theme. I am using 
ImageMagick to generate thumbnails which is does for items with files.

Your kind advice please

Cheers

Kev

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