clarify "Set Citation Data Field Type for a Dataset" in API Guide #10237
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
Added clarification to what is affected in Set Citation Data Field Type for a Dataset
pdurbin
changed the title
|
"Looks good!" from @sbarbosadataverse in Slack. |
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.
Added clarification to what is affected in Set Citation Data Field Type for a Dataset
What this PR does / why we need it: Adds some additional information about how the endpoint affects dataset versions and files.
Which issue(s) this PR closes: #10227 (comment)
Special notes for your reviewer:
Suggestions on how to test this: Created a demo dataset to test the changes to each version here: https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/X5GFFN.
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: