-
Notifications
You must be signed in to change notification settings - Fork 12
Who should be notified that records are ready for review? #153
Comments
In the state diagram in #211, the following states trigger notification:
|
I think the more pressing question before tackling local mail delivery in #201 is: who wants to get an email when a record is completed in staging? @joycebcat? @jpstroop? @tpendragon? Maybe we should setup a dummy account for this, so we can check to see if it actually works, without having to sign up to actually get these emails in our real accounts? |
@jpstroop Yes, you're right that we have several points in the workflow where we want to send notifications. At some point, we will also need to resolve the question of how different environments behave. My thinking of how to approach #201 was:
Once that's done, this issue (#153) would be a good vehicle for deciding on a more flexible system for deciding who gets notified (either a mailing list or using plum's roles). E.g., we could make roles for each workflow state ( |
@kevinreiss do you know the process for getting a dummy email address? |
I thought it would be easier to setup a dummy email address than figure out a long-term approach. But how about:
This will be very flexible, and allow admin users to manage notifications. My understanding is that it's mostly admin users who want to be notified. |
Sort of related to #210 |
It is mostly admin users who want to be notified except for the use case of notifying the project initiator at the "final review" and "complete" stages. |
Unless the developers are admins...which maybe we don't need to be for the production system. |
reviewer
role?The text was updated successfully, but these errors were encountered: