You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to decide if we want to have moderation on changes, i.e. when someone would update their information from the website, will we require approval before the change is saved to the Person model? Note that if we do not require approval, changes can still be reverted through Reversion.
This is probably what the Modifications model was trying to achieve. Relates to #52 and #56.
The text was updated successfully, but these errors were encountered:
If we build this feature such that we can also let new members subscribe through this mechanism it could be useful. But that can also be achieved by creating an application just for that.
For just the 'change-case' I think this is not needed. I do think the secretary should get an update when someone changes his/her information so strange behaviour can be detected immediately.
So TLDR; moderation on changes is not necessary in my opinion, just a notification.
Alright. The notification could simply be made from the selfservice application as well. Might be worth implementing #52 to register where the change came from in Reversion as well.
We need to decide if we want to have moderation on changes, i.e. when someone would update their information from the website, will we require approval before the change is saved to the Person model? Note that if we do not require approval, changes can still be reverted through Reversion.
This is probably what the
Modifications
model was trying to achieve. Relates to #52 and #56.The text was updated successfully, but these errors were encountered: