ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/app/messages/alert.email.erb

31 lines
1.5 KiB
Plaintext
Raw Normal View History

alerts, closes #4317 * Daily job to evaluate alerts * Spawns a new job for each root account (for parallelization). It could be broken down to per-course level if needed (i.e. if there is a *huge* root account). * Evaluating criteria at a course level using efficient queries. * UI for CRUD on alerts * Render existing alerts * Delete existing alerts * Create a new alert * CRUD for criteria, recipients, repetition * Validations * Improve instructure_helper's formErrors to support passing errors for specific elements * Improve Rails' :include to be able to :exclude an :include inherited from a named scope * Specs!! * Note that we want to slowly roll this out, so there is a setting on root accounts to enable it So I ran an alert with just an interaction criterion on a test cluster against 50,000 courses, and it took less than 10 minutes without any parallelization. That seems like acceptable performance to me (since there are only just over 3000 courses in production that would even be elligible to have alerts sent right now). Of course, that's probably skewed because I'm sure a bunch of those 50,000 courses were essentially empty. Change-Id: Ie028ef206c9155b9a72fb2a820f3e0e516de562a Reviewed-on: https://gerrit.instructure.com/4799 Reviewed-by: Jon Jensen <jon@instructure.com> Tested-by: Hudson <hudson@instructure.com>
2011-07-26 00:12:55 +08:00
<% define_content :link do %>
<%= polymorphic_url asset_context.course %>
<% end %>
<% define_content :subject do %>
<%= t('subject', 'Alert: %{user_name}', :user_name => asset_context.user.name) %>
<% end %>
<%=
if asset_context.user_id == user.id
t('body_student', {:one => "An alert has been triggered for you because the following condition has been met:", :other => "An alert has been triggered for you because the following conditions have been met:"}, :count => asset.criteria.length)
else
t('body', {:one => "An alert has been triggered for %{student} because the following condition has been met:", :other => "An alert has been triggered for %{student} because the following conditions have been met:"}, :count => asset.criteria.length, :student => asset_context.user.name)
end
%>
<% asset.criteria.each do |criterion| %>
<%=
case criterion.criterion_type
when 'Interaction'
t('interaction_description', 'No student/teacher interaction for %{count} days', :count => criterion.threshold)
when 'UngradedCount'
add missing description for ungraded timespan alerts, refs #4317 Change-Id: Ifd9e1bddb2f8d4b93f21d8f5e5d40f5a41563525 Reviewed-on: https://gerrit.instructure.com/7335 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Brian Whitmer <brian@instructure.com>
2011-12-08 02:15:54 +08:00
t('ungraded_count_description', '%{count} or more submissions have not been graded', :count => criterion.threshold)
when 'UngradedTimespan'
t('ungraded_timespan_description', 'A submission has been left ungraded for %{count} days', :count => criterion.threshold)
alerts, closes #4317 * Daily job to evaluate alerts * Spawns a new job for each root account (for parallelization). It could be broken down to per-course level if needed (i.e. if there is a *huge* root account). * Evaluating criteria at a course level using efficient queries. * UI for CRUD on alerts * Render existing alerts * Delete existing alerts * Create a new alert * CRUD for criteria, recipients, repetition * Validations * Improve instructure_helper's formErrors to support passing errors for specific elements * Improve Rails' :include to be able to :exclude an :include inherited from a named scope * Specs!! * Note that we want to slowly roll this out, so there is a setting on root accounts to enable it So I ran an alert with just an interaction criterion on a test cluster against 50,000 courses, and it took less than 10 minutes without any parallelization. That seems like acceptable performance to me (since there are only just over 3000 courses in production that would even be elligible to have alerts sent right now). Of course, that's probably skewed because I'm sure a bunch of those 50,000 courses were essentially empty. Change-Id: Ie028ef206c9155b9a72fb2a820f3e0e516de562a Reviewed-on: https://gerrit.instructure.com/4799 Reviewed-by: Jon Jensen <jon@instructure.com> Tested-by: Hudson <hudson@instructure.com>
2011-07-26 00:12:55 +08:00
when 'UserNote'
t('usernote_description', 'No faculty journal entries for %{count} days', :count => criterion.threshold)
end
%>
<% end %>
<%= content :link %>