-
Notifications
You must be signed in to change notification settings - Fork 493
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
8112 5.7 release notes #8128
8112 5.7 release notes #8128
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few comments but overall this is looking good.
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
- Users retrieving large guestbooks over the API will experience fewer failures (Issue #8073, PR #8084) | ||
- Users will now be able to set a language for metadata entry for datasets (Issue #7388, PR #7958) | ||
- Administrators will now be able to set a language for metadata exports at the document or element level (Issue #7388, PR #7958) | ||
- Administrators will now be able to specify the language of controlled vocabulary items (Issue #6751, PR #7959) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"DDI metadata exports will include values for controlled vocabulary items using the metadata language defined for the dataset and will include a second value in the Dataverse instance's default language (if different)."?
I.e. - if the Dataverse is set up to display French and a given Dataset defines English as the metadata lang, the controlled vocab entries in the DDI export will include a French lang element and an English one. If the Dataset uses French for the metadata language, there would only be one entry in this case (since the Dataverse instances uses French).
I
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What this PR does / why we need it:
5.7 is upon us.
Which issue(s) this PR closes:
Closes #8112
Special notes for your reviewer:
Suggestions on how to test this:
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?:
Additional documentation: