Project

General

Profile

Actions

Feature #16335

open

Revisiting options and functions of Creative Commons license widget

Added by Laurie Hurson 3 months ago. Updated 30 days ago.

Status:
Reporter Feedback
Priority name:
Normal
Assignee:
-
Category name:
-
Target version:
Start date:
2022-07-06
Due date:
% Done:

0%

Estimated time:

Description

Hi All,

The release of the OER tag and the Open Education institute I ran in June has highlighted some issues with the Creative Commons license widget we are running on the commons, particularly on sites.

By default, every page of every site site is tagged with a CC license. I think we should revisit that. People may want some of their content openly licensed but not all of it. For example, Raffi Khatchadourian wrote to the Zendesk asking how to list some of his pages on his main site as oer but not all of the pages. Currently this is not really possible - the CC license is only available on a page by page basis or it encompasses the whole site. I am proposing we allow CC for some pages and no clear open license on other pages (hence signifying they are not open).

I think the automatic, by default tagging of every page as CC, regardless of whether a user has chosen the CC license knowingly, is an issue.

This also raises questions about creating an option to allows folks to restrict some of their work. Maybe we don't want to provide a "closed" option but this could also occur through simply not applying a CC license by default to every page and allowing a user to knowingly assign the CC license to only "open" content.

I think all of these issues, ideas, and options warrant a discussion, which hopefully we can pick up in the fall.


Files

2022-07-07_144335.png (12.6 KB) 2022-07-07_144335.png Raymond Hoh, 2022-07-07 05:50 PM
Actions #1

Updated by Laurie Hurson 3 months ago

  • Subject changed from Revisi options and functions of Creative Commons license widget to Revisiting options and functions of Creative Commons license widget
Actions #2

Updated by Boone Gorges 3 months ago

  • Status changed from New to Reporter Feedback
  • Target version set to 2.1.0

Thanks for this, Laurie. I think there are technical and design considerations about how different layers of license work together (fallback vs page-specific settings, etc), and I've added Ray and Sara as watchers.

But before jumping into this, I think there should be a broader discussion about what we want to accomplish, and how these licenses are designed to work in a context with more than one level of granularity. Maybe we should bring a librarian into the discussion so that we can sketch out best practices?

Actions #3

Updated by Raymond Hoh 3 months ago

Thanks for accumulating these issues, Laurie.

I think the automatic, by default tagging of every page as CC, regardless of whether a user has chosen the CC license knowingly, is an issue.

I can see how it would be better to not use the default site license for each post or page. Instead, we can introduce a default "Inherit" option on posts and pages, which would make it more clear that the post license is using whatever the site license is. See attached mockup.

If "Inherit" is also an issue because we do not want the site to even have a sitewide license, then a "Not set" option would be better. Maybe the "Inherit" label is used if the site has set a site license and the "Not set" label is used when the site has not set a site license under the "Settings > Writing" admin dashboard page or during site creation.

Also, it's worth noting that it currently isn't possible to have the site license set to nothing, so some work would need to be done there.

Actions #4

Updated by Laurie Hurson 3 months ago

Thank you both for feedback on this.

Also, it's worth noting that it currently isn't possible to have the site license set to nothing, so some work would need to be done there.

Yes, and this is what prompted the ticket in the first place. I think now that we are beginning to see sites tagged as OER, we should offer more control and granularity in how the CC licenses are applied on sites. The original use case for this is Raffi's site - on which he has created an OER but does not want to license the whole site as open.

If "Inherit" is also an issue because we do not want the site to even have a sitewide license, then a "Not set" option would be better. Maybe the "Inherit" label is used if the site has set a site license and the "Not set" label is used when the site has not set a site license under the "Settings > Writing" admin dashboard page or during site creation.

I think an both an "inherit" option and "not set" option would be helpful but also somehow adding the a way to have a page with no license at all (perhaps accomplished through the not set option).

All of this is to say that yes, I agree with Boone that we likely need to have a longer discussion about how to refine the CC licensing in the Fall. I think getting librarians feedback would be helpful too. But first we may want to have a team convo to outline our goals for how the CC features will function on the commons.

Actions #5

Updated by Laurie Hurson 30 days ago

Hi Sara & All,

Following up on this after the dev call on Tuesday.

I am sending along a few examples of how creative Commons Licenses display on Commons sites. Please correct me if any of explanations are incorrect or confusing.

By default, a CC license is displayed on every page/post on every site. If the admin uses the CC widget to put a license in the sidebar or footer, this becomes the site-wise license and then the CC is not displayed on every page/post.

Examples of pages with CC licenses

1.  https://khatchad.commons.gc.cuny.edu/

This site is actually one of the sites that re-started this conversation about the CCLicense. This prof has an oer on his site (linked in next bullet) but does not want the whole site to be open (i.e. putting the license in footer. So now, by default because not in footer every page has a CC license after the content body. Not ideal. We also dont have a way for authors to have a more restrictive license for use on content like their own writing or resume.

https://khatchad.commons.gc.cuny.edu/teaching/csci-40500-77100-software-engineering-sp-21/2.

2. https://iletc.commons.gc.cuny.edu/

Another example where it would make sense for some pages to have CC while others do not or are restricted from re-use. This is a center's site with center and event information but also a ton of open resources ("Materials" in menu). You will see that every page has the CC after the content that reads "This entry...." meaning that single page has xyz license type.

Examples of CC License in Footer

1. https://tlc.commons.gc.cuny.edu/

2. https://psy327f22.commons.gc.cuny.edu/
On this site the CC is in the footer areas, even though it does look like it is in the page. You'll notice though that in posts, there is no "this entry..." language after the content because the CC license defaults to the footer widget.

When revisiting this functionality, we might consider three issues:

1. More signalling and education around how all Commons content will be CC or better yet (IMO)  revisiting this option and NOT assigning CC  immediately, but instead allowing users to select into applying CC to their site.

2. On sites where only some of the content is open, Admins should have a way to create pages that do not have to be under the CC license. For example, writing samples, CVs, and students' work (if they don't want to openly license it). This could mean turning the CC "off" or hiding it for the page.

3. Relatedly, users should have access to more restrictive licenses or tagging options. This resolves #2 and also provides a way to communicate that this  content is not open.

Actions

Also available in: Atom PDF