|Status:||Closed||Start date:||Nov 20, 2015|
|Assignee:||Panagiota Koltsida||% Done:|
|Sprint:||zz - Search and Index Enhancement|
#2 Updated by Pasquale Pagano about 4 years ago
We are thinking to add a new service to the enabling layer. It will be a sort of meta-scheduler. Currently it supports typical invocation of repetitive tasks with the same cron capabilities. This will allow to schedule the tasks at level of different VREs. Harvesting and frequency of harvesting could then be managed by this new service. It just needs a service to call periodically. In this sense you may avoid to implement everything about scheduling in your OAI-PMH harvesting.
#3 Updated by Massimiliano Assante almost 4 years ago
I very welcome the fact that you "linked" this ticket to the work package, perhaps it would be better to "attach" these activities to WP9 Tasks (T9.1, T9.2 or T9.3) instead of the WP directly (Set as Parent task, or related, the T9.1, T9.2 or T9.3 and not WP9)
Is this sound for you?
#6 Updated by Massimiliano Assante almost 4 years ago
I'm removing the parent task of this ticket as it was wrongly attached as subtask of the WP 9 ticket. The correct way is to put this ticket as related to the corresponding Project Task (T9.1 in this case)
also, @firstname.lastname@example.org could you please provide us with an update on the status of this activity? It is in progress since 2 months, no further information have been added. It would be beneficial if you could set an estimation of the due date for this activity.
#8 Updated by Panagiota Koltsida almost 4 years ago
- % Done changed from 0 to 50
Currently we have almost finished the implementation of a generic OAI-PMH harvester service and it remains to directly store the harvested records to the available index by directly interacting with it.
The OAI-PMH harvester can harvest OAI-PMH services that are registered to it and the harvesting is done either periodically (per URI if set) or explicitly when requested.