synchroniser-gbif-refactor: get organization and resource metadata from Registry

11006
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: synchroniser-gbif-refactor: get organization and resource metadata from Registry
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-03-20 15:13:35.746
Updated: 2013-01-15 14:40:04.006
Resolved: 2012-06-22 15:14:24.421
        
Description: The refactored HIT must continue to create/update data_provider and data_resource entries in the Portal DB at the beginning of synchronization just like the old version.

In the old version, when a job was sent to synchroniser-gbif, it knew all the data-provider and data-resource metadata in advance, having gotten it during synchronization with the Registry.

In the refactored version, however, the job message will only include the UUID of the resource being synchronized. Then, it will be the gbif-synchronizer's job to call the Registry WS for all the Organization and Resource metadata needed.

As a reminder, the synchronizer should always update the metadata for data_resource, data_provider, agents, etc entries even if they exist already. ]]>
    

Author: kbraak@gbif.org
Comment: As soon as issue (REG-252) is resolved, and DwC-Archive metadata derived from the eml.xml file is populated in the Registry, the HIT's synchronizer must be updated.
Created: 2012-06-20 10:15:51.512
Updated: 2012-06-20 10:16:22.521

Author: kbraak@gbif.org
Comment: Issue resolved. When the Registry sync populates the Registry with metadata for Dwcas, the synchronizer will again have to be modified. We can open a separate issue for this when the time comes.
Created: 2012-06-22 15:14:24.454
Updated: 2012-06-22 15:14:24.454