| | 1 | This is a project proposal for GSoC 2012. |
| | 2 | |
| | 3 | We need to parse inbound messages, with an initial focus being SMS. |
| | 4 | |
| | 5 | We can test this with [http://www.clickatell.com/pricing/us_small_business.php Clickatell] or a local phone (the Clickatell Inbound SMS fucntionality needs to be developed). |
| | 6 | |
| | 7 | Currently message parsing is done in the core code: [https://github.com/flavour/eden/blob/master/modules/s3/s3msg.py#L192 modules/s3/s3msg.py] |
| | 8 | |
| | 9 | We want to be able to make this a deployment-specific set of options. |
| | 10 | |
| | 11 | We are still working on developing our [https://groups.google.com/forum/?fromgroups#!topic/sahana-eden/Vy8xT4bA_pA Profile Layer] for having deployment-specific files separated from core code, so we can start by just making this a deployment-template like [https://github.com/flavour/eden/blob/master/deployment-templates/models/000_config.py 000_config.py] copying the file to {{{modules/s3/s3parsing.py}}} for easy import into S3MSG. |
| | 12 | |
| | 13 | If we need to have complex parsing, then we can make use of [wiki:pyparsing pyparsing] |
| | 14 | |
| | 15 | |
| | 16 | This will be used by at least [BluePrintCERT CERT] |
