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

Send email to organization address on file when flagging info or submitting updates #130

Open
monfresh opened this Issue Jun 10, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@monfresh
Member

monfresh commented Jun 10, 2013

If someone flags an org's info as wrong, or submits an update, it should send an email to the organization (we have email addresses for most of them) so they can make the update (in case the flag requires an update), or approve/deny the submission.

Users must be signed in to flag or submit updates. If they are signed in with an email address whose domain matches the organization's, then we assume they are the moderator for that org, and therefore won't send them an email when they make an update themselves.

Just thinking out loud here on a potential solution to the moderation problem.

@anselmbradford

This comment has been minimized.

Show comment
Hide comment
@anselmbradford

anselmbradford Jun 12, 2013

Member

While I think this would be a great feature to have available, I think it would need to not be on by default. Sending unsolicited emails may not endear our platform to the recipient orgs and we'd also potentially be breaking anti-spam laws by sending emails to the addresses we have, as they are essentially harvested addresses for our system (none of the orgs "signed up" to be in our database).

For this kind of notification system to work I think it would need to:

** Be a setting a logged in organization moderator would need to turn on themselves.
** Only send an update when the information changed, e.g. if a field was flagged as wrong 10 times, only the first time would trigger an email. And when a moderator went in to see/approve/deny the edits, that's when the email notification for that field would reset.
** Have an opt-out URL in the notification email that turned off the notification when clicked.

What's your thoughts behind requiring a user sign in to flag/edit fields? I fear this would be a big barrier to contributing edits, particularly if clients were to become involved in keeping the info up-to-date (see Yelp, for instance, where you can submit edits without being signed in). Just to be sure we're talking about the same thing here, I was thinking something like:

** Anybody can flag/edit fields of data.
** Signed in user (moderator) is the only one that can apply the submitted edits to the actual data in the database.

In this scenario, another possible way of preventing emails being sent to an organization email when that organization is doing the edits is to have one master organization moderation account that is tied to the email on file. If that account is logged in and makes edits to their own records, no email notification is sent, even if their notification preference is turned on.

Member

anselmbradford commented Jun 12, 2013

While I think this would be a great feature to have available, I think it would need to not be on by default. Sending unsolicited emails may not endear our platform to the recipient orgs and we'd also potentially be breaking anti-spam laws by sending emails to the addresses we have, as they are essentially harvested addresses for our system (none of the orgs "signed up" to be in our database).

For this kind of notification system to work I think it would need to:

** Be a setting a logged in organization moderator would need to turn on themselves.
** Only send an update when the information changed, e.g. if a field was flagged as wrong 10 times, only the first time would trigger an email. And when a moderator went in to see/approve/deny the edits, that's when the email notification for that field would reset.
** Have an opt-out URL in the notification email that turned off the notification when clicked.

What's your thoughts behind requiring a user sign in to flag/edit fields? I fear this would be a big barrier to contributing edits, particularly if clients were to become involved in keeping the info up-to-date (see Yelp, for instance, where you can submit edits without being signed in). Just to be sure we're talking about the same thing here, I was thinking something like:

** Anybody can flag/edit fields of data.
** Signed in user (moderator) is the only one that can apply the submitted edits to the actual data in the database.

In this scenario, another possible way of preventing emails being sent to an organization email when that organization is doing the edits is to have one master organization moderation account that is tied to the email on file. If that account is logged in and makes edits to their own records, no email notification is sent, even if their notification preference is turned on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment