Yeah,
We've just noticed the reversal, or fix.
Pretty / site refresh: http://creativecommons.org/choose
Partner Interface: http://creativecommons.org/choose/?partner=dspace
http://wiki.creativecommons.org/Partner_Interface
I had finished cherry-picking, and updating a patch to our system (to use
DSpace 1.8 Web Services API), and had deployed it to our staging
environment to give our admins, managers, and submitters a chance to give
us feedback, and by late afternoon yesterday, the original method (still
residing on production) appeared to be back working.
Disconcerting indeed.
I've just emailed the folks at Creative Commons, to see if this was just an
oops during their site refresh, or if we should instead definitely update
our system to use the web service. They've just responded:
> Thanks for the message, and sorry about that downtime on the Partner
> Interface. The downtime was definitely unintentional. There are no
> current plans to retire the Partner Interface, so you should be safe
> to continue using it.
Personally, I'm not entirely sure what our next step is locally. We could
use either the API or the partner/legacy method. Also, I've got to look
into the difference between what a creative-commons license object looked
like in 1.7 and older, vs how the API version of creative commons stuffs it
in there. i.e. storing the metadata in dc.rights in the newer one. And some
catch-up we might have to do to upgrade old items to look like the new ones.
Peter Dietz
On Wed, Jul 25, 2012 at 9:27 AM, Robin Taylor <[email protected]> wrote:
> Hi Peter,
>
> Having encountered the same problem but with the JSPUI I went to create a
> fix today and found the CC site seems to have reverted to the old format.
> Nothing new has been reported on the Twitter feed. So the immediate problem
> has disappeared but its a bit disconcerting.
>
> Cheers, Robin.
>
>
>
> On 23/07/12 22:56, Peter Dietz wrote:
>
> Hi All,
>
> Its just been reported to me that the Creative Commons site has changed
> its format, so if you are using an older version of DSpace (such as 1.7 and
> earlier) and have submissions with a creative commons license, then your
> submission will be stuck, due to the dependency on the Creative Commons
> site.
>
> The current version of DSpace (1.8) works fine as that version was
> re-tooled to use the Creative Commons web services API.
>
> According to the @creativecommons Twitter feed, I've noticed their
> recent posting.
> New interactive Creative Commons license chooser is now live!http://
> creativecommons.org/choose/ <http://t.co/NhADOfW2>
>
> I'm going to look into back-porting the change to use CC Webservices API
> for 1.7 (XMLUI), and posting a patch.
>
> Peter Dietz
>
>
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
