EPrints Technical Mailing List Archive

Message: #05168

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Antwort: Creative commons

Hi John,

we just recently created a phrases file that covers license images and the various versions.

We keep it simple and easy - just offer the versions in the dropdown menu, which itself is controlled by a namedset of the values. No complicated workflow steps.

Since we include the license image also in Coversheets (with LaTeX), we downloaded the image files instead of accessing them via creativecommons.org

Best regards,

Martin

--
Dr. Martin Brändle
Zentrale Informatik
Universität Zürich
Stampfenbachstr. 73
CH-8006 Zürich



Inactive hide details for John Salter ---25/11/2015 12:10:02---Hi, We need to be able to support historic as well as current CCJohn Salter ---25/11/2015 12:10:02---Hi, We need to be able to support historic as well as current CC license options in our repository.

Von: John Salter <J.Salter@leeds.ac.uk>
An: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Datum: 25/11/2015 12:10
Betreff: [EP-tech]  Creative commons
Gesendet von: eprints-tech-bounces@ecs.soton.ac.uk




Hi,
We need to be able to support historic as well as current CC license options in our repository.

I'm considering building a 'licenses' bazaar package that will:
- know about all historic and current licences
- store licenses as URIs*
- render the cc license logos in normal or compact variants
- allow which license versions to offer to be controlled by the workflow (e.g. options="v3,v4" would show all v3 and v4 licenses)
- ???

I'm not sure if this will require a custom EPrints::MetaField::License or just an EPrints::Plugin::InputForm::Component::Field::License.
Has anyone done any work around the CC licenses that might be useful?

Are there other aspects that would be useful to cover in this work?

Cheers,
John

*currently EPrints saves the licence as e.g. 'cc_by' or 'cc_by_4' - but 'cc_by'  could have meant v2, v2.5, or v3 at different points in time - therefore the exact licence applied is ambiguous.

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/