-
Notifications
You must be signed in to change notification settings - Fork 531
IQSS/10883-License Enhancements #11232
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
IQSS/10883-License Enhancements #11232
Conversation
|
No issues found with this PR. Merging |
|
@ofahimIQSS @qqmyers @jeromeroucou now that this PR has been merged does the JSON French license in this PR need to be revisited? Would it still work? |
|
Things should be null safe, so the new fields aren't needed. |
I agree with @qqmyers But if you are OK, I will push an update with new fields as soon as I have confirmation of which |
|
@jeromeroucou sure, sounds good. Please do create a PR when you're ready. |
What this PR does / why we need it: Multiple license changes per #10883, affecting attributes that can be uploaded for new licenses and what is sent to DataCite.
Which issue(s) this PR closes:
Special notes for your reviewer: This should cover all the points listed in the issue, plus the optional add of a language parameter.
Suggestions on how to test this: ~Regression testing - licenses should work as before on a new db as well as after an update of an existing db. The new feature is primarily in what gets sent to DataCite, so creating a dataset, selecting a license, publishing, and then verifying that the DataCite export has the new rights attributes and xml:lang entry as shown in the issue should do it.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?: included.
Additional documentation: