Issue 11004
harvest-service: Integrate MetadataSync
11004
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: harvest-service: Integrate MetadataSync
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-03-20 14:55:05.131
Updated: 2013-01-15 14:40:03.295
Resolved: 2012-04-20 16:59:28.946
Description: Integrate MetadataSync and HIT/ThreadPool, probably using messaging. In someway the scheduler will send a notification to the MetadataSync requesting the update of registry datasets.
The HIT should use the registry API to get UUIDs (by technical installation probably). The UUID will be included in the notification and the MetadataSync will then be able to schedule the subsequent jobs.]]>
Author: kbraak@gbif.org
Created: 2012-04-20 16:58:52.475
Updated: 2012-04-20 16:58:52.475
Fede's metadata sync is now triggered for DiGIR, BioCASE, and TAPIR technical installations. The HIT populates a bioDatasource representing the technical installation that contains the Dataset aware Registry's technical installation UUID. This is what gets passed to the metadata sync, in combination with the bioDatasource ID needed for writing log messages.
Fede has setup a RabbitMQ server and has created a convenient publisher that can be used to send a message to the queue that his metadata sync is listening to.
The sending and receiving of messages is working fine, and a metadata sync for DiGIR working fine.