Changes between Version 28 and Version 29 of Event/2012/GSoC/MessageParsing


Ignore:
Timestamp:
06/28/12 19:08:03 (9 years ago)
Author:
Ashwyn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2012/GSoC/MessageParsing

    v28 v29  
    1 === Message Parsing ===
     1== Message Parsing ==
    22[[TOC]]
    33
    4 === Personal Details ===
     4== Personal Details ==
    55 
    66Name:  Ashwyn Sharma
     
    2222Github Branch: [https://github.com/ashwyn/eden]
    2323 
    24 === Project Abstract ===
     24== Project Abstract ==
    2525
    2626The essential requirement for this project is to parse inbound messages, with an initial focus to SMS. The project is specifically aimed at the CERT usecase where they wish to process responses to deployment notifications. Or in other words, to handle replies to deployment requests. Currently the message parsing is done in the core code i.e. modules/s3/s3msg.py, to be particular, in the parse_message() method. The parsing rules will be defined in private/templates/default/parser.py which allows for hosting of multiple profile options in the main code.  This also enforces the on-going work in the development of the Profile Layer, in which deployment-specific files are separated from core code.The parsing module utilizes a data model "msg_workflow”  to link the source and the workflow to schedule tasks. Processing of OpenGeoSMS encoded messages is also an important area to work on especially for the existing Android Client, for which it will be of real use. Also to provide robustness and extend the existing code, the pyparsing Parser module can be incorporated or any other parsing generator; which will be subjective to the parsing needs.
     
    2828
    2929
    30 === Timeline ===
     30===Timeline ==
    3131First Trimester:
    3232
     
    3434||(24th April  - 7th May)||1.Design of the workflow handling mechanism.\\ 2.process_log() method is defined.\\3.Tweaks in msg_log datamodel.||1.Community bonding period.\\2.Decision to outline the template.||Completed||
    3535||(8th May – 21st May)||1.The msg_workflow data model is developed.\\ 2.S3ParsingModel starts to take shape.||Code committed locally.||Completed||
    36 
    37 Second Trimester:
    38 
    39 ||= Due Date =||= SMART Goal =||= Measure =||= Status =||
    4036||28th May  -*(won’t be available due to university exams )|| || || ||
    4137||4th June||1.Parsing Rules moved to private/templates/default/parser.py.\\ 2.Scheduler logic for parsing workflows is developed.||SMS response processing starts to take shape.||Completed||
     
    4440||2nd July||1.Message Parsing UI designed.\\ 2.UI for Email settings.\\3.deployment_setting.parser.template defined and parser_enabled removed.\\4.Data model msg_workflow redefined.||Code committed to trunk.||Completed||
    4541||8th  July||1.Integration of the IRS module for incident reporting through SMS.||1.Commits so far tested thoroughly.\\2.Bug fixing.\\ 3.Code committed to trunk.[Mid-Term evaluations :-) ] ||In Progress||
    46  
    47  
    48 Third Trimester:
    49 
    50 ||= Due Date =||= SMART Goal =||= Measure =||
    5142||15th July||1.Integration with templates folders.\\2.Development of post-install UI (CRUD interface admin panel).||Code committed locally.||
    5243||22nd July||1.Routing mechanism to resources.\\ 2.Save search and subscription implemented for msg_log.||Code committed to trunk.||
     
    5647||20th August||PENCILS DOWN||Project Completed. :-)||
    5748
    58 === Weekly Meeting ===
     49== Weekly Meeting ==
    5950
    6051Fridays 13:00 UTC