Changes between Version 9 and Version 10 of BluePrint/Messaging/ExtendingParsing
- Timestamp:
- 03/28/13 15:54:35 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Messaging/ExtendingParsing
v9 v10 14 14 * Things that we want to extract and are essential requirements for the framework are discussed below. 15 15 16 == = Input Source Improvements ===16 == Input Source Improvements == 17 17 18 == Reliability/trustworthiness of the message sources/senders==18 === Reliability/trustworthiness of the message sources/senders === 19 19 20 20 * Currently, this is done manually through the CRUD interface with the msg_sender data model. … … 25 25 26 26 27 == = Parser Improvements ===27 == Parser Improvements == 28 28 29 == Actionability==29 === Actionability === 30 30 31 31 * Is this something that we can actually do something with? … … 37 37 * An OpenGeoSMS parser already exists in the default parser template(also available as an API within s3msg.py) which is able to parse lat-lon information of the location from OpenGeoSMS formatted messages. But , it would be great if it could be linked with the database (look the location up from the database). 38 38 39 == = UI Improvements ===39 == UI Improvements == 40 40 41 41 *Implementing a UI which prioritises message parsing for starred senders is a useful requirement. 42 42 *The user should be able to *star* senders and *mark* keywords through the UI. 43 43 44 == = Use Cases ===44 == Use Cases == 45 45 46 46 == Parsing bounced messages == … … 49 49 mis-typed / users moved / etc. 50 50 51 == Situational Awareness Dashboard==51 === Situational Awareness Dashboard === 52 52 53 * Trying to present a single,simplified view for many disparate information sources including RSS feeds.53 * Trying to present a single,simplified view for many disparate information sources including RSS feeds.
