Global locking of dataset metadata

10778
Reporter: jcuadra
Type: NewFeature
Summary: Global locking of dataset metadata
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-02-03 17:34:17.545
Updated: 2013-12-16 17:50:43.309
Resolved: 2013-12-10 12:18:54.407
        
Description: We should start with global locking, then consider locking individual fields or specific blocks of information (eg. contact data).

An "overwrite" flag is needed --> This will lock the interpreted version from being updated on registry metadata synchronization.

BUT if for example Verbatim version 1 (January 2012) is different from Verbatim version 2 (July 2012), and locking is ON, then the admin console should clearly state the change so that an administrator can take proper action, as possibly the data publisher changed useful information. Also mark this as relating to the messaging definition task: a registry admin should be able to see conflicts when viewing pages, but cannot keep browsing all of them to spot possible issues -> need additional way of checking]]>
    

Author: kbraak@gbif.org
Comment: There is a locked for auto update flag on a Dataset. The additional features outlined in this issue aren't needed. Closing issue.
Created: 2013-12-10 12:18:54.437
Updated: 2013-12-10 12:18:54.437