in demo/eval env, configure root collection alias and name #11196
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:
In Milestone F of the container proposal and in recent discussions, we've said we want people to be able to configure the alias and name of the root collection.
Which issue(s) this PR closes:
Special notes for your reviewer:
I could have used https://guides.dataverse.org/en/6.5/api/native-api.html#update-a-dataverse-collection to update both the alias and name in one request but I went with https://guides.dataverse.org/en/6.5/api/native-api.html#collection-attributes-api because it was easier.
I have a mental TODO to try testing a name with a space in it.
I also started a topic in Zulip for discussion: https://dataverse.zulipchat.com/#narrow/channel/375812-containers/topic/in.20demo.2Feval.20env.2C.20configure.20root.20collection.20alias.20and.20name/near/496383414
Suggestions on how to test this:
Follow the provided instructions.
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?:
Yes, coming.
Additional documentation: