-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notifications: Customer use case may need subscription model for notifications. #868
Comments
See also a use case and webhooks discussion in this issue: 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 |
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: It would be helpful in our case that all data request notifications go to my email address only, RT 228414: |
It sounds like there is (or was) a fair amount of interest in this feature. |
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.) |
@mheppler - sure, feel free to take what's relevant from that issue and paste it in here. |
classic use case = being notified of errors |
Another useful feature to include in a more flexible notification system would be the possibility to easily customize the content of the notifications. |
2024/08/19 - Will add to new epic on |
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.
The text was updated successfully, but these errors were encountered: