Jump to:

The program organizing committee often needs to send targeted email to the presenters of sessions, even those sessions not accepted for the program. It would be great to have a way to easily allow organizers to filter and send these messages to presenters.

One issue was that it was difficult to not send duplicate emails to presenters for the multiple sessions they may have submitted. Maybe it was just a matter of setting up the views correctly? Here are the types of communications necessary from the organizing committee viewpoint.

Accepted Sessions

Send email to each presenter of a session to confirm a session was accepted.

A presenter with multiple sessions accepted should get a confirmation email about each session accepted.

General communications to each presenter of a session as conference approaches.

Deferred Sessions

Send email to each presenter of a session that was not accepted.

Presenters with multiple sessions deferred should get a message about each session not accepted.

I think the conflict comes when you need to communicate with presenters about general news or information. In that case, you don't want to send duplicate messages for each session, as just one is enough. So I probably should have broke up the above scenarios into 3 categories:

Accepted Sessions

Send email to each presenter of a session to confirm a session was accepted.

A presenter with multiple sessions accepted should get a confirmation email about each session accepted.

Deferred Sessions

Send email to each presenter of a session that was not accepted.

Presenters with multiple sessions deferred should get a message about each session not accepted.

General Communications with Presenters

General communications to each presenter of a session as conference approaches.

We should be able to use the 'distinct' checkbox and require the "Presenters" relationship to control whether we send one email per presenter per session or just one email per presenter, and provide these as displays on a separate view linked from the main session moderation displays.

Since we'll already have controls for sending the message, I think we would want the presenter contact displays to not include filters from the session moderation Views.

So, I see us creating one display for each of mrshaver's scenarios in #2, plus an additional display for "session has been scheduled" in case organizers want to confirm that presenters can make their assigned session times.

I've built a feature based on the above, as well as a "presenter confirmation" flag that allows each presenter to confirm that she can present at the scheduled date and time. I'll be working on contributing this hopefully this week.

One thing I've noticed is that while the user's name is correct in the message, only the last name appears in the "to" part of the email. It seems like combining two fields into a single column isn't supported by views_send, so we should either stick with last name or use username instead.

Here's a revised version of this patch that switches from using full name to username for the email's "to" name. I haven't tested this as extensively as the previous patch but will do a quicker run through before committing, which I plan to do this week.

Here's a revised version of this patch that switches from using full name to username for the email's "to" name. I haven't tested this as extensively as the previous patch but will do a quicker run through before committing, which I plan to do this week.

Thank you for proposing the session session, "[views-send-node_title]".

We are happy to inform you that your session has been accepted for the conference.

Please confirm that you are able to present this session at the scheduled date and time by visiting [site-url]/user .

Thanks!

Conference organizing team"

Into the Message text box and continue with sending, the tokens are not being replaced- the following is what is received:

"Hello [views-send-users_node_data_field_speakers_profile_values_profile_first_value], Thank you for proposing the session session, "[views-send-node_title]". We are happy to inform you that your session has been accepted for the conference. Please confirm that you are able to present this session at the scheduled date and time by visiting [site-url]/user . Thanks! Conference organizing team"