harvest-service: modify behavior of metadata harvesters (orange bioDatasources)
11008
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: harvest-service: modify behavior of metadata harvesters (orange bioDatasources)
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-03-20 15:50:37.037
Updated: 2013-01-15 14:40:02.954
Resolved: 2012-04-20 16:44:05.551
Description: Orange bioDatasources have the ability to 1) schedule a metadata update and 2) synchronize metadata in Portal DB - this will not change. What an orange bioDatasource represents changes (see issue HIT-10) as does what happens during 1) schedule a metadata update.
Change needed:
In the old HIT, it would be the job of the HIT to expand the resources behind DiGIR and BioCASE resources. This is what Fede's new Metadata Synchronizer will do now instead. When the HIT user schedules a metadata update against a technical installation, all it does is kick off Fede's Metadata Synchronizer and that's it. ]]>
Author: kbraak@gbif.org
Created: 2012-04-20 16:42:21.82
Updated: 2012-04-20 16:42:21.82
DiGIR and BioCASE accesspoints are no longer represented as orange bioDatasources. Neither are TAPIR resource accesspoints.
Instead, there are now orange bioDatasources representing the actual technical installations for DiGIR, BioCASE, and TAPIR.
DwC-A orange bioDatsources will continue as they are (representing the resource accesspoint), since Fede's synchronizer doesn't handle DwC-As yet.
Author: kbraak@gbif.org
Comment: The biggest change made for this issue, was really a change to the scheduler. When it is recognized a job relating to metadata update for DIGIR, BIOCASE, or TAPIR occurs, Fede's synchronizer is triggered.
Created: 2012-04-20 16:43:56.348
Updated: 2012-04-20 16:43:56.348