-
Notifications
You must be signed in to change notification settings - Fork 501
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
When setting harvesting schedule to weekly, settings don't persist #4398
Comments
sekmiller
added a commit
that referenced
this issue
Jan 24, 2018
also the day of the week array is zero-based.
5 tasks
OK, settings persist in UI but found the weekly harvest is not kicking off while the daily does. |
kcondon
added a commit
that referenced
this issue
Feb 1, 2018
#4398 - Fix display of Harvest Client in edit mode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scheduling weekly harvesting is working, but the scheduled settings don't persist when I set harvesting to weekly (they do persist when set to daily). I'm seeing this on Harvard Dataverse and Demo Dataverse, both on 4.8.4.
To reproduce: I set a harvesting client to harvest weekly, and save those settings, and when I edit that client again - to check or change the harvesting schedule - the scheduling settings seem to be reset ("none" is selected instead of the weekly schedule I chose before). This makes it seem as though I didn't schedule anything the first time, that weekly scheduling won't work, and makes it difficult to manage harvesting, especially as the number of harvesting clients increases.
Labeled this as a bug since the scheduling settings for weekly harvesting should at least persist like they do when for daily harvesting settings.
Going a little further, maybe the harvesting table can indicate someplace the schedule for each client, so installation admins don't have to go through all of the edit steps to check what the schedule is for each client.
The text was updated successfully, but these errors were encountered: