Present license info when chosen license is All Rights Reserved
| Project: | Creative Commons |
| Version: | 6.x-1.0-beta2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | turadg |
| Status: | active |
Jump to:
My site license is CC Attribution, but some of the content on the site comes from others who have chosen to license by All Rights Reserved with some qualifications.
The CC block currently doesn't display when the ARR is the 'license'. That's because the CC class codes ARR as no license (license URI is blank and thus has_license() returns false). On my site, this would lead people to assume that the content node is under the general site license, which would be bad.
I see the logic in ARR not being consider a "license", but it is part of the usage terms, which are arguably what this module is designed to communicate. Right now it only supports CC license terms, but it would be easy to add new ones. This module is targeted at CC, but a lot of its code would work for selecting any license.
What do people think of these propositions?
1) Allow specifying non-CC licenses that aren't All Rights Reserved. These could be encoded as URIs and the module could read the URL for the terms of the license.
2) Factor out the general license code into a new 'license' module and give it the above functionality. The CC-specific stuff would stay in this module and use hooks provided by License.
#1
In the meantime, I've added output for when the license is "None (All Rights Reserved)".
t('This @dc:type-name, @dc:title, by @cc:attributionName is made available under the fair use doctrine. All rights reserved.', $args);
#2
I think it'd make sense to support non-CC licenses that use CC technology (e.g. licenses which implement ccREL, since it is made to be used for non-CC licenses too), by allowing a user to be able to configure his/her own "custom" license that uses the same code to display or for search purposes, etc.
If we're talking about licenses that depart from the CC toolkit though, I think factoring code out into a generic 'license' module may make more sense.
As for the output on All Rights Reserved, that makes sense to display something (I didn't consider the Site License case). I'm going to adjust the text slightly though, to make it a little more jurisdiction agnostic (e.g. we don't have fair use in Canada).
#3
I have the same issue, but I am not sure how to add this new output for ARR content. Can you point me to the right place? Thanks.
#4
Maybe we can have a setting for what to display in the ARR case. I need the "fair use" clause but I see that it shouldn't be default. Or at least we could make it a themeable element.
#5
@ #4
Allowing configurable ARR text would be great, and it should be possible to have the old behaviour of displaying nothing when All Rights Reserved.
Making it a themeable (theme function or license.tpl.php) is one acceptable solution, but I'd like to see an admin UI setting to allow the text to be specified. (For all licenses, not just ARR). Perhaps built out of tokens, like date formats (or even integrate with token module). This would put the configuration in the reach of non-themers.
Also, I suggest that the default is to display nothing. When upgrading, the website should not suddenly start displaying more information.
I understand the use case presented, but the solution in #1 has led to my site displaying the ARR. This makes no sense for a site where the default, site-wide license is ARR. I've gone back to beta2 in the meantime.
Perhaps an option to only display the license block when the node-license differs from the site-wide license? This is assuming the site-wide license is enabled, of course.
As for the other propositions...
1) non-CC licenses would be very welcome. Free software licenses would be a good start, font licenses, academic licenses... You may have to change the name of the project, of course.
2) Yeah, if that's the best way to manage the code, do it. The Nodewords project has recently been reaaranged as a core nodewords module, and several add-on modules for different types of meta data.
Perhaps there could be a core license API, supported by modules like CC, custom license, F/OSS...
#6
Re: ARR text
Alright, for a short-term solution (unless there are any objections), I'm going to create a setting where an admin can configure text to be displayed for ARR content. The default will be blank.
In the future, we can look at different ways of making the license text configurable for all licenses, but it's a bit complicated because of the ccREL RDFa and optional metadata.
Re: node license display
I like this idea. May implement it an option soon -- don't display node license if site license enabled and node license is the same as the site license.
This also has me thinking about collapsing the node and site license blocks... but it seems confusing in a couple cases. You may have content types for which CC licensing isn't enabled, yet the site license would still apply. And there may be non-node content that a site license is meant to cover (e.g. the website design)... just a thought.
Re: Additional licenses
I like the idea of refactoring modules into a generic license module, and then a CC module that adds CC specific functionality (like ccREL, CC search, icons, etc.). But I'd rather get a stable CC module out the door first. Something to think about for the future though.