inhaiti winter 2012

final presentation

Transcript

1. INFORMATION NETWORK: HAITI wes vetter - jasmine liu - mishika vora susan liu - anna shilova - raymond chen - jon wong ta: james mccloskey client: katie rast
2. our client
3. haiti medical and public health information sharing environment (MPHISE) OBJECTIVES: - deliver consistent GUIDANCE, POLICY, and CAPABILITIES across governmental and organizational domains. - seek to enable RAPID RESPONSE by the community to any crisis or disaster. - provide CRITICAL INFORMATION regarding medical dangers to the communities and areas in question.
4. our project (and current progress)
5. wehave-weneed.org
6. wehave-weneed.org a communication-agnostic, inventory sharing system for doctors and humanitarians in Haiti
7. wehave-weneed.org a communication-agnostic, inventory sharing system for doctors and humanitarians in Haiti
8. communication agnostic SMS WHWN EMAIL To enable transactions, users must be able to: 1. message each other without revealing private information. 2. message each other without having to login to the site To facilitate message routing, we create unique hashtags to identify each transaction.
9. communication agnostic SMS WHWN SMS we use message routing for SMS to SMS: Assume User 1 & User 2 are share transaction "#83aj". 1. User 1 texts our phone number with the message "#83aj - Hello World" 2. Our server receives the text, parses the transaction number, and forwards the message 3. User 2 receives a text from our phone number that says "#83aj - Hello world"
10. communication agnostic EMAIL WHWN EMAIL and we use message routing for email to email: Assume User 1 & User 2 are share transaction "#83aj". 1. User 1 emails messages@wehave-weneed.org with the subject "#83aj" and a message "Hello World" 2. Our server receives the email, parses the transaction number, and forwards the message 3. User 2 receives an email from messages@wehave-weneed.org that says "Hello world" and has a subject "#83aj"
11. communication agnostic SMS WHWN EMAIL and we even use message routing for SMS to email (or vice versa): Assume User 1 & User 2 are share transaction "#83aj". 1. User 1 texts our phone number with the body "#83aj" and a message "Hello World" 2. Our server receives the text, parses the transaction number, and forwards the message 3. User 2 receives an email from messages@wehave-weneed.org that says "Hello world" and has a subject "#83aj"
12. wehave-weneed.org a communication-agnostic, inventory sharing system for doctors and humanitarians in Haiti
13. inventory sharing users start by adding supplies to their inventory, one by one or by CSV upload
14. inventory sharing Having CSV uploads allows us to reduce the friction between shipping manifests and our database. • Allows users to upload multiple items at once • Each excel file is expected to be formatted properly for upload ◦ Prompts the user which lines have missing fields and asks the user to fill in those fields before uploading the file again • This function will parse each item and its attributes and store it into the database In general, we tried to make this feature as robust as possible by testing and handling corner cases with proper error messages returned to the user
15. inventory sharing Having CSV uploads allows us to reduce the friction between shipping manifests and our database. Initially, we required users to enter more attributes ◦ Item description ◦ Longitude and latitude We scaled down the form requirements to make the application more flexible and user-friendly Now we only require: Item name Item category Amount Units Optional item description Upon successful uploads, users may edit individual item details
16. inventory sharing Having CSV uploads allows us to reduce the friction between shipping manifests and our database.
17. inventory sharing users start by adding supplies to their inventory, one by one or by CSV upload then they can search for what they have or what they need
18. inventory sharing Right now a simple search is implemented. It allows a user to search by item name, transaction ID, or item description When active site use grows, fully dedicated search service will be implemented. We will also begin to fine-tune relevance of results to be more useful to users.
19. inventory sharing users start by adding supplies to their inventory, one by one or by CSV upload then they can search for what they have or what they need which leads to transactions between users
20. inventory sharing 1. User views item on postings and wants to Request or Fulfill 2: User clicks link and message form pops up 3: Message form is auto filled with subject of item being requested/fulfilled 4: User edits message in message form and begins a transaction we use these transactions to route messages between users while ensuring that we keep their information safe from prying eyes. this will serve as a feedback mechanism to know what we can improve to better serve our users i.e. many people responding to one specific post, new categories of items that should be added, more security for medical items posted, etc. finally, transactional/messaging data can give us more data for visualization and statistics for humanitarians
21. inventory sharing this will serve as a feedback mechanism to know what we can improve to better serve our users i.e. many people responding to one specific post, new categories of items that should be added, more security for medical items posted, etc. finally, transactional/messaging data can give us more data for visualization and statistics for humanitarians
22. wehave-weneed.org a communication-agnostic, inventory sharing system for doctors and humanitarians in haiti
23. our tech stack
24. wehave-weneed.org runs on Django + Python and mongodb,
25. wehave-weneed.org runs on Django + Python and mongodb, hosted in its entirety on dotCloud,
26. wehave-weneed.org runs on Django + Python and mongodb, hosted in its entirety on dotCloud, using services like Twilio for SMS, Postmark for email, TileMill + TileStream for mapping, and bitbucket + mercurial for version control
27. other cool things
28. wehave-weneed.org auto generates its own documentation thanks to Sphinx
29. wehave-weneed.org and was on display at PyCon 2012
30. our future
31. short term goals Flesh out unit and integration tests Improve the robustness of our application Test our current setup for many concurrent users Increase transparency of development process by exposing project management and version control tools. Look to deliver an ALPHA version this next quarter.
32. long term goals International Accessibility • International SMS service • User testing in foreign countries • Implement site in different languages (i.e. French) Trend Predictions • Heat Maps • Predicting disasters and outbreaks from trending item demands Privacy • Structure and organize how to manage, share, or hide inventory with other users or groups
33. our challenges
34. problems with transactions • Ambiguity between 'Owner of Item' and 'Requester of Item' • One who posts an item may be posting about owning an item or needing an item • Where should a transaction begin? At the start of a one-way communication, or two-way communication? • How should users view messaging and transaction? ◦ Answers to posts of Have's /Need's ◦ Submissions of posts of Have's/Need's
35. questions?
36. our thanks mandy bratton zach salin james mccloskey katie rast