Changes between Version 42 and Version 43 of BluePrint/Sunflower

Timestamp:

08/11/14 20:48:00 (11 years ago)

Author:

somayjain

Comment:

--

BluePrint/Sunflower

@@ -85 +85 @@
 
 * A person who is subscribed to a task/project/organisation/etc receives notifications via email about it.
+* A person on commenting on a task is automatically subscribed to the comments feed of that task.
 * The updates can be for new records or updates in the records.
 * The frequency of the updates can be 
@@ -121 +122 @@
 * Make it simpler to log bugs 
  * http://eden.sahanafoundation.org/ticket/1307 
- * Less fields  / progressibely show fields (easier to log for people)
+ * Less fields  / progressively show fields (easier to log for people)
  * No login required - but allow user to specify who’s login it in a field 
  * Add a default link to log a bug in Sunflower - which copies the current URL to the “Source” field 
@@ -277 +278 @@
   * Use summary pages and datalists for each module mentioned above.
 
-==== Subscriptions ====
-
-The newsfeed is generated using S3Audit (check CRMT template for reference - https://github.com/flavour/eden/blob/master/private/templates/CRMT/config.py#L113
-===== Onclick =====
+== Future Extensions ==
+
+=== Subscriptions ===
+
+* On a "create"/"update"/"delete" event of a record from any of the table (for eg - {{{project_project}}}, {{{project_task}}}), an audit can be created (check CRMT template for reference - https://github.com/flavour/eden/blob/master/private/templates/CRMT/config.py#L113).
+* When this audit is created, a newsfeed item could be generated having - 
+ * Title (Eg - Task Updated/Task Created/ Project Updated...)
+ * Type - Can be the tablename (Eg - project_task/project_project)
+ * Value - Can contain key:value pairs separated by a delimiter such as "name:new task;project_task_project.id:1;status:2". The keys can be database fields and link tablename's fieldname for embedded inline components.
+ * Author - user_id of the person who made the change
+* The newsfeed can be created using the {{{cms_post}}} table, or a new table (if necessary).
+
+* This newsfeed can be made filterable according to the key:value pairs. Eg - All tasks under the project "Sunflower" whose Author is "Bob".
+* The newsfeed can be linked to subscriptions using {{{pr_subscription_resource}}} with a {{{pr_filter}}} on the newsfeed resource.
+
+==== Onclick ====
 
 * Using just a "click" to subscribe to an item. Eg- "Subscribe/Unsubscribe to Project", "Subscribe/Unsubscribe to task" action buttons on project/task.
@@ -286 +299 @@
 * The user can also subscribe to the individual item by clicking on "Subscribe/Unsubscribe" button on the newsfeed item.
 
-===== Hand crafted filters =====
+==== Hand crafted filters ====
 
 * Hand crafted subscription filter and subscription settings for the newsfeed - The user can set the subscription filter manually. Eg - Selecting All tasks for project X, Updates on Org Y, etc.
@@ -293 +306 @@
  * Mode - Email/No Email
 
-== Future Extensions ==
-
-* Metrics - Making the metrics being automatically updated
+==== Possible Extensions ====
+
+* Having the above design allows as to provide subscription for any feed which can be converted in (title, type, value, author) format.
+* Eg - Having incoming feeds converted to such format.
+
+=== Metrics ===
+* Making the metrics being automatically updated
  * Emails links on the list.
  * Trunk commits URLs
@@ -302 +319 @@
  * Links of wiki pages edited.
 
-* Diff viewer - 
- * Include a diff viewer on the task page to display the patch(if any) added as an attachment.
- * The viewer should be able to support inline comments, preferably like Github viewer does.
+=== Diff Viewer ===
+* Include a diff viewer on the task page to display the patch(if any) added as an attachment.
+* The viewer should be able to support inline comments, preferably like Github viewer does.
+
 == References ==
 * [wiki:S3/Notifications Subscriptions and Notifications]