Which Creative Commons licenses should Dataverse include by default?

[Philip Durbin]

The next release of Dataverse will ship with multiple license support.

As always, a new installation of Dataverse will show a CC0 option but we have an opportunity to present additional Creative Commons licenses in the dropdown. But which ones?

I feel like CC BY gets mentioned a lot so it seems natural to include it. But does it make sense to include CC BY-SA? What about CC BY-NC-ND? Do they all make sense for data? Does the dropdown get noisy if we include too many?

Here's the complete list of the six Creative Commons licenses we could include out of the box:

- CC BY

- CC BY-SA

- CC BY-NC

- CC BY-NC-SA

- CC BY-ND

- CC BY-NC-ND

If you were designing Dataverse, which would you include in the license dropdown for a new installation?

You're welcome to reply here or comment at https://github.com/IQSS/dataverse/issues/8347

Please note that no matter what licenses are installed by default, a sysadmin can later remove undesired licenses from the installation. In addition, the licenses above or custom licenses can be added at any time. The focus here is the experience of someone installing Dataverse for the first time.

Thanks for your input!

Phil

p.s. The list of licenses above is ordered by most permissive to least permissive according to https://creativecommons.org/about/cclicenses/

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Kris Dekeyser]

Hi Philip,

Currently, at the KU Leuven we use templates for licences, but we would like to use the multiple license support as soon as possible. We now offer the following options:

3-Clause BSD License (BSD 3 Clause)
Academic Free License 3.0 (AFL 3.0)
Affero General Public License v3.0 or later (AGPL 3.0-or-later)
Apache License 2.0 (Apache 2.0)
Attribution 4.0 International (CC BY 4.0)
Attribution License (ODC By)
Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0)
Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)
Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0)
Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
Common Development and Distribution License 1.0 (CDDL 1.0)
Copyleft 0.3.1 (copyleft-next-0.3.1)
Do What The F*ck You Want To Public License (WTFPL)
Eclipse Publice License 2.0 (EPL 2.0)
Educational Community License 2.0 (ECL 2.0)
European Union Public License 1.2 (EUPL 1.2)
Free Documentation License v1.3 (GFDL 1.3)
General Public License v3.0 or later (GPL 3.0+)
Lesser General Public License v3.0 or later (LGPL 3.0+)
MIT License (MIT)
Mozilla Public License 2.0 (MPL 2.0)
Open Database License (ODbL)
Permissive 2.0 (CDLA Permissive 2.0)
Public Domain Dedication and License (PDDL)
Public Domain Mark 1.0 (Public Domain)
Sharing 1.0 (CDLA Sharing 1.0)
Zero-Clause BSD (0BSD)

Take Your Pick! ;)

Kris

[Jacek Chudzik]

Dear Philip,

multiple licence support is something we are waiting for.

When the new release can be expected?

Regards,

Jacek

[Kris Dekeyser]

Jacek,

From what I can tell from Github, it is ready for release in 5.10 which is currently being wrapped up: 5.10 milestone status. In the Community Call 5.10 was announced as 'imminent'. i.o.w. soon ;)

Cheers,

Kris

[Philip Durbin]

Yep, that's right. The only thing I'll add is that https://github.com/IQSS/dataverse/milestones/5.10 is a slightly better link because it also includes open, unmerged pull requests (instead of just issues) that we'd like to include in 5.10.

So yeah, I'd say soon. We can't promise a date. Sorry. Glad you're excited!

Thanks,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0b202447-3cac-4a4e-8fa4-068b2ab10916n%40googlegroups.com.

[Eunice Soh]

Hi Phil, 

we're in the midst of discussing this as well.. I think having CC0 and CC BY licenses out of the box could be good. We've had GPLv3, which is a software license, used as well in our instance.

License name: GPLv3

License URL: https://www.gnu.org/licenses/gpl-3.0.en.html

Short description: The GNU General Public License v3.0

Icon URL: https://www.gnu.org/graphics/gplv3-88x31.png

The ones most used (ranked as so):

-CC BY-NC 4.0 (DEFAULT; vast majority of datasets)

-CC BY 4.0 (<50 datasets but >10 datasets)

-CC BY-SA 4.0 (<10 datasets)

-CC BY-NC-SA 4.0 (<10 datasets)

-CC0 1.0 (<10 datasets)

-GPLv3 (<10 datasets)

There were also uses of:

MIT: https://opensource.org/licenses/MIT

BSD-3-Clause: https://opensource.org/licenses/BSD-3-Clause

But these two licenses appear to have some text that needs to be customised, and also may thus need to be added as a license.md/license.txt as well. For example, the MIT license requires year and copyright holder to be filled in: Copyright <YEAR> <COPYRIGHT HOLDER>.  

Not using the license from the dropdown, but the custom 'terms of use' results in the metadata exports showing "termsofuse" rather than "license". Only the latter of which is picked up by Google Dataset Search (see screenshot below).

Kind regards,

Eunice