IQSS/8422 default to allow dataset level choice of metadatalanguage #8440
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
move asterix message to top of metadata table handle using template during dataset creation docs re: the change to default stype tweaks to add instructions and style the selection box the same as others, e.g. the template selection
qqmyers
added this to Review 🦁
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
via automation
landreev
approved these changes
Mar 7, 2022
IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
automation
moved this from Review 🦁
to QA 🔎✅
Mar 7, 2022
|
(I have approved the PR, but please take a look at the failed integration test. It looked like it was something outside the PR that killed ansible, but please double-check). |
…_allow_dataset_level_choice_of_metadatalanguage
IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
automation
moved this from QA 🔎✅
to Done 🚀
Mar 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: Per the issue, the recent enhancement to add a choice of metadata language restricted that choice to collections and, if no collection-level choice was made, the global default option (the machine locale/language) was chosen. This PR changes the default behavior such that, if the metadatalanguage isn't chosen in an ancestor collection, the user is allowed/forced (because there is no 'none' option) to chose a language at dataset creation. (This is only if the metadata language setting is configured in the first place.) Thus, this allows a use case where a collection/repository manager can let users decide which language to use and have collections that include datasets using different metadata languages.
Which issue(s) this PR closes:
Closes #8422
Special notes for your reviewer:
Suggestions on how to test this: Configure metadatalanguages, verify that the dataverse/edit/general entry for metadata language includes the new value 'Chosen at Dataset Creation' and that choosing that on the root or child dataverse triggers a change in the dataset creation page to allow a user to chose the metadata language (versus showing the predefined choice from the collection level) -see image below.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
The change in the dataset page, only if metadatalanguage is enabled and only in collections where a choice hasn't been made is for the metadata language to be a live input:
Is there a release notes update needed for this change?:
Additional documentation: Change in default behavior note in the config docs