Project

General

Profile

Actions

Feature #17102

open

Feature #16335: Revisiting options and functions of Creative Commons license widget

Universal footer revisions for ToS / CC

Added by Colin McDonald over 1 year ago. Updated 2 months ago.

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

0%

Estimated time:
Deployment actions:

Flush sitewide_footer site transient


Description

As part of our Creative Commons licensing and display overhaul, we want to edit the universal footer that appears across all Commons pages (see attached for its current state).

The main issue is the four links that appear under the nav items: Help, Privacy, Terms of Service, Creative Commons (CC) license unless otherwise noted.

(Incidentally, we have another project we should resolve here to update the text at some of these links: https://commons.gc.cuny.edu/groups/cac-community-team-project-planning/forum/topic/summer-project-review-of-commons-tos-privacy-policy-and-mission-statement-2/)

I'm proposing we change the fourth link to say Creative Commons License Info, and then instead of linking to this general CC license page that we do now:

https://creativecommons.org/licenses/by-nc-sa/4.0/

Instead we link to a new page of documentation that explains a few of the CC points we've made in recent meetings:

- CC-licensed content on the Commons is also subject to our ToS, which allows us to truncate, show excerpts, repurpose, etc as per the needs of our design and the Commons overall
- The overall Commons content philosophy and distinction: You own your content on the Commons, different than on almost any other platform or social network. Explain what this means, how you can protect/export/etc.
- You can change the CC license of your Commons content at any time, on a space-by-space level.
- You can also choose no CC license at all, later or during space setup, and retain all rights with the exception of the ToS allowances mentioned above.
- A section on CC licensing and OER, which would be related to #17101

This version of the universal footer would only show up on our "core" Commons pages, like the homepage and directories -- we will need to spell out what this core contains.

A separate version would appear for this footer on individual Commons site and group pages, which will have their own licensing decisions and display. This version could just omit the fourth link to CC information, to reduce possible confusion there.


Files

universal-footer.png (31.7 KB) universal-footer.png Colin McDonald, 2022-10-25 11:49 AM

Related issues

Related to CUNY Academic Commons - Design/UX #16536: Main Navigation Drop-Down EliminationResolvedBoone Gorges2022-07-26

Actions
Actions #1

Updated by Boone Gorges over 1 year ago

A technical note, once this is ready for implementation. The sitewide footer is currently shared between all sites, including the main site. The markup is stored in a site transient, and if triggered from a non-root site, a switch_to_blog() takes place. See https://github.com/cuny-academic-commons/cac/blob/2.0.x/wp-content/themes/bp-nelo/footer.php, https://github.com/cuny-academic-commons/cac/blob/2.0.x/wp-content/mu-plugins/cac-sitewide-footer.php

If we are switching to a configuration where the main site shows one version of the footer, while all other sites show a different version (but the same as each other, so there's exactly 2 separate versions of the footer across the site), we'll have to modify this approach. The two different versions will have to be separately cached, and then retrieved separately.

Actions #2

Updated by Laurie Hurson over 1 year ago

An idea:

If we switch the site wide footer nav label to read "Creative Commons License Info" and link to a page on the main site (similar to About) called "Creative Commons License Info"
we could keep the sitewide footer the same network wide. On the CC info page we could outline how all main content on commons.gc.cuny.edu pages are CC license XYZ and all subdomains have their own licensing. If not noted on subdomains, the license on the sites is some rights restricted except for those indicated in the commons TOS

This allows us to keep 1 footer but achieve the goal of main CAC pages as CC and subdomains as they indicate.Then, we also dont ahve the change the processes Boone is referring to ( I think, if i understand correctly)

Thoughts?

Actions #3

Updated by Sara Cannon over 1 year ago

Laurie - I love the simplicity of that idea. I am wondering if legally the license needs to be displayed on the actual page. If it doesn't, this is a fabulous thought.

Actions #4

Updated by Colin McDonald over 1 year ago

I think this is a good idea too Laurie, thanks! We should go over it more on the call today, because I'm not sure either about the legal requirements.

It does seem like it would be more clear to have one CC documentation page with a full licensing breakdown (perhaps this should even be linked to from our main About page). And I definitely think it would be an easier technical lift.

Actions #5

Updated by Colin McDonald over 1 year ago

  • Target version set to 2.1.0
Actions #6

Updated by Boone Gorges over 1 year ago

+1 to Laurie's idea. If the team has agreed to move forward with this strategy, let me know and I can implement.

Actions #8

Updated by Boone Gorges over 1 year ago

  • Deployment actions updated (diff)

I've changed the link text in https://github.com/cuny-academic-commons/cac/commit/c4f4989a9dbcf0cea2ead2276052b8535181d3a8

Once we have a URL for the new help page, please provide it. Perhaps it could be created as a draft fairly soon?

Actions #9

Updated by scott voth over 1 year ago

Here is the URL for the new page: https://help.commons.gc.cuny.edu/content-licensing-on-the-commons/

It is is draft and has no content yet.

Actions #11

Updated by Boone Gorges about 1 year ago

The change to the global footer link has been reverted while other CC-related items are settled. https://redmine.gc.cuny.edu/issues/16536 See https://redmine.gc.cuny.edu/issues/16536#note-7

Actions #12

Updated by Boone Gorges about 1 year ago

Actions #13

Updated by Boone Gorges about 1 year ago

  • Target version changed from 2.1.0 to 2.2.0
Actions #14

Updated by Boone Gorges 5 months ago

  • Target version changed from 2.2.0 to 2.3.0
Actions #15

Updated by Boone Gorges 2 months ago

  • Target version changed from 2.3.0 to 2.4.0
Actions

Also available in: Atom PDF