This is a proposal to enhance django-notification with the ability to generate email digests (i.e. taking a repeated Notice and grouping that into one mail message over a system-wide period of time).
1. NoticeType.digest would be a new boolean field to enable/disable whether that NoticeType is part of a digest. This enables counters and other functionality to be used during post processing (i.e. we don't know how many notices there are per user/NoticeType until the send() method is called). 2. A last_sent DateTimeField will be attached to NoticeSetting so that for each NoticeType/user combination, we can determine when the last_sent datetime was. This will be updated on non-digest emails for consistency. 3. An arbitrary digest period that is based on the NoticeType. I've implemented 1 and 2 and am ready to implement 3 at: http://github.com/AdamN/django-notification One major change that I made that people may not like is that I got rid of pickling of queued notifications. I found the pickled data unworkable. In addition, I also use annotate() which requires Django 1.1. I know these changes may make this fork impossible to push back to Pinax but I had to do it for my own project. Thanks, Adam -- You received this message because you are subscribed to the Google Groups "Pinax Core Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pinax-core-dev?hl=en.
