Re: [dspace-tech] Submission page got archived and not shown on the login page

2019-10-17 Thread Paul Münch
Good morning and welcome in the DSpace community,

could you please send the screenshot in a common image format? Or just
copy the plain error text.

Kind regards,

Paul Münch

Am 18.10.19 um 07:03 schrieb suman gupta:
> Good morning everyone!
>  I am new to DSpace. I have installed DSpace 6.0 on the Ubuntu server.
> Since the last weeks, I received this error in my DSpace repository
> while updating automatically on my server. I can't solve this error. I
> have pasted the screenshot below the error I face in my dspace. Any
> help would be appreciated.
> Thanks and Regards
> Suman Gupta
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to dspace-tech+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAP-ALMK0W6Jp%3DEDcH8ie1k-tRRiP5YUYHj-DgM3sxH-oS%3DDGng%40mail.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7bf1d1be-cbc0-f45b-63d6-8c746c2748e1%40staff.uni-marburg.de.


signature.asc
Description: OpenPGP digital signature


[dspace-tech] Re: Shibboleth attributes not working [SOLVED]

2019-10-17 Thread Gary Browne
Hi all,

When I looked more closely at the attribute map definition in 
attribute-map.xml:
http://schemas.xmlsoap.org/ws/2008/06/identity/claims/role; 
id="SHIB-SCOPED-AFFILIATION"/>

and the actual response received from SAML:
 http://schemas.microsoft.com/ws/2008/06/identity/claims/role;>

I realised that I had specified the wrong schema!

SOLVED!

Cheers,
Gary

On Thursday, October 17, 2019 at 9:50:22 PM UTC+11, Gary Browne wrote:
>
> Hi all,
>
>  
>
> DSpace 6.3, Tomcat 7, Amazon Linux 2
>
>  
>
> I have implemented Shibboleth authentication. It is working but now I need 
> to auto-allocate users to role-based groups. I have followed the 
> documentation on the duraspace wiki but I am not clear on how claim 
> attributes are specified so that they can be used by the 
> authentication-shibboleth.cfg configuration.
>
>  
>
> In /etc/shibboleth/attribute-map.xml I have added:
>
>  
>
> http://schemas.xmlsoap.org/ws/2008/06/identity/claims/role; 
> id="SHIB-SCOPED-AFFILIATION"/>
>
>  
>
> And then in authentication-shibboleth.cfg I have:
>
>  
>
> authentication-shibboleth.role-header = SHIB-SCOPED-AFFILIATION
>
>  
>
> # Whether to ignore the attribute's scope or value.
>
> authentication-shibboleth.role-header.ignore-scope = true
>
> authentication-shibboleth.role-header.ignore-value = false
>
>  
>
> # Default mappings of roles values to a comma separated list of DSpace 
> group
>
> # names (Case Sensitive).
>
> authentication-shibboleth.role.staff = staffRole
>
> authentication-shibboleth.role.student = studentRole
>
>  
>
> However when I login with my staff credentials via Shibboleth/SAML I get:
>
>  
>
> 2019-10-17 21:27:01,761 INFO  org.dspace.authenticate.ShibAuthentication @ 
> gary.bro...@sydney.edu.au has been authenticated via shibboleth.
>
> 2019-10-17 21:27:01,761 INFO  org.dspace.eperson.EPersonServiceImpl @ 
> gary.bro...@sydney.edu.au:session_id=:ip_addr=xxx:update_eperson:eperson_id=xxx
>
> 2019-10-17 21:27:01,761 INFO  
> org.dspace.app.xmlui.utils.AuthenticationUtil @ 
> gary.bro...@sydney.edu.au:session_id=:ip_addr=:login:type=explicit
>
> 2019-10-17 21:27:01,779 INFO  org.dspace.authenticate.ShibAuthentication @ 
> Added current EPerson to special groups: []
>
>  
>
> So you can see authentication is successful but adding to special groups 
> is not working (“[]”). I have confirmed that the SAML response contains the 
> data:
>
>  
>
>   http://schemas.microsoft.com/ws/2008/06/identity/claims/role;>
>
> staff
>
> 
>
>  
>
> Where am I going wrong??
>
>  
>
> Thanks,
> Gary
>
>  
>
>  
>
> Gary Browne | Technical Manager, Developments
> Online Services
> University of Sydney Library
> THE UNIVERSITY OF SYDNEY
> Level 1, Fisher Library F03, The University of Sydney NSW 2006
> T +61 2 9351 5946 | M +61 405 647 868
> E gary.bro...@sydney.edu.au 
> 
>
> The University of Sydney Camperdown campus stands on land of the Gadigal 
> peoples of the Eora nation.
>
>  
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/2fc8b20b-4c71-4c09-9508-18533c28c038%40googlegroups.com.


Re: [dspace-tech] Error OAI import -c -v

2019-10-17 Thread Michel Santana
I  have posted this reply to another question here. Perhaps is the same:
"We had a problem very similar and was because the OAI server has a bug in one 
library that causes a server crash when the dataset has an item with a non 
standard UNICODE character in the Metadata.
The solution is to change that library (xalan 1.7.1) to a previous one (xalan 
1.7.0) in the pom.xml file.
I have done a pull request to solve this.
https://github.com/4Science/DSpace/pull/101
Take a look and try. Good luck!"

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9e480ce6-3654-4375-939f-4f6816adf652%40googlegroups.com.


[dspace-tech] Limit on OAI harvested data?

2019-10-17 Thread Michel Santana
We had a problem very similar and was because the OAI server has a bug in one 
library that causes a server crash when the dataset has an item with a non 
standard UNICODE character in the Metadata.
The solution is to change that library (xalan 1.7.1) to a previous one (xalan 
1.7.0) in the pom.xml file.
I have done a pull request to solve this.
https://github.com/4Science/DSpace/pull/101

Take a look and try. Good luck! 

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/2bdd8320-15f1-468f-a56a-d4c97d135439%40googlegroups.com.


Re: [dspace-tech] Error OAI import -c -v

2019-10-17 Thread Ramón Cordeiro
Paul, The problem is dspace 5.2 does not export in numeric order, It's 
random. I've seen the item 9489, it's also ok. 


Em quinta-feira, 17 de outubro de 2019 07:49:01 UTC-3, muenchp escreveu:
>
> Hello,
>
> how is the next item with handle 2011/9489?
>
> We had also some UTF-8 coding issues. We exported all item metadata as 
> CSV-file and check for invalid characters, either manually or via script.
>
> I hope this helps and kind regards,
>
> Paul Münch
>
> Am 16.10.19 um 15:11 schrieb Ramón Cordeiro:
>
> Hello Everyone!
>
> I'm using Dspace 5.2. When I try to import the process begin, but in the 
> half of process show it: 
>
>
>
> *"*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *3800 items imported so far... Item with handle 2011/9488 indexed 
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: [was 
> class java.io.CharConversionException] Invalid UTF-8 character 0xfffe at 
> char #8143, byte #8191) 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:211) at 
> org.dspace.xoai.app.XOAI.indexAll(XOAI.java:198) at 
> org.dspace.xoai.app.XOAI.index(XOAI.java:131) at 
> org.dspace.xoai.app.XOAI.main(XOAI.java:405) at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
> at java.lang.reflect.Method.invoke(Method.java:498) at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226) 
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78) *
> *"*
>
> I've updated Charset of Operation System, but does not work. 
> I'm doing this update because the records was showed wrongs characters in 
> integrated database.
> Now, Items imported is showing correct characters, but the processo stop 
> after item 2011/9488. This item is Ok. I don't know what item is broken. Is 
> there how to discovery ?
> -- 
> 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 dspac...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/7e90ab53-dd88-49bf-b344-6c4ca65547cd%40googlegroups.com
>  
> 
> .
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/6122516c-f9b4-420c-a615-33bef86e40b1%40googlegroups.com.


[dspace-tech] Shibboleth attributes not working

2019-10-17 Thread Gary Browne
Hi all,

DSpace 6.3, Tomcat 7, Amazon Linux 2

I have implemented Shibboleth authentication. It is working but now I need to 
auto-allocate users to role-based groups. I have followed the documentation on 
the duraspace wiki but I am not clear on how claim attributes are specified so 
that they can be used by the authentication-shibboleth.cfg configuration.

In /etc/shibboleth/attribute-map.xml I have added:

http://schemas.xmlsoap.org/ws/2008/06/identity/claims/role; 
id="SHIB-SCOPED-AFFILIATION"/>

And then in authentication-shibboleth.cfg I have:

authentication-shibboleth.role-header = SHIB-SCOPED-AFFILIATION

# Whether to ignore the attribute's scope or value.
authentication-shibboleth.role-header.ignore-scope = true
authentication-shibboleth.role-header.ignore-value = false

# Default mappings of roles values to a comma separated list of DSpace group
# names (Case Sensitive).
authentication-shibboleth.role.staff = staffRole
authentication-shibboleth.role.student = studentRole

However when I login with my staff credentials via Shibboleth/SAML I get:

2019-10-17 21:27:01,761 INFO  org.dspace.authenticate.ShibAuthentication @ 
gary.bro...@sydney.edu.au has been authenticated via shibboleth.
2019-10-17 21:27:01,761 INFO  org.dspace.eperson.EPersonServiceImpl @ 
gary.bro...@sydney.edu.au:session_id=:ip_addr=xxx:update_eperson:eperson_id=xxx
2019-10-17 21:27:01,761 INFO  org.dspace.app.xmlui.utils.AuthenticationUtil @ 
gary.bro...@sydney.edu.au:session_id=:ip_addr=:login:type=explicit
2019-10-17 21:27:01,779 INFO  org.dspace.authenticate.ShibAuthentication @ 
Added current EPerson to special groups: []

So you can see authentication is successful but adding to special groups is not 
working (“[]”). I have confirmed that the SAML response contains the data:

  http://schemas.microsoft.com/ws/2008/06/identity/claims/role;>
staff


Where am I going wrong??

Thanks,
Gary


Gary Browne | Technical Manager, Developments
Online Services
University of Sydney Library
THE UNIVERSITY OF SYDNEY
Level 1, Fisher Library F03, The University of Sydney NSW 2006
T +61 2 9351 5946 | M +61 405 647 868
E 
gary.bro...@sydney.edu.au
The University of Sydney Camperdown campus stands on land of the Gadigal 
peoples of the Eora nation.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3B763FB0-A80C-4BFB-B733-55253DA031CF%40sydney.edu.au.


Re: [dspace-tech] Error OAI import -c -v

2019-10-17 Thread Paul Münch
Hello,

how is the next item with handle 2011/9489?

We had also some UTF-8 coding issues. We exported all item metadata as
CSV-file and check for invalid characters, either manually or via script.

I hope this helps and kind regards,

Paul Münch

Am 16.10.19 um 15:11 schrieb Ramón Cordeiro:
> Hello Everyone!
>
> I'm using Dspace 5.2. When I try to import the process begin, but in
> the half of process show it:
>
>
>
> *"*
> *3800 items imported so far...
> Item with handle 2011/9488 indexed
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
> [was class java.io.CharConversionException] Invalid UTF-8 character
> 0xfffe at char #8143, byte #8191)
>     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:211)
>     at org.dspace.xoai.app.XOAI.indexAll(XOAI.java:198)
>     at org.dspace.xoai.app.XOAI.index(XOAI.java:131)
>     at org.dspace.xoai.app.XOAI.main(XOAI.java:405)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
>     at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
> *
> *"*
>
> I've updated Charset of Operation System, but does not work.
> I'm doing this update because the records was showed wrongs characters
> in integrated database.
> Now, Items imported is showing correct characters, but the processo
> stop after item 2011/9488. This item is Ok. I don't know what item is
> broken. Is there how to discovery ?
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to dspace-tech+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/7e90ab53-dd88-49bf-b344-6c4ca65547cd%40googlegroups.com
> .

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/33c2e04a-a491-a298-8608-88903a584b6a%40staff.uni-marburg.de.


signature.asc
Description: OpenPGP digital signature


Re: [dspace-tech] Could not find or load main class dsrun

2019-10-17 Thread Fazio Riccardo
Dear Rakhi,

this should be run from dspace install dir:
[dspace-install]/bin/scopus-retrieve

check also if you can run this
[dspace-install]/bin/dspace

which is your OS ( linux or Windows)?

Regards
Riccardo

On Tue, 2019-10-15 at 11:12 +0500, Rakhi Batra - Assistant Manager
Publication wrote:
> 
> I am using Dspace-cris 5.10
> 
> 
> On Mon, Oct 14, 2019 at 10:38 AM Fazio Riccardo <
> riccardo.fa...@4science.it> wrote:
> > Dear Rakhi,
> > 
> > which version of DSpace-CRIS are your running?
> > can you share the command that you are using?
> > 
> > Riccardo
> > 
> > On Thu, 2019-10-10 at 22:57 -0700, Rakhi Batra - Assistant Manager
> > Publication wrote:
> > > Can anyone guide, why I am getting this error "Could not find or
> > load
> > > main class dsrun" when executing scopus-retrieve script? 
> > > Any input will be appreciated
> > > -- 
> > > All messages to this mailing list should adhere to the DuraSpace
> > Code
> > > of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> > > --- 
> > > You received this message because you are subscribed to the
> > Google
> > > Groups "DSpace Technical Support" group.
> > > To unsubscribe from this group and stop receiving emails from it,
> > > send an email to dspace-tech+unsubscr...@googlegroups.com.
> > > To view this discussion on the web visit 
> > > 
> > https://groups.google.com/d/msgid/dspace-tech/0b5224ca-1f16-4623-a292-5b107d0a6eaa%40googlegroups.com
> > > .
> > > 
> > -- 
> > -- 
> > Riccardo Fazio
> > DSpace and DSpace-CRIS developer
> > 
> > 4Science,  www.4science.it (an Itway Group Company)
> > 
> > office: UP Urban Places - Via Tiburtina, 652, 00159 Roma RM
> > tel: +39 3339341798
> > 
> > --
> > Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato
> > non infetto.
> > This message was scanned by Libra ESVA and is believed to be clean.
> > 
> 
> 
> -- 
> Regards,
> 
> Rakhi 
> 
> 
-- 
-- 
Riccardo Fazio
DSpace and DSpace-CRIS developer

4Science,  www.4science.it (an Itway Group Company)

office: UP Urban Places - Via Tiburtina, 652, 00159 Roma RM
tel: +39 3339341798

--
Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato non infetto.
This message was scanned by Libra ESVA and is believed to be clean.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/fb02a197c7ed08137795d637e9234a6046cb0498.camel%404science.it.