docs: "Update a Dataverse Collection" vs. "Change Collection Attributes"#11002
Merged
ofahimIQSS merged 1 commit intodevelopfrom Nov 15, 2024
Merged
docs: "Update a Dataverse Collection" vs. "Change Collection Attributes"#11002ofahimIQSS merged 1 commit intodevelopfrom
ofahimIQSS merged 1 commit intodevelopfrom
Conversation
GPortas
approved these changes
Nov 15, 2024
Contributor
|
Proofread - no issues found. Merging PR |
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
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.
Preview here:
What this PR does / why we need it:
A new "Update a Dataverse Collection" API endpoint was added in #10925 and users of the older "Change Collection Attributes" endpoint (added in #9614) should probably be aware of it.
This pull request cross references the two APIs.
Which issue(s) this PR closes:
None but relates to #10904 and the PR above.
Special notes for your reviewer:
I was tempted to say that "Update a Dataverse Collection" does everything that "Change Collection Attributes" does and more but I'm not sure if it handles
filePIDsEnabled. 🤔Suggestions on how to test this:
Review the docs that are automatically built.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
No.
Additional documentation:
None.