I'm using the 5.6 version, and nothing change.
2018-05-14 15:02 GMT-03:00 Javier Távara <[email protected]>: > Jira says it has been fixed for 5.6 and 6.0. You can try updating. > > > El lunes, 14 de mayo de 2018, 7:43:25 (UTC-5), [email protected] escribió: >> >> Any news for this? I'm having the same problem. >> >> Em sexta-feira, 26 de agosto de 2016 05:53:53 UTC-3, Oliver Goldschmidt >> escreveu: >>> >>> Hi, >>> >>> thank you for your reply. Unfortunately this solution does not work for >>> me. Adding the trailing slah or not - it does not make a difference at all, >>> for neither of the two issues. >>> >>> Thanks for the suggestion, though! >>> >>> Best >>> Oliver >>> >>> Am Donnerstag, 25. August 2016 16:35:23 UTC+2 schrieb Guillermo Esteban >>> Murillo Goussen: >>>> >>>> Hi, I had the same issue like two months ago. The solution was "add >>>> the trailing slash at the cc.api.rooturl value. I read at their >>>> documentation, they chaged it, and it worked. >>>> >>>> # The url to the web service API >>>> cc.api.rooturl = http://api.creativecommons.org/rest/1.5*/* >>>> >>>> 2016-08-25 8:14 GMT-06:00 Oliver Goldschmidt <[email protected]>: >>>> >>>>> Hi DSpace community, >>>>> >>>>> I'm having trouble with the CC-Liceses again. Two things are a little >>>>> bit strange: >>>>> >>>>> * the local files license_rdf and license_text are empty >>>>> This is already described in https://jira.duraspace.org/browse/DS-2604, >>>>> but obviously it is not solved yet. As I have noted in a comment there, I >>>>> have found a strange error in my dspace.log: >>>>> ERROR org.dspace.license.CreativeCommons @ Server returned HTTP >>>>> response code: 403 for URL: http://creativecommons.org/lic >>>>> enses/by/3.0/de/ >>>>> I don't understand that, because getting the url with wget is not a >>>>> problem at all - even not from my DSpace server! >>>>> >>>>> * the license doesn't get it into the metadata >>>>> This is already described in https://jira.duraspace.org/browse/DS-1538, >>>>> but also obviously not solved yet. dc.rights and dc.rights.uri are not >>>>> getting set at all (I have also seen the error message described in >>>>> DS-1538, but the more common behaviour is, that the field is not getting >>>>> set). >>>>> >>>>> Any ideas how to fix this? We are using DSpace 5.4 with JSPUI (and are >>>>> about to switch to 5.6) >>>>> >>>>> Thanks in advance for any hints, >>>>> best >>>>> Oliver >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- > You received this message because you are subscribed to a topic in the > Google Groups "DSpace Technical Support" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/dspace-tech/StUrVb0GHUM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Júlia Carneiro de Almeida Graduada em Bacharelado em Sistemas de Informação - CIn/UFPE Mestranda em Ciência da Computação - CIn/UFPE [email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
