Changes between Version 30 and Version 31 of group_email


Ignore:
Timestamp:
2011-08-04T18:15:27Z (13 years ago)
Author:
Taehyun You
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • group_email

    v30 v31  
    1313
    1414Optional:
    15 * User can use and edit his/her own email template
    16  * Ownership such as private, public, or shared among some group
    17 * Email merge system, so template can have fields for variables
    18 * Allowing a user to see and copy group email addresses, so he/she can use a preferred email client
    19 
     15* Email Template: User can make and use his/her own email template
     16 * Has ownership such as private, public, or shared among some group
     17* Email merge: User can make a merge field such as name, email, or etc which are automatically filled when the mail is sent
     18* Get Email Addresses: User can get email addresses of group and use copied email addresses with preferred email client.
    2019
    2120== Implementation ==
    2221=== Recipients ===
    23 * Recipients are depending on which link user clicked (from course, group, or user page)
    24 * Can add additional recipients by doing similar way of adding instructors to a course.
     22* Recipients list in "To" field will be:
     23 * Students registered in a course if user click "Email to All Students" on Course homepage
     24 * Group members in a group if user click "Email to All Members" on Group view page
     25 * Student if user click Email Icon next to student name on Group view or User index page. 
     26* Can add/remove additional recipients by doing similar way of adding instructors to a course.
     27* Not allowing manually typed email address to prevent errors with Email merge system.
    2528
    26 === Templates ===
    27 * User can add/edit/delete/view own template
     29=== Email Templates ===
     30* User can add/edit/delete/view own email templates
    2831* Can add merge fields on a template.
    2932
    3033=== schedules ===
    3134* Single/multiple schedule on email is possible.
     35 * Multiple schedule needs a number of times to send and interval(day(s), hour(s), or minute(s))
    3236* Default schedule is current datetime.
    33 * All emails goes to database then send() function will send emails that meet requierments
    34 * User can track emails
     37* User can view emails and cancel if email is not sent yet.
     38* For better performance in user's view, all emails go to Email Schedule Database, then server will send emails that are ready by cron job.
    3539
    3640