Metadatalanguage fix #489
Open
Metadatalanguage fix #489
Conversation
This file contains hidden or 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
each Dataverse collection and ask the user to set one of them.
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Closes this issue: #478
Before exporting, RSpace makes an API call to Dataverse querying the possible metadata languages for each Dataverse collection. If there are metadata languages configured on the Dataverse server, the Dataverse export form has a new input field for choosing one.
I also worked on Dataverse itself, the Dataverse Java client and the Dataverse adaptor. This PR only works with the changes presented in the following PRs:
Design decisions
Configuring available metadata languages on the integration form and keeping track of the possible changes would put too much administrative burden on the user., so I decided it would be better to gather this information automatically.
Testing notes
Checkout the other pull requests first and set up a Dataverse instance with some metadata languages configured.