If a Dataset switches technical installation, there should be some logic implemented to handle gracefully this switch

11630
Reporter: jcuadra
Type: Improvement
Summary: If a Dataset switches technical installation, there should be some logic implemented to handle gracefully this switch
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-07-25 17:01:05.129
Updated: 2013-12-16 17:50:56.127
Resolved: 2013-12-11 13:57:07.759
        
Description: With the current process, if a Dataset is changed from one technical installation to another one (e.g. moving a DS from DiGIR to IPT), what happens right now is that inside GBIFS we need to prepare ahead of this scenario. It would be desirable if there was some logic implemented in where we can automatically detect duplicate datasets (given the same title as a prexisting DS), but with different technical installations. A good mechanism would be that if the metadata-sync detects a duplicate title, the new Dataset is marked as "blocked". This "block flag would need to be manually taken care of, in other words, an admin would need to go into the admin console and merge the two Datasets somehow.

see: http://code.google.com/p/gbif-registry/source/browse/registry/trunk/registry-api/src/main/java/org/gbif/registry/api/messaging/DatasetNotification.java#13]]>
    

Author: kbraak@gbif.org
Created: 2013-12-11 13:57:07.802
Updated: 2013-12-11 13:57:07.802
        
A dataset can easily switch hosting installation. The IPT provides a dataset migration feature, making this possible for example. The Registry Console operator then has to ensure that the DiGIR/TAPIR/BioCASE version of the dataset is cleaned-up following migration.

Marking issue as won't fix.