Registry metadata update: handle offline endpoint information flow

10764
Reporter: ahahn
Type: SubTask
Summary: Registry metadata update: handle offline endpoint information flow
Priority: Major
Status: Open
Created: 2012-02-03 15:50:44.353
Updated: 2013-12-12 17:32:50.569
        
Description: On automatic metadata updates, some logging will keep track of endpoint availability.

Logging should track
- endpoints that are offline (nonexisting or timing out)
- endpoints that do not respond with one of the expected response types (e.g showing 404, linking to a http page, etc)

Messaging intended for
- data publishers: fully automated offline endpoints notification (define rules like "if an endpoint has been continuously down in 10 subsequent metadata updates, send notification to dataset and publisher technical contact")
- other?]]>
    

Attachment Screen Shot 2013-12-10 at 3.39.44 PM.png

Author: kbraak@gbif.org
Created: 2013-12-10 15:44:18.955
Updated: 2013-12-12 16:43:45.238
        
Metadata updates can currently be triggered using the Registry Console. In the event of failure, a clear message is displayed under synchronization history (see screenshot).

Outstanding, is automated offline endpoint notification. Or a convenient way for the Registry Console operator to find out which updates failed.