Open spalp opened 6 days ago
@spalp Thanks Salza
I'll move this issue to the registry GitHub repository since email notificiation is its functionality
To add some context: in most cases, we would expect that the registered publishing organization is in control over who they hand the registry token to, so that dataset publication is under their full control. Once an organization is registered to an IPT, though, it can be chosen by IPT administrators with the appropriate scope to publish datasets under. In the case of a community IPT (like the cloud-hosted ECA installation), where several administrators may have access, this required additional awareness and coordination.
I would agree that notifying the contacts of the publisher would be useful. Maybe that needs to be an opt-in solution, though, since there are different models of publisher support, and we would like to avoid excess and potentially confusing communication.
I see your point. Being an opt-in solution sounds reasonable. Perhaps to avoid sending out too many emails, could we have a filtering criteria for the notifications: e.g. to send a notification email only when the email of the person publishing/registering the dataset does not match the email of the Technical point of contact or any of the points of contact of the publisher?
As a point of contact for the following publisher, I would like to be notified when a new dataset has been published under our organization. Sometimes, the person who publishes the dataset have not coordinated this with the organization (as is the case with the following dataset: Small mammals of Yugoslavia 1992 atlas). Notifying the publisher's contact may help us to review that the metadata is correct and confirm that we may take responsibility and ownership of the dataset.