Automated email response at time of registration on DigiVol

[atlasoflivingaustralia]

Automated email response at time of registration on DigiVol

[davidbairdala]

@djtfmartin Mailchimp has a web api that allows for subscribing users to lists etc. The question is how tightly to we want to couple the BVP with MailChimp - does the Atlas already have a email campaign platform, or would we consider using MailChimp generally. Should there be an abstraction over MailChimp, or should BVP just deal with it directly.

@snomelf Do you already have a mail chimp account? I don't suppose it would be enough to have the BVP send you an email when someone joins, and you manage their subscription to a list via mail chimp manually?

Just FYI - BVP isn't alerted when someone registers with the Atlas, and the Atlas doesn't know if someone is registering for the purpose of using the BVP. But we can tell if a registered user is coming to the site for the first time, although you might want to consider if you want to send a welcome pack to everyone who visits the site for the first time - should there be some other criteria to select who should get a welcome pack? First transcription? First view of a task?

[djtfmartin]

I think this sounds like an extension to the alerts webapp.
When new users are created in the Atlas we already subscribe them to blogs
etc.

The alerts service supports emails when new records are added. We could do
something similar for expeditions too with minimal code changes.

On Tue, Aug 19, 2014 at 10:34 AM, David Baird [email protected]
wrote:

@djtfmartin https://github.com/djtfmartin Mailchimp has a web api that
allows for subscribing users to lists etc. The question is how tightly to
we want to couple the BVP with MailChimp - does the Atlas already have a
email campaign platform, or would we consider using MailChimp generally.
Should there be an abstraction over MailChimp, or should BVP just deal with
it directly.

@snomelf https://github.com/snomelf Do you already have a mail chimp
account? I don't suppose it would be enough to have the BVP send you an
email when someone joins, and you manage their subscription to a list via
mail chimp manually?

Just FYI - BVP isn't alerted when someone registers with the Atlas, and
the Atlas doesn't know if someone is registering for the purpose of using
the BVP. But we can tell if a registered user is coming to the site for the
first time, although you might want to consider if you want to send a
welcome pack to everyone who visits the site for the first time - should
there be some other criteria to select who should get a welcome pack? First
transcription? First view of a task?

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

[snomelf]

Welcome back Dave M - hope you had a good holiday!

Hmmm ok so i want to email people that have registered with the intent of
looking at DigiVol (notice im trying to refer to it as its future name :-))
regardless of whether they transcribe because maybe they find it all too
daunting so they dont transcribe - so the welcome pack is to try and get
them over the line. But its also to try and get them to feel like they are
entering something that has interaction - so pointing out the Forum and
honour boards etc.

I have an account for MailChimp yes and currently I use it to send all
users emails. Unfortunately each time i send one its a pain in the ass to
update the list of DigiVol users as I have to download the user report,
import to Excel, filter for last date that I updated the email list, import
into MailChimp etc - you get the drift. So YES an email each time someone
registered (and visited the site for the first time) would help (and if
thats the best you can do for now then yes ill take that) but ideally i
would prefer that the MailChimp email list was updated automatically.

On 19 August 2014 10:42, Dave Martin [email protected] wrote:

I think this sounds like an extension to the alerts webapp.
When new users are created in the Atlas we already subscribe them to blogs
etc.

The alerts service supports emails when new records are added. We could do
something similar for expeditions too with minimal code changes.

On Tue, Aug 19, 2014 at 10:34 AM, David Baird [email protected]
wrote:

@djtfmartin https://github.com/djtfmartin Mailchimp has a web api
that
allows for subscribing users to lists etc. The question is how tightly
to
we want to couple the BVP with MailChimp - does the Atlas already have a
email campaign platform, or would we consider using MailChimp generally.
Should there be an abstraction over MailChimp, or should BVP just deal
with
it directly.

@snomelf https://github.com/snomelf Do you already have a mail chimp
account? I don't suppose it would be enough to have the BVP send you an
email when someone joins, and you manage their subscription to a list
via
mail chimp manually?

Just FYI - BVP isn't alerted when someone registers with the Atlas, and
the Atlas doesn't know if someone is registering for the purpose of
using
the BVP. But we can tell if a registered user is coming to the site for
the
first time, although you might want to consider if you want to send a
welcome pack to everyone who visits the site for the first time - should
there be some other criteria to select who should get a welcome pack?
First
transcription? First view of a task?

—
Reply to this email directly or view it on GitHub
<
https://github.com/AtlasOfLivingAustralia/volunteer-portal/issues/21#issuecomment-52575966>

.

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

[davidbairdala]

Users with the role 'site_admin' will be notified by email when the BVP creates/registers a new user. This is a separate step from Atlas registration that only occurs when a new user views a task for the first time, or views their stats.