Dataset with several active access points: auto-delete metadata operator ("red") for unused protocol(s) from HIT UI

11926
Reporter: ahahn
Assignee: kbraak
Type: Task
Summary: Dataset with several active access points: auto-delete metadata operator ("red") for unused protocol(s) from HIT UI
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-09-19 16:36:44.964
Updated: 2013-12-09 15:29:08.47
Resolved: 2013-12-09 15:29:08.436
        
Description: Some datasets are served through more than one active protocol. As several access points exist, we want to maintain them in the registry and web portal, but not use all of them for indexing. As tagging is not possible in these cases, the HIT automatically uses the protocol with the highest priority if several different ones are detected. It still generates the metadata update operator in the HIT operator interface, though, which will lead to confusion.

Removal of the operator is technically possible for the user, but requires detecting and analysing the situation through comparison with the registry in each individual case. In situations where a decision on priority can be made automatically, we should also automatically logically remove the unused operators from the HIT user interface.

Example:
Royal Botanic Garden Edinburgh (http://gbrds.gbif.org/browse/agent?uuid=605c3cb0-f762-11e1-a439-00145eb45e9a) serves two datasets - each both through an active Tapir endpoint, and also as a Darwin Core Archive. In the HIT (http://hit.gbif.org/datasource/list.html?filter=provider&value=royal+botanic+garden), all are added, despite the fact that the DwC-A endpoints should take priority. We will never want to harvest the Tapir endpoint, so that it should be removed from the interface. ]]>
    

Author: omeyn@gbif.org
Comment: just fixing problems caused by internet hooligan
Created: 2013-03-04 14:00:47.904
Updated: 2013-03-04 14:00:47.904

Author: kbraak@gbif.org
Comment: Won't fix. Closing issue.
Created: 2013-12-09 15:29:08.467
Updated: 2013-12-09 15:29:08.467