-
Notifications
You must be signed in to change notification settings - Fork 494
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
8290 harvest client api #9174
8290 harvest client api #9174
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.
Overall this looks good but please take a look at my comments, @landreev. Happy to discuss. Thanks.
|
||
- archiveDescription: What the name suggests. If not supplied, will default to "This Dataset is harvested from our partners. Clicking the link will take you directly to the archival source of the data." | ||
- set: The OAI set on the remote server. If not supplied, will default to none, i.e., "harvest everything". | ||
- schedule: Harvesting schedule. Defaults to "none". |
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.
Can we have an example of a schedule? What does it look like?
On a related note, I see this comment in the code:
// TODO: Make schedule configurable via this API too.
Perhaps this means that schedule cannot be configured via API? If so, we should say so. Or if schedule can be set on create but not on modify we could document that under "Modify a Harvesting Client".
src/main/java/edu/harvard/iq/dataverse/api/HarvestingClients.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
(I have added some simple restassured tests, as discussed) |
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. Approving. I did notice that the last two Jenkins run failed so I pushed a tiny commit to kick off another run.
Issues found:
|
Kevin is satisfied with everthing, but uncovered a missed use case. |
What this PR does / why we need it:
Our API for creating harvesting clients was an afterthought, we never got it fully to work, and never advertised or documented it. However a user discovered it and reported that it wasn't working. We will need this API to create functional restassured tests for harvesting clients (there's a dedicated issue that's been prioritized recently).
This PR provides a working API for creating a new harvesting client (with an
-X POST
method) and documents it in the guide. The documentation part of the PR should thus close the issue #8267 as well.Which issue(s) this PR closes:
Closes #8290
Closes #8267
Special notes for your reviewer:
I'm not adding restassured tests for this API in this PR, because there's a dedicated issue for harvesting tests that's also been prioritized.
Suggestions on how to test this:
It should be possible to create a new client, with an
-X POST
method, as documented. The List, Edit and Delete, not specifically mentioned in the issue, should also be working as documented.Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: