| 22 | | === Current System === |
| 23 | | For ease of getting a large dataset to play with, we will use Twitter for this example, although the same system can be used for other message channels, like Email, SMS & RSS. |
| 24 | | |
| 25 | | Test Server to see User Interface: |
| 26 | | * http://demo.eden.sahanafoundation.org/eden/msg/ |
| 27 | | |
| 28 | | Install on your own system: |
| 29 | | * Install Eden |
| 30 | | * Install the [https://pypi.python.org/pypi/TwitterSearch/ TwitterSearch] library |
| 31 | | * Follow the [UserGuidelines/Messaging#TwitterSearch User Guidelines] to get a Twitter OAuth account & use this to search |
| 32 | | |
| 33 | | Relevant documentation: |
| 34 | | * DeveloperGuidelines/Messaging |
| 35 | | * DeveloperGuidelines/Messaging/Channels |
| 36 | | |
| 37 | | Note: Documentation for both end-users & devs could use improvement |
| 38 | | * feel free to dive in! |
| 39 | | |
| 40 | | === Projects === |
| 41 | | There are 2 projects that we can work on during this session: |
| 42 | | (A) Some simple enhancements to the current interface |
| 43 | | (B) Creating a 'Human Intelligence Tasking' module to allow the processing of these messages to be divided up amongst a lot of workers |
| 44 | | |
| 45 | | ==== Enhancements ==== |
| 46 | | |
| 47 | | ===== Simple ===== |
| 48 | | The current workflow for a user to search Twitter is very cumbersome! |
| 49 | | |
| 50 | | Some ideas for improvements (although feel free to come up with your own!) |
| 51 | | * There should be an option (on by default) to have the Search run after save |
| 52 | | * The next screen should be the Results: {{{s3db.configure(create_next = URL(f="twitter_result"))}}} |
| 53 | | * There should be some filters above the results: |
| 54 | | * http://eden.sahanafoundation.org/wiki/S3/FilterForms |
| 55 | | * There should be a link to see the results on a Map |
| 56 | | * this will require modifying the code to have the msg_twitter_result table use self.gis_location_id() Foreign key instead of !lat/lon fields |
| 57 | | * The S3Map() method is then automatically accessible via /eden/msg/twitter_result/map |
| 58 | | * This will use the same filters defined for the list view |
| 59 | | * There should be a Report method configured for charts based on pivot tables |
| 60 | | * http://eden.sahanafoundation.org/wiki/S3/S3Report |
| 61 | | * We could create a 'Summary' view which allows the Table, Chart & Map to be separate tabs on a single page, sharing a common set of filters, keeping the settings when moving between the views |
| 62 | | * Example: http://demo.lacrmt.sahanafoundation.org/eden/vulnerability/risk/summary |
| 63 | | * This is accessible via /eden/msg/twitter_result/summary |
| 64 | | * The Chart, Table, Filter, map settings are inherited |
| 65 | | * The configuration of which Tabs to display can be seen in the CRMT template |
| 66 | | * https://github.com/flavour/eden/blob/master/private/templates/CRMT/config.py#L235 |
| 67 | | * Can see this locally by switching to the CRMT template: {{{settings.base.template = "CRMT"}}} in {{{models/000_config.py}}} & doing a fresh [DeveloperGuidelines/PrePopulate prepopulate] |
| 68 | | |
| 69 | | ===== Advanced ===== |
| 70 | | * Run [DeveloperGuidelines/Messaging/Parser Parsers] on the list |
| 71 | | * Train these parsers |
| 72 | | * We want to add tools to the Table view to Geocode, Classify, Whitelist sender, Blacklist sender |
| 73 | | * This has overlap witht he HIT module approach |
| 74 | | * Timeline Report? |
| 75 | | * We have this integrated already: http://www.simile-widgets.org/timeline/ |
| 76 | | * Can see this locally by switching to the IFRC template: {{{settings.base.template = "IFRC"}}} in {{{models/000_config.py}}}, doing a fresh [DeveloperGuidelines/PrePopulate prepopulate] & then looking at /eden/irs/ireport/timeline |
| 77 | | * Work on [https://github.com/ashwyn/KeyGraph KeyGraph] visualisation? |
| 78 | | |
| 79 | | ==== HIT Module ==== |
