wiki:Event/2012/GSoC/MessageParsing

Version 40 (modified by Ashwyn, 9 years ago) ( diff )

--

Message Parsing

Personal Details

Name: Ashwyn Sharma

Email: ashwyn1092@gmail.com

Freenode IRC Nickname: ashwyn

Skype: ashwyn sharma

Age: 19

Education: Currently pursuing B.E.(Bachelor in Engineering) from N.S.I.T, New Delhi.

Country: India

Timezone: GMT +0530

Github Branch: https://github.com/ashwyn/eden

Demo Branch

Demo Instance: http://msg-parser.demo.gsoc.sahanafoundation.org

Project Abstract

The 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.

Timeline

SMART Goal Measure Status
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
1.The msg_workflow data model is developed.
2.S3ParsingModel starts to take shape.
Code committed locally.Completed
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
1.API designed to link source-->workflow
2.Bug fixing in fetch_inbound_email()
3.parse_import() replaces process_log()
1.Code committed locally.
2.Tested on local system.
Completed
1.Scheduler logic moved to s3msg.py form zzz_1st_run.py.
2.deployment_setting.parser.parser_enabled defined.
Code committed to trunk.Completed
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
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 :-) ]
Completed
1.Demo Branch Released for mid-term code review.
2.Testing the IRS parsing routine.
Code committed locally.Completed
1.Securing the parser queries
2.Authentication of parser queries(Remote user login).
3.2-step Parser(Common code for parsers in s3parser.py)
Code committed to trunk.Completed.
1.Twilio functionality is developed for eden. Code committed locally.Completed.
1.Drafting Developer and User Guidelines.Project being documented.5th August
1.System testing & Bug fixing.
2.Final changes to the code are applied.
1.Project reaches final stage.
2.Bug fixes
3.Final Code committed to trunk.
13th August
PENCILS DOWNProject Completed. :-)20th August

Weekly Meeting

Fridays 13:00 UTC

Note: See TracWiki for help on using the wiki.