Logo

Subscription Scheduling

Last modified: 05/20/2006 07:46 AM
Revision: subscriptions_scheduling-draft.txt 30651 2005-12-14 22:15:41Z dkuhlman

Scheduling the notifications on daily, weekly or monthly basis.

1   Use case

  • While subscribing a user can specify how he would like to subscribe?
    • daily
    • weekly
    • monthly
  • And then he will receive the messages according to this configuration. Compilation of all the notifications related to the event he subscribed to during the time corresponding to the sort of notification.

2   Implementation

  • It has to be an external process that will ask for the notification category. (No available scheduler available within Zope). With crond, it will work just fine.
  • We need to maintain, within the portal_subscriptions, a scheduling table classified by categories / user / event subscribed. The categories correspond to the sort of subscriptions described above.
  • The mail content can be stored within the portal_subscriptions as simple objects containing the bodies of all notifications. A Btree will be storing the these objects.
  • The mapping, within a category, will contain an entry for the mail and then the references on the given mail body objects.
  • API which is call for a given category and then compile all the mail bodies that are referenced in the scheduling table and then sent that to the given users registered within the scheduling table.
This site is powered by CPS, which includes CPSSkins. CPS and its design are Copyright © 2002-2006 Nuxeo SAS.
CPSSkins is Copyright © 2003-2006 Jean-Marc Orliaguet.
powered_by_nuxeo.png