Issue 12225

Support automatic follow-up on changed "owns" relationship

12225
Reporter: ahahn
Assignee: kbraak
Type: Improvement
Summary: Support automatic follow-up on changed "owns" relationship
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-11-09 11:23:56.301
Updated: 2012-11-27 16:41:47.025
Resolved: 2012-11-27 16:41:42.24
        
Description: Context: dataset-aware registry; attribution (new portal)

Background: the dataset-aware registry allows to model both "serves" and "owns relationships. As these are made more transparent in the new data portal, and are sold as the way towards better attribution of both owners and hosts of datasets, we can expect a major wave of re-wiring datasets, both for international networks (OBIS) and country participants (GBIF-Spain, others). At present, such an ownership change is easy to do on the registry side, but needs manual follow-up on the index backend database to re-use the existing indexed dataset: the indexing process will generate a duplicate (which loses the history: dataset id date of first registration, logs, feedback), which then has to be rewired manually on the backend, and likewise the duplicate removed manually.

Request: If a dataset already exists (registry UUID) and is recognised to have moved to a different owning institution (registry "owns relationship), the HIT synchronisation process should not generate a new dataset entry under the new (or existing) organisation, but instead update the index to re-link the dataset to the new owning institution, preserving the dataset's id and history. Index-side, this involves changes to (list probably not complete):
- data_resource.data_provider_id
- resource_access_point.data_provider_id
- raw_occurrence_record.data_provider_id
- (occurrence_record.data_provider_id: should now be redundant, as this is regenerated at rollover anyway)
- gbif_log_message.data_provider_id (though: check whether this is used anywhere in the portal app or web services. gbif_log_message updates have the additional complication that they would have to be done both on the live portal (usage logs) and on the index (indexing logs))
]]>
    


Author: kbraak@gbif.org
Created: 2012-11-27 15:07:11.929
Updated: 2012-11-27 15:07:11.929
        
Changes committed to index synchronizer in http://dev.gbif.org/code/changelog/gbif-indexingtoolkit?cs=1810

Andrea, please verify this is working to your satisfaction. 
    


Author: ahahn@gbif.org
Comment: Tested, looks ok - closing
Created: 2012-11-27 16:41:42.264
Updated: 2012-11-27 16:41:42.264