Issue 11449

Identify if data resources are deleted or not during rollover

Reporter: kbraak
Assignee: trobertson
Type: Improvement
Summary: Identify if data resources are deleted or not during rollover
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-06-20 12:14:54.889
Updated: 2013-12-17 15:23:07.41
Resolved: 2013-09-27 19:33:38.198
Description: Note, this issue depends on the release of the dataset-aware registry.

Since the dataset-aware registry knows about all datasets, no data resource should exist in the processed index if it doesn't exist in the registry.

Therefore, during the rollover, identify whether a data resource corresponds to a deleted dataset before proceeding with processing. ]]>

Comment: Automatic deletion implies not only not handling the dataset in "extraction"/rollover processing, but also flagging the data resource entry as deleted in the index, and most importantly, to remove existing GBIF_log_message entries, as these create problems in the portal app if they get orphaned. Also need to check whether we have to remove existing raw_occurrence_records and entries from satellite tables, but here I am not sure on the impact of orphaned records (e.g. in preview pages, downloads or web service responses).
Created: 2012-06-20 16:53:20.959
Updated: 2012-06-20 16:53:20.959

Comment: won't do any more rollovers
Created: 2013-09-27 19:33:38.227
Updated: 2013-09-27 19:33:38.227