DANS - Multifile edit #11271
Open
DANS - Multifile edit #11271
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
qqmyers
added
Size: 3
qqmyers
added a commit
to QualitativeDataRepository/dataverse
that referenced
this pull request
Feb 20, 2025
qqmyers
added a commit
to QualitativeDataRepository/dataverse
that referenced
this pull request
Feb 20, 2025
qqmyers
added a commit
to QualitativeDataRepository/dataverse
that referenced
this pull request
Feb 20, 2025
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: Analogous to the mutli-file delete endpoint, this PR adds an API call allowing updates to the metadata of several files at once, for reasons of efficiency with large numbers of files.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: A new test in DatasetsIT covers the basics. You should be able to add some files, submit a json array of file metadata objects (see example in the native api docs) and see all the requested changes. This should work on a draft version or starting from a published version (where it will create a new draft). Sending in a file id that doesn't exist, or one in a different dataset, or trying to restrict a file that's already restricted, etc. should result in an error (400). Not having edit perms on the dataset should result in 403.
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: