Hi,
We still have failure with CC, too (DSpace Version 6.2).
At the momentan, the CC API at https://api.creativecommons.org/rest/1.5
<https://api.creativecommons.org/rest/1.5> is not available (503 error).
Kind regards,
Marion
-----------------------------------
Marion Rupp
Bibliotheks-IT
Universitäts- und Landesbibliothek Bonn
Postfach 2460, D-53014 Bonn
Tel. 0228 / 73 75 50 Fax: 0228 / 73 75 46
eMail: [email protected]
Internet: http://www.ulb.uni-bonn.de
Twitter: http://twitter.com/ulbbonn
Facebook: http://facebook.com/ulbbonn
Am 03.04.2018 um 02:49 schrieb George Kozak:
Hi, Everyone:
I made the suggested change from http to https, but I still have
failure in connecting to Creative Commons. I restarted tomcat and
cleared the cocoon cache, as well.
George Kozak
Cornell University
On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara <[email protected]
<mailto:[email protected]>> wrote:
Thank you for the update Rob.
Any redirection is being applied from non-SSL to SSL? Was the same
before the update?
I changed my settings (dspace.cfg) to use SSL:
# The url to the web service API
cc.api.rooturl = https://api.creativecommons.org/rest/1.5
<https://api.creativecommons.org/rest/1.5>
And it works now :)
- Javier.
El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers escribió:
Heya everyone, Rob from Creative Commons here.
I'm very sorry that our API isn't working with DSpace at the
moment. I upgraded the server that the API runs on, and the
problem that you are seeing wasn't caught by my tests.
If I call the API simply via the command line, e.g.:
curl -d
"answers=<answers><locale>en</locale><license-standard><commercial>y</commercial><derivatives>sa</derivatives><jurisdiction></jurisdiction></license-standard><work-info><title>Untitled</title><creator>A.
N. Other</creator><work-url>https://example.com/untitled
<https://example.com/untitled></work-url></work-info></answers>"
https://api.creativecommons.org/rest/1.5/license/standard/issue
<https://api.creativecommons.org/rest/1.5/license/standard/issue>
Then I do get back an xml block, e.g.:
<?xml version='1.0' encoding='utf-8'?>
<result>
<license-uri>http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/></license-uri>
<license-name>Attribution-ShareAlike 4.0
International</license-name>
<deprecated>false</deprecated>
<rdf>
<rdf:RDF xmlns="http://creativecommons.org/ns#
<http://creativecommons.org/ns#>"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns#>">
<Work xmlns:dc="http://purl.org/dc/elements/1.1/
<http://purl.org/dc/elements/1.1/>"
rdf:about="https://example.com/untitled
<https://example.com/untitled>"><dc:title>Untitled</dc:title><dc:creator>A.
N. Other</dc:creator><license
rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/>"/></Work><License
rdf:about="http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/>">
<permits
rdf:resource="http://creativecommons.org/ns#DerivativeWorks
<http://creativecommons.org/ns#DerivativeWorks>"/>
<permits
rdf:resource="http://creativecommons.org/ns#Distribution
<http://creativecommons.org/ns#Distribution>"/>
<permits
rdf:resource="http://creativecommons.org/ns#Reproduction
<http://creativecommons.org/ns#Reproduction>"/>
<requires
rdf:resource="http://creativecommons.org/ns#Attribution
<http://creativecommons.org/ns#Attribution>"/>
<requires
rdf:resource="http://creativecommons.org/ns#Notice
<http://creativecommons.org/ns#Notice>"/>
<requires
rdf:resource="http://creativecommons.org/ns#ShareAlike
<http://creativecommons.org/ns#ShareAlike>"/>
</License>
</rdf:RDF>
</rdf>
<licenserdf>
<rdf:RDF xmlns="http://creativecommons.org/ns#
<http://creativecommons.org/ns#>"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns#>">
<License
rdf:about="http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/>">
<permits
rdf:resource="http://creativecommons.org/ns#DerivativeWorks
<http://creativecommons.org/ns#DerivativeWorks>"/>
<permits
rdf:resource="http://creativecommons.org/ns#Distribution
<http://creativecommons.org/ns#Distribution>"/>
<permits
rdf:resource="http://creativecommons.org/ns#Reproduction
<http://creativecommons.org/ns#Reproduction>"/>
<requires
rdf:resource="http://creativecommons.org/ns#Attribution
<http://creativecommons.org/ns#Attribution>"/>
<requires
rdf:resource="http://creativecommons.org/ns#Notice
<http://creativecommons.org/ns#Notice>"/>
<requires
rdf:resource="http://creativecommons.org/ns#ShareAlike
<http://creativecommons.org/ns#ShareAlike>"/>
</License>
</rdf:RDF>
</licenserdf>
<html><a rel="license"
href="http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/>"><img
alt="Creative Commons License" style="border-width:0"
src="http://i.creativecommons.org/l/by-sa/4.0/88x31.png
<http://i.creativecommons.org/l/by-sa/4.0/88x31.png>"/></a><br/><span
xmlns:dct="http://purl.org/dc/terms/
<http://purl.org/dc/terms/>"
property="dct:title">Untitled</span> by <a
xmlns:cc="http://creativecommons.org/ns#
<http://creativecommons.org/ns#>"
href="https://example.com/untitled
<https://example.com/untitled>" property="cc:attributionName"
rel="cc:attributionURL">A. N. Other</a> is licensed under a <a
rel="license"
href="http://creativecommons.org/licenses/by-sa/4.0/
<http://creativecommons.org/licenses/by-sa/4.0/>">Creative
Commons Attribution-ShareAlike 4.0 International
License</a>.</html>
</result>
Which does validate OK locally.
The only thing that should have changed for users of the API
is the SSL certificate for the domain (might the old one be
being cached somewhere?), although the versions of Python and
Apache Web server that the software runs of have jumped a few
versions, so it is possible that something else has changed
without me catching it.
I'd be very grateful if anyone could pass me any further
information, particularly if anyone can see what
api.creativecommons.org <http://api.creativecommons.org>
thinks it is sending back to DSpace in response to a license
request.
Thank you, and again my apologies for this.
- Rob Myers,
Core Systems Manager,
Creative Commons.
On Monday, April 2, 2018 at 3:38:07 PM UTC-7, Javier Távara
wrote:
I saw the tweets. Thank you.
As we don't have any useful logs of what's happening, I
thought disabling/enabling the step could fire any sort of
cache clearing.
No success.
- Javier
El lunes, 2 de abril de 2018, 17:33:16 (UTC-5), Keith
Gilbertson escribió:
On Monday, April 2, 2018 at 6:18:47 PM UTC-4, Javier
Távara wrote:
I really don't want to disable the CC License step.
That's understandable. Our repository team has been
encouraging people to select CC licenses.
Rob Myers at Creative Commons is aware that some
DSpace repositories have had an issue, but it's now
past normal working hours, and I haven't been able to
provide him with any useful information as to what's
specifically causing the problem.
Disabling/enabling fixes nothing by the way.
I had to comment out the CC License step in multiple
locations in the item-submission.xml file on our test
server, and then restart Tomcat. I think you are
offering additional information that the CC License
step still doesn't work once you enable it again.
- Javier.
El lunes, 2 de abril de 2018, 16:43:29 (UTC-5),
Keith Gilbertson escribió:
George, we've had similar problems today.
We'll probably disable CC License steps for
now, and then restart Tomcat. On our system,
this is configured in
/dspace/conf/item-submission.xml
--keith
On Monday, April 2, 2018 at 5:31:29 PM UTC-4,
George Kozak wrote:
Hi,
We have a DSpace 5.5 and a DSpace 6.2
install. This afternoon, the CC License
submission step stopped working and caused
an internal error. I don't use Twitter,
but one of my co-workers who does saw
Creative Commons tweeted that their API
was broken, but an hour later said it was
back up. However, our DSpace installs are
still failing at the CC License step. I
tried rebooting my tomcat, but that didn't
help. Any suggestions?
--
***************************
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924 <tel:%28607%29%20255-8924>
[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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech
<https://groups.google.com/group/dspace-tech>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
***************************
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
[email protected] <mailto:[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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[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 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.
