-
Notifications
You must be signed in to change notification settings - Fork 12
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
Require license selection at dandiset creation time #778
Comments
This seems to be done already. |
i'm not sure this is done already. clicking on new dandiset does not ask for a license. perhaps one thing that could be done is the new dandiset uses a version of the meditor but has a description saying what is required. the minimum validation requirements for a dandiset are quite limited and perhaps that's a way to also reduce spam. |
Ah, you want the license selection to be required at the time of creation of the dandiset. Is it not sufficient to make the license field required? Then the creator can defer the selection to later. What's the reason for forcing the selection at creation time? (Perhaps a separate topic but--for that matter, what's the value in forcing a description at that time as well?) |
i think just enough of a hill to climb to make people think about things. |
One of the reasons could be: we are distributing draft versions of datasets. Before publish we otherwise wouldn't have a chance to enforce having a license for distributed draft version of the dandiset. Mandating having license specified at creation time resolves that. |
related issue: dandi/dandi-schema#115 in which I argue against license selection for embargoed dandisets, and have that selection at Unemabrgo point. |
This was completed in #839. |
a license is a required element of every dandiset. can we add license selection when someone creates a dandiset (at present we are only allowing cc0 and ccby. the license types should be pulled in from dandi schema.
The text was updated successfully, but these errors were encountered: