Version 58 (modified by Fran Boon, 14 years ago) ( diff )


Blueprint for the Messaging Module

What we need is:

Core Architecture

Instead of having several "apps" that cross-talk, such as sms, email, tweet, jabber, etc, it would be good to have a central messaging core that has 'connectors'. This would be the equivalent of a star-hub structure.

This way, additional 'connectors' could be added or used as needed without refactoring the entire code base, and would allow sending messages from one connector to another, such as sms to email or email to jabber.

Need to have per-user inboxes (e.g. to support workflow)

Message Flows

  • When a message is picked up by the handler, it decides whether it's an XForm or not.
  • If it is, then it is routed direct to the relevant resource.
  • If not then it is added to the Master Message Log (msg_log)
  • When new messages arrive in the Master Message Log, then the Parser looks for keywords & tries to Route automatically - either to a resource or to a pe_pentity (NB 'routing' to a resource is actually just 'tagging').
  • Users can view the Master Message Log via the 'Ticketing Module' UI & do manual Routing - either to a resource or a pe_pentity.
  • Users can Subscribe to Resources in order to receive copies of all messages which are routed to a resource.
  • When a user visits a Resource via it's Web UI, then the RESTController scans the msg_log & provides access to associated messages in the views (display/update views have a list of associated messages in a table below the main record. list views have an extra column showing the number of messages tagged to this resource & number unread by this user (unread(read)) which is hyperlinked to a view which displays these records.
  • XML exports (such as RSS feeds) include tagged messages as linked resources.

Message Flows

How do we achieve this?

  • Table msg_log is used as a replacement for the current msg_inbox, msg_outbox & ticket_log.
    • Fields: sender, subject, body, verified, actionable, assignee (multiple?), actioned, priority
      • Q: Do we move some of these 'ticketing' fields to a separate, linked ticket_msg table?
  • Table msg_tag is used to tag messages for resources.
    • Fields: message_id, resource, record_uid
  • Table pe_subscription is used to maintain subscriptions for a pe_pentity.
    • Fields: pr_pe_id, resource, record_uid
  • Table msg_delivery_status is used to store delivery statuses.
    • Fields: message_id, pe_contact_id, status
  • Table msg_read_status is used to show that a message has been read by a user.
    • Fields: message_id, auth_user_id ('read' is assumed)
    • Q: Do we mark as read if pe_contact_id status suggests person has received message? (Fran thinks not)
    • Good to have UI to 'Mark Unread'
  • Parser has hooks for modules to plug-into?
  • Q: Do we treat a pentity the same way as any other resource?
    • Just that when a message is routed to them, it not only tags but also creates an entry in msg_delivery_status, which is scanned by the Cron task for 'pending' messages to be sent out.
  • shn_rest_controller() is modified to check msg_log for messages tagged to the resource (list) or record (display/update)
    • Views modified as above
  • 'Ticketing Module' UI
    • default view is all un-actioned messages (assigned to this user & unassigned?)
    • If a message is routed to a resource/pentity, this results in a 'create' form popup with as many fields auto-populated as possible (subject into 'name' field & body into 'comments' field, if nowhere better)
      • Q: If a message is routed to a resource, does this automatically mark ticket as 'actioned'? Provide a popup to ask this?

User Interface

The home page should be a common Inbox view which, by default, shows all new unread Items (the 'Ticketing Module').

Users/Groups should be able to subscribe to incoming messages of a certain type (Project / Location / Organisation) & have these messages forwarded via SMS / Email / Twitter / etc.

Ideally there should be the ability to launch a popup/ticker to notify of new items & a portlet which can be on a user's dashboard when they login.

The 'Send Message/Alert' screen should have a small box to enter the Plain-text message which is sent to all recipients (using all available SMS/Email addresses in the Group specified).

There should be a 2nd box to create a Rich-text message, with the option of adding attachments. This content just gets sent to those members of the group with an Email address specified.

We don't need the option of having Email or SMS groups - all groups are 'Both'.

If a user is added to a group we warn about any missing details, but still allow addition (the ref is by so addresses can eb added/changed later anyway).

When sending we need to provide warning messages about users for whom details weren't available.

Email has mail settings:

# These settings should be made configurable as part of the Messaging Module

& a function:

mail.send(to, subject='None', message='None')

Can use this to send emails with dynamic data inserted into templates (like HTML pages):

There is a Cron job to check the contents of the OutBox & send pending messages. On Success it moves the message to the 'Sent' table:

Rich Text

We'd like to be able to send HTML mails for rich-text support (including attachments) This requires the use of smtplib to send MIME-encoded files:


Need to be able to support both online gateways (such as Clickatell) & local hardware such as:

The SMS Daemon to handle Inbound messages is a separate Python script.

It can distinguish between simple messages (added to the InBox of the Messaging Module) & those which are encoded in Binary XML (the output of XForms from the J2ME client).

Implementation details are here:

Q: Do we use Cron to check OutBox & signal the daemon to send Pending messages? (as for email)

Toolkits we can base on:

Hardware compatibility databases:


Adding support for sending out/receiving alerts via Twitter would be nice.


Alternate implementations


Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.