22 | | == Project breakdown == |
| 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 | ==== Simple Enhancements ==== |
| 46 | The current workflow for a user to search Twitter is very cumbersome! |
| 47 | |
| 48 | Some ideas for improvements (although feel free to come up with your own!) |
| 49 | * There should be an option (on by default) to have the Search run after save |
| 50 | * The next screen should be the Results: {{{s3db.configure(create_next = URL(f="twitter_result"))}}} |
| 51 | * There should be some filters above the results: |
| 52 | * http://eden.sahanafoundation.org/wiki/S3/FilterForms |
| 53 | * There should be a link to see the results on a Map |
| 54 | * 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 |
| 55 | * The S3Map() method is then automatically accessible via /eden/msg/twitter_result/map |
| 56 | * This will use the same filters defined for the list view |
| 57 | * There should be a Report method configured for charts based on pivot tables |
| 58 | * http://eden.sahanafoundation.org/wiki/S3/S3Report |
| 59 | * 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 |
| 60 | * Example: http://demo.lacrmt.sahanafoundation.org/eden/vulnerability/risk/summary |
| 61 | * This is accessible via /eden/msg/twitter_result/summary |
| 62 | * The Chart, Table, Filter, map settings are inherited |
| 63 | * The configuration of which Tabs to display can be seen in the CRMT template |
| 64 | * https://github.com/flavour/eden/blob/master/private/templates/CRMT/config.py#L235 |
| 65 | * We want to add tools to the Table view to Geocode, Classify, Whitelist sender, Blacklist sender |
| 66 | |
| 67 | ==== HIT Module ==== |
| 68 | ===== Project breakdown ===== |
65 | | Relevant documentation: |
66 | | * UserGuidelines/Messaging (very much in need of clarification and concrete examples) |
67 | | * DeveloperGuidelines/Messaging |
68 | | * DeveloperGuidelines/Messaging/Channels |
69 | | |
70 | | User interface: |
71 | | http://demo.eden.sahanafoundation.org/eden/msg/ |
72 | | |
73 | | In summary: |
74 | | * Install the [https://pypi.python.org/pypi/TwitterSearch/ TwitterSearch] library |
75 | | * Follow the [UserGuidelines/Messaging#TwitterSearch User Guidelines] to get a Twitter OAuth account & use this to search |
76 | | |
77 | | === Fill in required "new module" boilerplate === |
| 109 | ===== Fill in required "new module" boilerplate ===== |