Is your feature request related to a problem? Please describe.
Historically, a mass notification email has been sent out letting all PIs/managers of “Active” PCAs/FCAs know that renewals for next year are ready. This all occurs manually and the emails are not tailored for the project in question. This request proposes that the process becomes automated (though it can be initiated manually) and that each email is tailored for its respective project.
Describe the solution you'd like
My initial plan is to use django-q to trigger a send_renewal_emails function yearly (placeholder naming for now). In the send_renewal_emails function, the projects are split into blocks so that emails are staggered out. Inside each block, tailor an email for each project individually and send each using async_task from django-q.
Additional context
- Given the usage limits on the new Google Forms renewal survey process, the emails should be staggered rather than sent all at once.
Is your feature request related to a problem? Please describe.
Historically, a mass notification email has been sent out letting all PIs/managers of “Active” PCAs/FCAs know that renewals for next year are ready. This all occurs manually and the emails are not tailored for the project in question. This request proposes that the process becomes automated (though it can be initiated manually) and that each email is tailored for its respective project.
Describe the solution you'd like
My initial plan is to use
django-qto trigger asend_renewal_emailsfunction yearly (placeholder naming for now). In thesend_renewal_emailsfunction, the projects are split into blocks so that emails are staggered out. Inside each block, tailor an email for each project individually and send each using async_task fromdjango-q.Additional context