redirect to draft version of dataset after editing terms#1016
Open
ekraffmiller wants to merge 6 commits into
Open
redirect to draft version of dataset after editing terms#1016ekraffmiller wants to merge 6 commits into
ekraffmiller wants to merge 6 commits into
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
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:
After saving changes in the terms tab, it should navigate to the Draft version of the dataset.
Which issue(s) this PR closes:
Special notes for your reviewer:
In the API, assigning a guestbook is not currently generating a draft version. There is an issue for this here:
IQSS/dataverse#12528
Suggestions on how to test this:
Edit all the terms tabs and check that it navigates to the Draft verson of the Dataset page.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no
Is there a release notes or changelog update needed for this change?:
Additional documentation: