Installation deletion should not be allowed when it hosts datasets

14399
Reporter: kbraak
Type: Bug
Summary: Installation deletion should not be allowed when it hosts datasets
Priority: Critical
Status: Open
Created: 2013-11-22 10:57:08.197
Updated: 2013-12-12 17:32:47.233
        
Description: If an installation is deleted while it hosts datasets there will be an inconsistency in the occurrence records which still think the deleted org is the  host. Action is taken immediately (m/r job syncing occurrences to registry) when registry change messages are sent so the registry must always be consistent.

So: when delete is pressed for an installation, a validation check should look for hosted datasets and prevent deletion until those datasets are either hosted by another org or deleted.]]>
    

Author: ahahn@gbif.org
Created: 2013-11-22 11:19:49.827
Updated: 2013-11-22 11:19:49.827
        
We may want to distinguish between a deleted organization and a deleted installation.

Both get logically deleted. An installation may be deleted if it does not serve any datasets (explicitly confirm dataset deletion first, or allow to move datasets). The organization hosting the installation may run other installations or be in an intermediate state where a new installation is being prepared, but not yet registered. Deletion of the organization itself needs to be handled by a separate explicit request.