Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. One email per course evaluation method - configurable interval per evaluation with one reminder sent per course evaluation per user and the email template is configurable per evaluation, includes direct link to the evaluation, after taking the evaluation the user is directed to the main page which lists all current evaluations
    • num of emails = num of assigned courses * num of evalaution * num of takers
    • (this is the method we are currently using)
  2. Landing page method - one email per user taking any evaluation (and per global reminder period) which directs the user to a landing page (main summary page) which includes a list of all their current evaluations, email is generic and uses a global template with no direct links
    • num of emails = num of takers
    • (this has the advantage of being pretty simple to code and execute with the only tricky bit being how to handle the case where an individual evaluation has a shorter reminder interval than the system interval)
  3. Fully aggregated email method - Aggregate all reminders into a single email which includes the list of all current evaluations for the user, this would be one email per user per global reminder period, the template would be a global template and individual evaluation templates would not be supported
    • num of emails = num of takers
    • (this is the most complicated to develop of the 4 options)
  4. One email per evaluation - one email per evaluation per user which lists a set of all course/groups for that evaluation and includes a direct link for each course evaluation, email template is configurable per evaluation and reminder interval is configured for each evaluation
    • num of emails = num of evaluation * num of takers
    • (this is the easiest one to develop of the non-current methods)
  5. Wiki Markup*Michigan method* \ - one email per \ [email template of\] student having one or more evaluations for which no response has been submitted. E.g., if a student has seven active evaluations that use two email templates, send two emails to that student. Email includes 1) a direct link to the summary page of the student's My Workspace site tool placement, and 2) the earliest due date among the active evaluations for which the student has not submitted a response. Earliest due date appears in the subject and body of available and reminder notifications. There are available and reminder consolidated-email \ [changing "consolidated" to "single email"\] templates. Global reminder period is expressed in number of days.
    • num of emails = num of students with at least one evaluation response that hasn't been submitted * number of email templates used for those evaluations
    • sets of evaluations using the same email template will be handled as part of the data import, creating email templates required and then setting email template ids when evaluations are saved.
    • exception handling in which an email template has to change will also be handled as part of the data import
    • this is relatively simple as it was implemented, a Quartz cron job firing once daily under the Job Scheduler
    • the ScheduledInvocationManager continues to manage evaluation state changes through the SCHEDULER_DELAYED_INVOCATION table, but email is handled by this cron job
    • Overlapping sets of evaluations (e.g., Pharmacy and seven-week courses might have overlapping evaluation dates) are not tagged or differentiated in terms of email templates
    • Email settings were added to sakai.properties and set as part of the build process based on target server, for safer email testing (options of "no email", "log email", "send email"), to limit by throttling the impact of email processing in production, and as a check to log email recipients. These settings would move to the administrate page, and appropriate values would be pre-loaded. The email notification settings were:
      • waitInterval@org.sakaiproject.evaluation.logic.EvalNotificationSettings
      • batchSize@org.sakaiproject.evaluation.logic.EvalNotificationSettings
      • logRecipents@org.sakaiproject.evaluation.logic.EvalNotificationSettings
      • deliveryOption@org.sakaiproject.evaluation.logic.EvalNotificationSettings
    • Performance required to fit in the maintenance window this fall after increasing courses 6-10x relative to pilots is a current subject of attention.

...