Skip to content
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

IPT email notification #2409

Open
mike-podolskiy90 opened this issue Apr 22, 2024 · 3 comments
Open

IPT email notification #2409

mike-podolskiy90 opened this issue Apr 22, 2024 · 3 comments
Assignees
Milestone

Comments

@mike-podolskiy90
Copy link
Contributor

Recently, the question arose about the implementation of email notifications in IPT.
This can be useful in many situations, but we need to be careful with the implementation.

Related #2133 #2408

@mike-podolskiy90 mike-podolskiy90 self-assigned this Apr 22, 2024
@mike-podolskiy90 mike-podolskiy90 added this to the 3.1.0 milestone Apr 22, 2024
@mike-podolskiy90
Copy link
Contributor Author

For what functionality it would be useful?

@dbloom
Copy link

dbloom commented Apr 22, 2024

Per the issues linked above, notification could be very useful to notify selected IPT Admins about:

  • Aborted publication events (possibly including the error log in the message)
  • Resources that are published with (significantly) fewer records than the previous version
  • Out of date Core/Extensions in use on the IPT
  • Current musical recomendations by @MattBlissett

I could think of several other potential uses, such as notifications when new resources are created, but honestly, I'm not certain those sorts of alerts are useful for most IPT managers, nor do I think GBIF wants to monitor and report on every little item that occurs in a given installation.

I would be happy to test some of these features on the VertNet IPT, if that would be userful.

@mike-podolskiy90
Copy link
Contributor Author

Thank you very much David!
Note, it's not for the upcoming release. We will try to plan it this year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants