Project

General

Profile

Actions

Feature #16335

open

Revisiting options and functions of Creative Commons license widget

Added by Laurie Hurson over 1 year ago. Updated about 2 months ago.

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

0%

Estimated time:
(Total: 0.00 h)
Deployment actions:

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
post-license-edit.gif (80.3 KB) post-license-edit.gif Raymond Hoh, 2022-12-08 09:12 PM
settings-writing.gif (139 KB) settings-writing.gif Raymond Hoh, 2022-12-08 09:12 PM
site-create.gif (144 KB) site-create.gif Raymond Hoh, 2022-12-08 09:12 PM
Screen Shot 2023-01-19 at 12.07.23 PM.png (185 KB) Screen Shot 2023-01-19 at 12.07.23 PM.png Laurie Hurson, 2023-01-19 12:10 PM

Subtasks 2 (2 open0 closed)

Feature #17101: OER tag and CC licensing notification systemNewBoone Gorges2022-10-25

Actions
Feature #17102: Universal footer revisions for ToS / CCNewBoone Gorges2022-10-25

Actions
Actions #1

Updated by Laurie Hurson over 1 year 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 over 1 year 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 over 1 year 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 over 1 year 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 over 1 year 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 #6

Updated by Laurie Hurson over 1 year ago

Hi All,

Circling back to this.

I think it might be best if the default CC license is no CC license:

- No widget in sidebar or footer by default
- No CC license on pages/posts by default

If default is no CC:

- Users could select to put the widget in the footer or sidebar to indicate that all content on the site, unless otherwise noted, is CC licensed.
- User could select the CC license on just a single page or post (similar to how they do now) when editing the page or post.

Is this above plan possible? What issues does it raise if our new default is no CC license?

Some questions/thoughts:

- What happens to already created sites, pages, posts? I would suggest we leave everything as is and this default is for all new sites.

- (How) should the CC license interact with the OER tag? If possible, perhaps we can add a notification that is triggered if someone selects the OER tag but no CC licenses are present on the site. The user would be able to select the PER tag but the notification (appearing as a dashboard banner) might say something like, "we noticed that you have tagged your site as an OER but no CC license is present. Please CC license the open content, or the whole site in Settings>General. To learn more about open licensing visit our documentation [here/link].

Are there other considerations/issues that we should consider?

Actions #7

Updated by Colin McDonald over 1 year ago

I wanted to note on the main ticket here that I just started ticket #17101 as a subtask to address the OER tag and CC license notification system Laurie proposes above.

I also started #17102 to go over how the universal footer's CC information will need to change (or be omitted) to reduce conflicts/confusion as we change our default to no CC license at all and leave the choice to add this licensing to users either during creation or later on.

We discussed during our last meeting changing the creation flow License section to say something like:

"By default, you reserve all rights to your content, subject to the Commons Terms of Service [ToS link].

You can click below to add an open Creative Commons license to your work. You can also do this later in your settings.

Add license (button starts license walkthrough and adds sidebar)

(Click here [new documentation link, outlined in #17102] for more about open licensing and full ownership of your Commons content."

I also agree that we leave the licensing as-is on everything existing now, but we could link to this new CC documentation page in Settings>Writing where the license can be changed. I think we also need the ability to remove CC licensing entirely in that popup dialog, correct?

The new documentation page should also cover how to use different licensing on different pages or posts of a site, as Laurie mentions.

Actions #8

Updated by Laurie Hurson over 1 year ago

We discussed during our last meeting changing the creation flow License section to say something like:

"By default, you reserve all rights to your content, subject to the Commons Terms of Service [ToS link].

You can click below to add an open Creative Commons license to your work. You can also do this later in your settings.

Add license (button starts license walkthrough and adds sidebar)

(Click here [new documentation link, outlined in #17102] for more about open licensing and full ownership of your Commons content."

For the most part this sounds good to me. I would lean towards changing the language to be a bit more accessible, something like:

By default, you retain all rights to your content, subject to the Commons Terms of Service [ToS link]. This is different from other web platforms that retain all rights.
If you would like to openly license your content so that others can reuse and remix your content, can select Creative Commons license for your site below. You can also do this later in your settings. For more information about Creative Commons open licensing and your ownership of your content see here": [new CC documentation link, outlined in #17102] To read more about the Commons' committment to open education see here [link to oer section].

-- Add license (button starts license walk-through and adds sidebar)--

I also agree that we leave the licensing as-is on everything existing now, but we could link to this new CC documentation page in Settings>Writing where the license can be changed. I think we also need the ability to remove CC licensing entirely in that popup dialog, correct?

Yes current licenses will stay as is, perhaps we add a link to new documentation in dhasboard with CC selector. And yes we'll need some process and option to remove the CC that is akready applied.

The new documentation page should also cover how to use different licensing on different pages or posts of a site, as Laurie mentions.

There are several different documentation pages I need to write. I will comb through current ticket and start a new ticket that lists all these new pages that need to be created.

Actions #9

Updated by Colin McDonald over 1 year ago

Thanks for your help planning the documentation, Laurie. The changes to the language sound good to me. We'll just want to make sure it doesn't seem too daunting during the creation flow. Once we finish the copy review in #17090, I'll get all of the new text to Ray for #16960 and we can see how it's looking.

Actions #10

Updated by Raymond Hoh about 1 year ago

I've updated cdev with the copy that Laurie has written up. The other changes are as follows:

1. Site license now defaults to nothing

Previously, we used to set the Creative Commons by-nc-sa license as the default even if a license was not manually chosen. Now, on the site creation page, setting the license requires the user to make a decision if they want to use a license. This also follows into point 2.

2. "Reset" button next to Creative Commons license selector

Previously, you could not remove / reset the Creative Commons license entirely. Now, you can with the "Reset" button. If you do not have access to cdev, here are some GIFs:

Site creation: https://redmine.gc.cuny.edu/attachments/24165

Settings > Writing admin page: https://redmine.gc.cuny.edu/attachments/24164

Based on Laurie's copy, I've added some copy when a Creative Commons license is not selected for a site. Laurie or Colin, feel free to pass me some follow-up changes here. Also, let me know if "Reset" should be changed to something else like "Remove" instead.

3. "Inherit" is now the default license option when drafting a new post or page

https://redmine.gc.cuny.edu/attachments/24163

Similar to point 1, previously the post license when drafting a new post or page would be set to the site license by default. (Oftentimes, that would be by-nc-sa.) Now, the "Inherit" option replaces this. This basically means that no license will be saved into the post's metadata table and no license will be displayed at the end of the post. Let me know if we should change the "Inherit" label to something else.

Actions #11

Updated by Laurie Hurson about 1 year ago

Since we are still working on various aspects of this, we might considering pull the language updates ray made in the create flow and reverting to default CC license on all sites.

If we keep it in, we should change the "see here" copy for accessibility purposes. Edited below.

By default, you retain all rights to your content, subject to the Commons Terms of Service [https://commons.gc.cuny.edu/about/tos/]. This is different from other web platforms that retain all rights to content added to their platforms.

If you would like to openly license your content so that others can reuse and remix your content, can select Creative Commons license for your site below. You can also choose to openly license your content later by selecting a license in your Site/Group settings area.

For more information about Creative Commons and your ownership of your content see our Help page on "Creative Commons Licensing" [https://help.commons.gc.cuny.edu/creative-commons-licensing-on-sites/]

To read more about the Commons' commitment to open education see the Help page "OER on Commons Groups and Sites" [https://help.commons.gc.cuny.edu/using-oer/oer-tag-for-groups-sites].

Actions #12

Updated by Raymond Hoh about 1 year ago

Hi Laurie,

The Creative Commons changes on cdev are not going to make the next v2.1.0 release. What you see on cdev is just for testing purposes. With that being said, I've updated the License description on the "Create A Site" page to match your copy on cdev.

Actions #13

Updated by Laurie Hurson about 1 year ago

Thanks Ray. Apologies for my confusion.

Actions #14

Updated by Boone Gorges about 1 year ago

Ray, is there anything here that needs to be reverted or rolled back before the 2.1.0 release?

Actions #15

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.1.0 to 2.2.0
Actions #16

Updated by Raymond Hoh about 1 year ago

Ray, is there anything here that needs to be reverted or rolled back before the 2.1.0 release?

No, I didn't commit anything under 2.1.x branch; everything is self-contained for testing on cdev. Will commit at a later date when we've finalized what we want to do.

Actions #17

Updated by Boone Gorges about 1 year ago

Perfect, thanks!

Actions #18

Updated by Boone Gorges 5 months ago

  • Target version changed from 2.2.0 to 2.3.0
Actions #19

Updated by Boone Gorges about 2 months ago

  • Target version changed from 2.3.0 to 2.4.0
Actions

Also available in: Atom PDF