No subject

designed to ensure that a harvest source couldn't be harvested more
than once simultaneously and get confused. Since the harvest job
becomes multiple gathers and further split into fetches, James was
keen to make sure a source could only have one job for each run of the
cron. BUT I'm sure we could get the backend (Redis if not RabbitMQ) to
tell us the status of the job (and its related gather/fetches) and
stop further ones being created until it is done.

Would the various CKAN sites using the harvester (OKF, Frauenhofer,
Canada, Washington etc.) be happy about this change? It would be on
the CKAN 2.x code.

Dave