Changes between Version 58 and Version 59 of Event/2012/GSoC/MessageParsing
- Timestamp:
- 06/05/13 15:37:31 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Event/2012/GSoC/MessageParsing
v58 v59 23 23 24 24 == Demo Branch == 25 Demo Instance: http://msg-parser.demo.gsoc.sahanafoundation.org 25 26 26 Demo Instance: http://msg-parser.demo.gsoc.sahanafoundation.org27 27 == Project Abstract == 28 28 29 29 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. 30 30 31 32 33 31 == Timeline == 34 35 32 36 33 ||= SMART Goal =||= Measure =||= Status =|| … … 48 45 ||1.OpenGeoSMS Parser for Incident Reports.\\ 2. 2-Step Refactoring for parsers. ||Code committed to Trunk.||Completed.|| 49 46 ||1.System testing & Bug fixing.\\ 2.Final changes to the code are applied.\\3.Drafting Developer and User Guidelines.||Project Completed. :-)||Completed.|| 47 50 48 == Weekly Meeting == 51 52 49 Fridays 13:00 UTC 53 50 51 == Future Options == 52 * Help menu parser for available commands. 53 * Look-up for existing locations in the DB for OpenGeoSMS Parser. 54 * CKEditor Integration for viewing the parser codes. 55 * Dedicated Outbound support for Twilio. 54 56 55 == Future Options == 56 1.Help menu parser for available commands.\\ 57 2.Look-up for existing locations in the DB for OpenGeoSMS Parser.\\ 58 3.CKEditor Integration for viewing the parser codes.\\ 59 4.Dedicated Outbound support for Twilio. \\ 57 == User Guidelines == 58 * UserGuidelines/Messaging/Parsing 59 * wiki:Event/2012/GSoC/MessageParsing/DemoGuidelines 60 60 61 == Project Guidelines ==62 63 64 *wiki:MessageParsingUserGuidelines \\65 *wiki:MessageParsingDemoGuidelines \\66
