-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataset: Show on Create Page CC0 default #1990
Comments
Something else to think about as well:
|
If we do this when a user hits publish, as mocked up: https://iqssharvard.mybalsamiq.com/projects/termsofuse-dataverse40/1C%20Terms%20of%20Use%20and%20Licensing then that should fix the problem. |
👍 |
I agree that we should make it clear to users which license or waiver has been selected by default. Check out this tweet at https://twitter.com/ruebot/status/938861697766477827 (emphasis mine):
|
In a design meeting today with @TaniaSchlatter @dlmurphy @djbrooke @scolapasta @mheppler @jggautier and myself we agreed to leave a comment on this issue to indicate that showing which license/waiver is used by default is under consideration for Dataverse 5. The doc we discussed was "CC0 visibility design doc" at https://docs.google.com/document/d/10lQeIbfqgFd8JOBXYznxv2AMHFXxhSlYxyEaOoe00G0/edit?usp=sharing #1753 is related. |
Would it be possible to open the document? |
@MrK191 sorry, I don't have access to open the doc. I would if I could!
We have this now. On publish, the license is shown. Here's a screenshot from 5.11.1: Is that enough to close this issue? I think so. Dear reader, what do YOU think? |
I just made the Google Doc publicly viewable again. It used to be public but it became restricted somehow. I agree with @pdurbin. More recent versions of the Dataverse software have changes designed to make "it clearer to users which license or waiver has been selected by default". |
Add into the create dataset page a section showing CC0 will be selected.
The text was updated successfully, but these errors were encountered: