Issue 10765

Email-alerts on registration of new datasets

10765
Reporter: ahahn
Type: SubTask
Summary: Email-alerts on registration of new datasets
Priority: Critical
Status: Open
Created: 2012-02-03 15:56:22.403
Updated: 2014-05-07 09:03:41.393
        
Description: - New technical endpoints and dataset added to the registry need to be reported to the institution that they are registered under.
- the same applies to Node Managers that the institution is endorsed by: should be informed of new datasets registered under their domain (no endorsement workflow for datasets so far; only information)

e.g. somebody registers new datasets through an IPT, we currently alert data publishers. The same should apply to anything added through the admin console directly or via a "registerme" page.

Do we need to supply an opt-out pathway for contacts who do not want to receive any more information mails?]]>
    


Author: kbraak@gbif.org
Created: 2013-12-10 15:53:07.97
Updated: 2013-12-10 15:53:07.97
        
We no longer send an email to publishers after a dataset gets registered via an IPT. Actually, we currently don't have any email-alerts on creation/registration of anything.

[~jlegind@gbif.org] or [~ahahn@gbif.org] could you please comment if such email-alerts on creation/registration are needed?
    


Author: kbraak@gbif.org
Created: 2013-12-10 16:08:44.82
Updated: 2013-12-10 16:08:44.82
        
To quote AH:

They are definitely needed. As the registration of a dataset can be quite decoupled from both the owning institution and the endorsing node, we should re-introduce notifications medium term, possibly with an opt-out possibility for people who feel harassed. The institutional contact should be made aware when their dataset comes on (esp. if the registration triggers automatic indexing), and likewise the Node Managers should be kept informed. I am not too particular whether that should happen on the registry side when the IPT registration comes in, or when the dataset is indexed for the first time (then including the link to the dataset page), that would need discussing. Might need some consultation with Nodes / [~olafbanki] as well.
    


Author: olafbanki
Comment: We can definitely get some advice from Nodes on what is their preferred moment they do want to get notified. I believe there would be quite some interest from Nodes in being notified. If this needs a consultation, it would be best to group it with other needed input around data publishing. Cheers, Olaf
Created: 2013-12-10 16:14:34.519
Updated: 2013-12-10 16:20:37.566


Author: jlegind@gbif.org
Comment: [~kbraak@gbif.org],  [~ahahn@gbif.org] - I would like to see these registry notifications when datasets are created and deleted via IPT or similar, if for no other reason than being able to check whether the action really went through. It will be a good way of spotting issues around new datasets as it is the time where they are most vulnerable.
Created: 2013-12-11 15:53:44.342
Updated: 2013-12-11 15:53:57.784


Author: pacopando
Created: 2014-05-07 09:02:59.308
Updated: 2014-05-07 09:03:41.336
        
I requested this recently to Burke by email. Burke redirected me here. My wordinig on the issue was:

"the issue: having some publishers  updating datasets from our countries without we (the nodes) noticing that; and so preventing us from keeping the tally on publication events or running data quality checks. So, would it be possible to create a procedure so that every time a publication event takes place the relevant node is informed?"

I have noticed that this issue (after 6 months) remains "Unassigned", Any way to move this forward? Thanks. Paco