Feature Request: notifications for superusers when datasets are published
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Add a feature that allows superusers (or sysadmins) to automatically receive notifications—such as email alerts—whenever a new dataset is published anywhere in the Dataverse instance. This would help repository maintainers monitor activity and ensure quality control across all collections without needing to manually subscribe to or be added as administrators of each dataset or dataverse.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Superusers / Sysadmins
What inspired the request?
At the Barcelona Supercomputing Center (BSC), we maintain our own Dataverse instance and would like to stay informed whenever a new dataset is published. Currently, notifications are only sent to users who have specific roles (e.g., admin or curator) within a dataverse or dataset. As superusers responsible for overseeing the repository, it would be useful to automatically receive these notifications at the instance level.
What existing behavior do you want changed?
Currently, notifications are limited to the roles assigned within individual dataverses or datasets. Superusers do not receive publication notifications unless they are explicitly added to each dataverse.
Any brand new behavior do you want to add to Dataverse?
Introduce a configurable option (e.g., in the admin dashboard or configuration file) that enables superusers or sysadmins to automatically receive notifications when any dataset across the instance is published. Ideally, the feature could support:
- Email notifications for new dataset publications (and possibly updates or deletions)
- A toggle to enable or disable this notification type for superusers
- (Optional) Support for a shared email address or mailing list for admin notifications
Any open or closed issues related to this feature request?
Not that I’m aware of, but please feel free to link if similar requests exist.
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
We’re not currently planning to implement it ourselves, but we’d be happy to contribute feedback, testing, or documentation support if this feature moves forward.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the existing role-based publication notification flow and the configuration or admin settings that control it. Done means a defined, configurable instance-wide notification behavior for superusers or sysadmins, with the requested publication scope and delivery method covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100