IQSS/9247 Curation Status Updates#11268
Merged
ofahimIQSS merged 67 commits intoIQSS:developfrom Jun 26, 2025
Merged
Conversation
IQSS/9247-CurationStatus_updates
src/main/java/edu/harvard/iq/dataverse/engine/command/impl/SetCurationStatusCommand.java
Outdated
Show resolved
Hide resolved
stevenwinship
approved these changes
Jun 20, 2025
Contributor
|
Can we update this PR with latest from dev? |
IQSS/9247-CurationStatus_updates
Contributor
ofahimIQSS
added a commit
that referenced
this pull request
Jun 26, 2025
…rationStatus_updates Fix for #11268
Merged
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: This PR extends the External/Curation Status Label mechanism:
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: Verify that curation statuses can be set/removed when the overall curation status mechanism is enabled. Verify that the status can be removed. Verify that status is removed at publication. Verify that the /api/datasets/{id}//curationStatus and /api/datasets/{id}/listCurationStates api calls return correct results, with and without the ?includeHistory=true flag. (Most of this is tested in IT tests as well.)
Does this PR introduce a user interface change? If mockups are available, please link/include them here: New facet:

Is there a release notes update needed for this change?:
Additional documentation: