Changes between Version 56 and Version 57 of BluePrint/Messaging

Timestamp:

06/16/10 21:34:41 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Messaging

@@ -50 +50 @@
  * 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 {{{ticket_msg}}} table?
+   * 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: ''tbc''
+  * 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?
+  * 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 the {{{msg_delivery_status}}}, which is scanned by the Cron task for 'pending' messages to be sent out.
+  * 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