Changes between Version 8 and Version 9 of BluePrint/Messaging/ExtendingParsing


Ignore:
Timestamp:
03/28/13 15:52:40 (8 years ago)
Author:
Ashwyn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Messaging/ExtendingParsing

    v8 v9  
    1414* Things that we want to extract and are essential requirements for the framework are discussed below.
    1515
    16 === Reliability/trustworthiness of the message sources/senders ===
     16=== Input Source Improvements ===
    1717
    18                   * Currently, this is done manually through the CRUD interface with the msg_sender data model. However , implementing a UI which prioritises message parsing for starred senders is also really useful.
     18== Reliability/trustworthiness of the message sources/senders ==
     19
     20                  * Currently, this is done manually through the CRUD interface with the msg_sender data model.
    1921             
    2022                  * A 'river' of messages are processed with starring of senders & adding of keywords on the fly so that the system gradually becomes more automated through the process.
    21 
    22                   * Keywords can be added to the database (msg_keyword) manually through this UI which can both help ''star'' and ''mark'' keywords.
    2323
    2424                  * We could as well pre-populate the keywords database with the most frequently used keywords (esp. in incident reporting) and the rest can be added on the fly.
    2525
    2626     
     27=== Parser Improvements ===
    2728
    28 === Actionability ===
     29== Actionability ==
    2930
    3031                  * Is this something that we can actually do something with?
     
    3637                  * 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).
    3738
     39=== UI Improvements ===
    3840
    39 === Parsing bounced messages ===
     41                  *Implementing a UI which prioritises message parsing for starred senders is a useful requirement.
     42                  *The user should be able to *star* senders and *mark* keywords through the UI.
     43
     44=== Use Cases ===
     45
     46== Parsing bounced messages ==
    4047
    4148                  * This is very important for IFRC Africa who send out bulk emails to their volunteer base from Eden & want to know which mails are
    42                    mis-typed / users moved / etc
     49                   mis-typed / users moved / etc.
     50                 
     51== Situational Awareness Dashboard ==
     52
     53                  *Trying to present a single,simplified view for many disparate information sources including RSS feeds.