Repository navigation
feat: add dataset curation status and submit-for-review use cases - #500
Open
ChengShi-1 wants to merge 1 commit into
Open
ChengShi-1 wants to merge 1 commit into
ChengShi-1 wants to merge 1 commit into
Conversation
7 tasks
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
github-actions
Bot
added
FY27 Sprint 8
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:
Expose six public use cases so consumers can load allowed curation labels, read current status and history, set or remove a label, and submit a draft for review without making direct HTTP requests. Supports numeric and persistent identifiers and preserves removal records and optional backend fields.
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Suggestions on how to test this:
Check if all tests are passing
Is there a release notes or changelog update needed for this change?:
Added an entry under
CHANGELOG.md→[Unreleased]→Added.Additional documentation:
Updated
docs/useCases.mdwith all six use cases, examples,:AllowedCurationLabelsconfiguration, effective label-set inheritance, required permissions, and configurable status visibility.