Issue 10760

Registry metadata update: handle removed datasets information flow

Reporter: ahahn
Type: SubTask
Summary: Registry metadata update: handle removed datasets information flow
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-02-03 15:44:58.764
Updated: 2013-12-12 17:27:11.795
Resolved: 2013-12-10 15:35:37.345
Description: What actions should the endpoint monitoring system take when it detects removed datasets (e.g., from a DiGIR response)?
- as a  first stab: alert registry admins and index operators (messaging)
Message like: Previously registered dataset x from publisher y, endpoint z could not be confirmed on metadata update on [date]

Eventually refine:
- Automatic firing of emails to publishers?
(not initially: there are some spamming perception dangers here)

-- if a previously registered dataset disappeared at the endpoint, automatic email interaction could be used to confirm delete from registry - YES/NO; but this is risky (reaching uninformed contacts; accidental confirm; how to prevent repeated requests / log responses?). Explore further.
-- the registry admin console could list the problematic endpoints and provide ability to click a button to fire the email to the publisher. However, browsing individual web pages does not appear to be the most efficient way to handle this task, so that it is probably better handled through messages to admins / helpdesk and follow-up communication there.


Created: 2013-12-10 15:35:37.385
Updated: 2013-12-10 15:35:37.385
Metadata updates will run periodically, and there is a well defined procedure to flag datasets as deleted, if they have been removed from an endpoint.

Closing issue.