Implement Use Case for Deaccession Dataset#255
Merged
ofahimIQSS merged 5 commits intodevelopfrom Feb 14, 2025
Merged
Conversation
g-saracca
requested changes
Feb 10, 2025
Contributor
g-saracca
left a comment
There was a problem hiding this comment.
Some minor suggestions 👌🏼
g-saracca
approved these changes
Feb 12, 2025
Contributor
g-saracca
left a comment
There was a problem hiding this comment.
Thanks! All good now, approving!
Contributor
|
tests passed- 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.
What this PR does / why we need it:
From the Q1 2025, we have a goal of implementing deaccession dataset part.
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Suggestions on how to test this:
Visual inspect, and tests
Is there a release notes update needed for this change?:
Additional documentation: