Issue 11957

GBIF-Spain: when metadata response becomes available, lift admin_override for configurered datasets in registry

11957
Reporter: ahahn
Assignee: jlegind
Type: Task
Summary: GBIF-Spain: when metadata response becomes available, lift admin_override for configurered datasets in registry
Priority: Major
Status: Open
Created: 2012-09-28 11:27:11.21
Updated: 2013-12-13 13:43:14.886
        
Description: On Sep 27, 2012, all datasets from GBIF-Spain were marked with an admin_override flag in the registry. This flag should be lifted from those datasets that are still contained in the metadata response, once that response is available again.

Background:
Apart from metadata updates, the override flag also prevents that datasets get automatically deleted if the access point is up, but the dataset is no longer found there. The use case that triggered this behaviour is GBIF-Spain: they intentionally disconnected 2/3 of their datasets (DiGIR) because the metadata response got so slow as to basically never come back (due to the live counts on > 100 datasets), and the concerned datasets were static anyway. The disconnected datasets are therefore no longer found in the DiGIR metadata response, and would under the new registry setup be auto-deleted (logically, i.e. flagged as deleted) from the registry. We do not want that in this case; the datasets should remain registered and indexed. As no metadata response at all was available for cross-checking at the time of flagging, though, now all and not only the de-configured datasets have been marked. If/when a metadata response becomes available again, this should be corrected so that the configured datasets are included in registry updates again.]]>