Skip to content
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

Request: Scheduled harvesting #5

Closed
MapZombie opened this issue Jul 28, 2016 · 1 comment
Closed

Request: Scheduled harvesting #5

MapZombie opened this issue Jul 28, 2016 · 1 comment

Comments

@MapZombie
Copy link

It would be great to have the same functionality as the previous version in terms of scheduling harvests. As well as the feature to have only new/updated metadata get harvested.

@pandzel-zz
Copy link

Current harvester design goes way beyond that; there is a "trigger" concept which allows to create any type of entities which would start up harvesting process. One type is a temporal trigger which does scheduled type triggering. Another type of trigger might be a trigger which observes a local folder - once a metadata is being dropped into that folder, it triggers harvesting of that folder. Yet another would be a a trigger which activates harvesting once a particular message arrives through the message queue (JMS).

Current implementation has full potentials available through REST interface (there is no UI yet). More types of triggers will arrive with the subsequent releases.

It is worth mentioning that you are not limited to scheduling through build-in scheduler; it is possible to schedule through Linux (Unix) crontab mechanism or Microsoft Windows task scheduler.

One may say: the sky is a limit...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants