Crawler/Indexer: inform of changes due to merged publisher entries

10772
Reporter: ahahn
Type: SubTask
Summary: Crawler/Indexer: inform of changes due to merged publisher entries
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-03 16:52:49.517
Updated: 2013-12-12 17:27:12.238
Resolved: 2013-12-10 15:59:17.646
        
Description: If two publisher entries are merged that potentially both already have service endpoints and datasets attached, an indexer/crawler needs to be informed of these changes, as this requires follow-up in indexing management and data synchronisation (reconnecting datasets). Information transmitted:
- publisher entry x updated
- publisher entry y deleted
- dataset a disconnected from publisher y
- dataset a connected to publisher x identical to previous publisher y version
- technical access point disconnected from publisher y
- technical access point connected to publisher x identical to previous publisher y version

Messaging should allow the indexer to follow up on the updates without deleting and re-creating datasets, but instead detaching and re-attaching them on the index side, and removing the deleted data publisher entry after that.]]>
    

Author: kbraak@gbif.org
Created: 2013-12-10 15:59:17.679
Updated: 2013-12-10 15:59:17.679
        
A result of REG-126, was that it was agreed a merger feature isn't needed.

Closing issue.