Changes between Version 30 and Version 31 of BluePrint/SaveSearch_Sub

Timestamp:

08/22/12 05:07:38 (13 years ago)

Author:

James O'Neill

Comment:

--

BluePrint/SaveSearch_Sub

@@ -13 +13 @@
 A single model for holding information about the search query and the parameters that are saved by the user. This will be in `/modules/eden/pr.py` as a component of `pr_entity`.
 
-==== Saved Search ====
  name::
   Name of the saved search as specified by the user.
@@ -28 +27 @@
  last_executed::
   The date and time the search was last executed by the subscription method. Set to match `modified_on` when record is first created.
-
-==== Public Saved Searches ====
- saved_search::
-  The saved search to make public.
- 
+ public::
+  Is this saved search viewable to everyone? This should trigger an authorisation process. Boolean, default is `False`.
 
 === Views ===
@@ -42 +38 @@
 Each person entity has a component for saved searches. This page will list all searches saved for this person entity, displaying the name of the search (as defined by the user when it was saved) and the query parameters.
 
-(The any/all option will require special extraction)
+Given the following search query string
 
-Query parameters will be displayed as human-readable definition lists, e.g.:
- Page::
-  Search Organisations (?)
- Search::
-  search strings
- Type::
-  Any of
-  * Red Cross / Red Crescent
- Sector::
-  Any of
-  * DRR
-  * Food Security
- Home Country::
-  Any of
-  * New Zealand
+{{{
+org_search_text_advanced=red+cross&org_search_type=3&org_search_sector_filter=any&org_search_sector=3&org_search_sector=2&org_search_home_country=NZ
+}}}
+
+The user should see
+
+{{{
+Search=red cross AND Type=Red Cross / Red Crescent AND Sector=DRR,Food Security AND Home Country=New Zealand
+}}}
+
+Any field that has no matching representation should be omitted.
 
 The user will have three options for each search record:
@@ -76 +68 @@
 1. Records with a `modified_on` value greater than `last_executed` are returned.
 1. `last_executed` field updated to when the request was made.
-1. If the pr_entity is a group, fetch the appropriate contact details from each member. Recursively?
 1. Format the response for special media, e.g., Twitter, SMS.
 
@@ -83 +74 @@
 * Implement representation functions for query string
 * Implement or update controllers
+  * `/msg/search_notifications/` to be called via cron, first argument is the frequency.
+  * Records with a `modified_on` value greater than `last_executed` are returned.
+* Expand `/msg/search_notifications/` to notify all people within a pr_group by fetching the relevant contact details from all members.
+* Add formatters/codecs to format the response for Twitter, SMS, etc.
 * Extend OAuth implementation for Twitter and Facebook to allow posting to users account.
 
@@ -89 +84 @@
 * Save a search after performing a search with filters.
 * Attempt to save a search with empty name; must fail.
+* Delete a saved search.
 * Edit and save a saved search.
 * Executing a search from the saved search list page.
-* Sending the notification email
+* Send notification email.