-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
178 publish collection use case #182
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Approving!
If you can also @GPortas make a quick code review while doing the QA will be great, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! only one minor change related to a method doc. @ekraffmiller
} | ||
|
||
/** | ||
* Publishes a collection, given its identifier and the type of version update type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the last part "and the type of version update type."
should be removed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GPortas thanks for finding that, done!
fix Publish Collection use case documentation
@ekraffmiller please merge develop into this branch before merging so we don't lose latest changes in file upload use case |
What this PR does / why we need it:
Creates a use case for publishing a collection
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Suggestions on how to test this:
Inspect code and run tests.
Is there a release notes update needed for this change?:
Additional documentation: