Notifications: Customer use case may need subscription model for notifications.

[kcondon]

Christine discussed a use case for notifications that may require a subscription model:

A world-wide research team with 200+ members working iteratively on datasets. There are two teams, one is a data collector, producing new versions of datasets. The other, the researcher/analyzers, selectively uses the dataset versions depending on how much or how interesting the new versions are, based on a qualitative description of the changes and potential recommendation put in the version notes by the collectors.

Email notification is most important since the analyzers are not likely to be logging into dataverse and checking. Having the version notes or some user created message in the email is important.

[pdurbin]

See also a use case and webhooks discussion in this issue:

• Allow for Dataverse to send a notification / synching service (web hook) to an application that is using our Data Deposit API #900

Also a whole notification system is being spec'ed out at https://github.com/CenterForOpenScience/SHARE where @posixeleni and I are listed as part of a working group: http://www.arl.org/focus-areas/shared-access-research-ecosystem-share/share-steering-and-working-groups#technical

[kcondon]

A user has just asked for limiting notifications to a specific user among several admins and was interested in the subscription model. See RT 228420, 228414

RT 228420:
A subscription model to notifications sounds great.

It would be helpful in our case that all data request notifications go to my email address only,
so the other admins don't get inundated with auto-generated emails (especially when a large number of requests happen).

RT 228414:
We wonder if it's possible to configure the Dataverse email notifications.
So when access has been requested for a restricted file on our site, the
notifications will ONLY go directly to my email address instead of being
sent to all of our administrators.
(see attached for example).
I hope the new feature will be implemented soon.

[pdurbin]

It sounds like there is (or was) a fair amount of interest in this feature.

[mheppler]

There is a duplicate of this issue at #2420. Should we copy+paste the info from one and close the other? (Full disclosure, I edited the title of the other issue to make these two issues easier to find.)

[djbrooke]

@mheppler - sure, feel free to take what's relevant from that issue and paste it in here.

[mheppler]

In the issue #2420 @raprasad outlined a use case similar to this feature request. I have closed that issue as a duplicate, in favor of tracking this original issue going forward.

Allow a researcher to register for dataset updates. If a dataset is updated, the researcher receives an email

[soodoku]

classic use case = being notified of errors

[philippconzett]

Another useful feature to include in a more flexible notification system would be the possibility to easily customize the content of the notifications.

[cmbz]

2024/08/19 - Will add to new epic on Feature: Notifications. Note that some notification tuning can be performed at the Installation level.