Prototype

Secure Mobile Data Collection For Human Rights

Summary: 

Testimonies. Field investigations. The voices of victims and witnesses continue to be the richest and most central source of information for human rights advocacy and research. Stories form the core of human rights data and the foundation for the human rights community’s demands for truth, redress and justice for the victims of gross abuses.

Human rights defenders often work in vulnerable environments: sometimes the same state agents whose crimes activists are documenting steal the activists’ computers or tap their Internet connections. Benetech (www.benetech.org) works with partners, as we develop Martus (Greek for “witness”, www.martus.org) to protect human rights activists, witnesses and victims in those environments.

Martus was designed to protect human rights defenders collecting information to support advocacy in dangerous contexts. Many HRP partners are involved in contentious debates about violence carried out by national security forces. Some are documenting violations during ongoing conflicts. Others have gathered extensive data about past abuses. These situations, and growing awareness of the risks to electronic data, have led human rights groups around the world to seek out Martus partnerships with us.

Private information is automatically encrypted by Martus on a user’s local computer, so that if an organization’s computers are lost or stolen, then sensitive information cannot be read without the authorization of the person who created it. Martus backs up the encrypted information to a network of secure servers around the world, so that if users’ computers are lost or stolen, then irreplaceable testimonies and investigations can be recovered.

Our task now is to rethink how the software contributes to human rights advocacy, maintaining our focus on security while adding new devices and architectures, better performance, and new analytic and visualization tools. We need to ensure that Martus does an even better job of advancing the cause of using human rights abuse stories for positive change.

THE NEED:

More and more human rights activists/journalists need secure mobile tools for doing data collection – while there are many mobile data collection tools available, many of them are not secure, putting the data collectors and their sources at risk.  Our goal is to build in Martus-level security to tools used smart-phones, greatly enhancing their ability to do their work unobtrusively and safely in the field. 

We would like to build a “Send to Martus” mobile Martus API prototype, initially on Android.  This would allow data collected on Android phones (text and image/video/audio attachments) to be sent securely to Martus servers for later load into laptop/desktop Martus for editing/organizing/analyzing.  Initially we would like to develop options to work with basic Android native tools and basic data, but may eventually also want to integrate with Tor, mobile collection tools for more structured data (E.g. questionnaires), or investigate IOS options as well. 

TECH NOTES:

Martus is open source, written in Java, for Windows/Mac/Linux.  Mobile prototypes should be security focused and be developed using open-source libraries.

Category: 
Status: 
Images and Video: 

Improving public transportation reliability to encourage people reduce their carbon footprint.

Summary: 
  • Managed to achieve a good prototype of a semi-real time tracker
  • Pulled data off the MARTA schedules to be used as our primary dataset.
  • Platform agnostic and user friendly.
  • Involves SMS service and use of smartphone technlogies to cater to a wide section of international population facing this problem
What we accomplished during the event: 
  • A good notion of routes in different countries.
  • A decent working framework to be able to get an idea of approximate time your transport is due in to the stop near you. 
  • A user friendly way of updating information in a crowd sourced framework. 
  • Intelligent route prediction possible once the data sets evolve over time. 
  • SMS service to cater to developing nations. 
  • Potential integration with Google transit as a way to handle deviations from predicted schedules in developed countries. 
Category: 
Status: 
Frameworks: 
Images and Video: 

InfoRisk

What we accomplished during the event: 

We created a twitter account capable of automatically retweeting and made a website with limited funcionality.

Progress made since the event: 

We've cleaned some scripts, but they're not working properly yet.

Next steps: 

We aim to finish an initial beta in january.

Category: 
Status: 
Programming languages: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 
Seeking people with skills in: 

Management of Microfinance Records

Summary: 

 

GAWFA is the leading and the first Micro finance institution established in 1987 in The Gambia. The total Membership of  GAWFA is over 49,000 members and the active borrowers are  over 14,780 (96% of who are women).GAWFA has branch offices spread throughout The Gambia.

 

 

 

 

Why we are working on this problem: 

GAWFA has never had an integrated system to consolidate the financial and operational transactions, and has over the years been tracking loans given to members through a manual system that is done in with an excel sheet Due to the methods of data entry and management, a lot of errors crop up, and the generation of reports is a slow and tedious task.

Category: 
Status: 
Programming languages: 
Frameworks: 
End user environments: 
Server requirements: 
Apache, Mysql, Php 5.2+
Images and Video: 

Security Alert App for Humanitarian Workers in Haiti

What we accomplished during the event: 
Category: 
Status: 
What RHoK event this project is being submitted for: 
Images and Video: 

CharityClick

Summary: 

CharityClick provides low cost advertising for charities through innovative web technologies.

 

CharityClick capitalises on the moment that a person is emotionally moved when reading an article or watching a video about issues that can benefit from a donation. It does this by vastly reducing the number of steps between desire to help and making a financial contribution.

 

How it works:

CharityClick places a tooltip next to a charity's name whenever the charity is mentioned anywhere on the internet. See example below: http://boileddown.squarespace.com/storage/Example%20CharityClick%20toolt... allows the potential donor to go straight to the donate page or if the charity has a text to donate code, they can enter in the free text area below as shown. There is also an option to go to the charity main webpage with "view charity information".      
Why we are working on this problem: 

Greatly reducing the advertising and marketing costs for charities by levaging already established media has the following benefits:

 

1. Gives charities an effective low-cost solution to fund-raising as many of them are already mentioned in articles, videos and blogs. This will particularly help small charities which tend to have very low marketing budgets.

 

2. Reduced expenditure on advertising means that a much higher percentage of each donation goes to the actual cause rather than to the advertiser's pocket.

 

This allows potentially more to be accomplished with the extra money by the charities, and may reduce cynicism about the waste of money associated with donations and increase the likelihood of donations in the first place.

 

3. Potentially less time spent fund-raising and more time doing productive work.

 

4. Making donations as easy as downloading an app or making a one-click purchase may potentially divert trivial commecial purchases into meaningful contributions.

What we accomplished during the event: 

We had 100% working software with a small bit of smoke and mirrors to tie it together.

 

Here's the link to the extension:

http://www.chromeextensions.org/wp-content/uploads/2011/12/charityclicks3.crx

 

And once you install the link visit the following two links

 

http://www.guardian.co.uk/society/2011/dec/04/charities-welcome-cash-for-homes?INTCMP=SRCH http://www.ted.com/speakers/sunitha_krishnan.html

 

Look for the little hearts. Hover over the hearts and you'll be able to see the the idea in action.

 

We also created a webpage but unfortunately it is not live as of this initial submission and so we are unable to provide a link to it right now but we'll add it to the revised versions. Many people at the event thought the site looked really smart for something put together in just over 24 hours.

 

 

We achieved this great progress through a number of means: systematically working through the user jouneys by from both the donor and the charity side, stripping it down to the bare essentials of what is likely to be accomplished in a weekend and focusing on those key tasks. 

 

The project was divided into discrete sections that allowed us to plug away on a section each whilst lending support to each other. David concentrated   

on the extension, Sandy worked on the main website, Andrea tackled the design and content and Alejandro created the presentation.

We were a team with great complementary skills who worked well with each other to leverage our individual abilities.

Progress made since the event: 

It's been less than 48 hours since the event that this initial submission is being written....

 

Nevertheless, the team have already been working on solutions from ways to devote more time to the project (by applying for sponsored time from our employers) to ways to promote the project (by making a video and contacting key people).

Traction: 

The feedback from everyone at the RHOK London event was overwhelmingly positive.

 

See minute 2:58 to 4:58 from the prize giving:

http://www.youtube.com/watch?v=DpSMNxdHaCM&feature=player_embedded

 

We were fast tracked for Springboard.

 

 

Next steps: 

General non-tech:

  • Utilise the fast track offer we were given for Springboard
  • Upload short presentation with links to the live site
  • Spread the word to friends, family, everyone who could be a donor
  • Contact key people within charities, get feedback and get as many registered as possible
  • Get a designer 
  • Address technical issues

 

 

Tech:

 

 

 

 

The team will work continue remotely and communicate via email

Next organised group face-to-face meeting is in January (exact weekend tbc)

 
Community help: 
  1. Spread the word and get would-be donors to install the exension
  2. Get charities to register with us
  3. Advice on the best ways to get large scale user and charity adoption
  4. Design help
  5. Advice and mentoring on the business-side 
Category: 
Status: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 

Localization Tools for e-Learning Modules (Numbers and Data Fluency)

Summary: 

Public Learning Media, a non-profit organization in the Boston area, has created three open-licence Learning Tools for young students to become more data literate and improve numeracy -- and while the Learning Tools involve data visualization and graphic calculators, the instructions are presented alongside to get started or when they ask for help.

The web-accessible Learning tools have been widely taken up in English speaking countries (USA, Canada, Australia, New Zealand and the UK) and there is increasing demand in non-English speaking countries.

The Learning Tools need a module to localise the content of the Tool Page  based on the student's request (translate language), which can be easily switched on by the STUDENT on the web site, using a language selector pull-down list.

The proposed solution is to find open source tools which 1) scrape content from the web site page and 2) look up the target foreign language phrases to substitute appropriately,  and present the content back on the web page.
 

Why we are working on this problem: 

We see these tools as valuable to improving numeracy and data fluency in young people.  We see good uptake of the tools in English-speaking countries.  A single language translation project to Spanish has driven good uptake in Spain and Mexico.

 

We would like to improve upon this success by increasing the translation capability and opening up the potential community to make thesse tools availble to international school audiences.  We see the potential to integrate open source tools to facilitate crowd-sourcing of the translations.

What we accomplished during the event: 

Progress so Far ...

  • goals and outcomes

 

  1. Prototype will be assembled from open-source tools and toolkit for crowd-sourced translation.
  2. Minimise code changes on current STUDENT system as it is currently live and in use -- look to swap out the current calls to the bespoke translation system for SPANISH

 

  •      code assessment criteria and project feasibility
  1.      scope limited in terms of hacking access primary web site ...
  2.      source code needs to go under formal version control
  3.      tools must be easy to use and understandable, or invisible

          

  •      strategy for prototype development
  1. Assess team member skills and capabilities; roles & assignments.
  2.  Follow a common methodology to scrape and translate phrases, and store the base and translated strings in a common language support catalog.  This catalog will be an on-going asset of Public Learning Media.
  3. Find open source tools and cobble together a module for Student Web Site that makes calls to language support catalog.
  4. Build a workflow which integrates external tools for crowdsourcing corrections and additions to the language support catalog
  5. Build / borrow resource to support web site scraping and converting phrases using the newly build language support catalog
  6. Build / maintain standardized LINGUAL SUPPORT CATALOG
  7. Find tool to facilitate crowd source evaluation/improvement of machine translations
  8. Get source code from Learning Resources and put in source control
  9. Establish project at GITHUB and manage the code as we build it

            

  • experimentation plans

 

  1. test getText toolkit support with PHP/APACHE
  2. write script to translate en-US phrases to localized version
  3. experiment with POOTLE language files and extant user interface
  4. prototype UI with CSS against native POOTLE user interface

             - give each TRANSLATOR a personal workspace page
             - exploit dashboard and statistics tools and present to workspace
             - simplify and stream line workflow to TRANSLATOR audience
             

  • issues/challenges
  1. had to scrap LAUNCHPAD and find another tool for translation
  2. found POOTLE open source system for crowdsourcing translation
  3. installation called for cloud web services

             -- got an AMAZON Sandbox Subscription at zero cost
             -- generic install was easy but requires a few extra steps
             -- POOTLE needs to be made "interactive" to allow us to "ftp-in" our content (language support catalog).
    

  • prototype / demonstration of concept

          using the home page for one of the "WHO IS" learning tools,
          scrape the English phrase and translate to French

 

 

GROUP DIARY

 

TEAM ASSESSMENT

  • Owner - problem definition and deliverable design, assist with semantics and site code organization, make source available to group and clarify licensing issues.
  •      Developers - assess source website code and proposed code modules (calls to language support and translator system to contribute)
  •      Organizer - Document as we go, make steps on sticky notes and move through phases "backlog" "in progress" "validate" and "done", scribe the diary -- prepare the presentation for the RHoK community.
  •      UI Designer -- Wireframe UI for Translators Website


 
DAY 1

  •  got the source web site under version control at GITHUB
  •  evaluated experimentation steps and set up project mgmt board
  •  installed/upgraded apache servers and php resources on development machines
  • evaluate getText to scrape the website for CATALOG keys to support the STUDENT interface (drop-down language choice and translate screen text)
  • evaluate Launchpad to build/maintain the master catalog

               -- found too many restrictions for use -- BSD licensing etc.
               -- web tools are required to be open-sourced (it is not clear that ll of the Public Learning Media modules are formally open source)
          
DAY 2

  •  evaluate POOTLE as external language phrase translation resource (language.sourceforge.net)
  • set up development web server on cloud services with POOTLE support
  • evaluate user interface / ease of operations

                 -- found need for UI tweeking -- enter Jonnah Goldstein

  •  prepare summary of process steps and presentation of project
  • discuss UI prototype -- try to include dashboard for TRANSLATORS
  • prototype TRANSLATOR INTERFACE

             a. theming -- styling CSS and HTML 

             b. UI changes -- workflow, process clarification 

  • presented proposed system design, experimentation findings, progress-so-far and next steps to the RHoK Boston group

 

Category: 
Status: 
Images and Video: 

Donor Relationship Managment

Summary: 

DRM is a web application designed to help charities manage their donors. This includes recording of conversations with donors, sending out donation requests to group and individual donors as well as general administration of donors, groups, and requests.

Why we are working on this problem: 

Charities that survive simply on donations from companies and individual donors do not have an efficient way to manage their donors. Some of them have large amounts of spreadsheets for capturing their data which often gets lost and duplicated. They have an issue when it comes to following up on donors becuase they dont know who has already been contact and this can lead to donors being irritated by continous calls from the charity. The relationship with their donors is essential to ensure the sustainability of these charities and they are simply not managed efficiently at this stage.

What we accomplished during the event: 

We managed to develop web application solution to help charities manage their donors. This includes recording of conversations with donors, sending out donation requests to group and individual donors as well as general administration of donors, groups, and requests. The solution is implemented without user management at this stage but most of the functionality is implemented.

Progress made since the event: 

None

Traction: 

The subject matter expert found the system great but still acknowledged that a lot of work is required to make the system stable and more alligned with their business processes.

Next steps: 

We will work together with another team who tackled this problem so that we can enhance the system and make it more stable so that it can be used by the charity.

Category: 
Status: 
Programming languages: 
Frameworks: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 

D2020

Summary: 

Problems can be hard to solve. Games make problem solving fun.

 

D2020 is a platform to inspire people to code, build games, and save the world.  

 

D2020 aims to train 2020 new game developers to make 2020 games by 2020, each one confronting one of the many pressing problems humanity faces. 

Why we are working on this problem: 

We believe all knowledge should be playable.  

 

Our game Code Hero teaches you how to code while you play, but there's more to making all knowledge playable than just the technical skills. We need to inspire the minds and build the teams that will make all the world's problems solvable. 

What we accomplished during the event: 

We built the first revision of the D2020 platform, along with an example game that teaches you how to make a problem-solving game. 

Category: 
Status: 
Programming languages: 
Frameworks: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 

Integrating Microtasking into Existing Crowdsource workflows

Summary: 

Have PyBossa running and have begun spec on the data interchange process.

 

Problem:

 

http://www.rhok.org/problems/integrating-microtasking-existing-crowdsour...

Why we are working on this problem: 

There is a great deal of lost productivity and confusion from running multiple unlinked applications to coordinate volunteer activities.

 

Microtasking is extremely effective for successful crowdsource projects.

 

A generic framework to break out broad ranging tasks into specific manageable ones requires far less training of new volunteers, faster process of getting 'up to speed' by experienced volunteers and ability to provide assistance to other tasks outside of the volunteers traditional field of expertise.

What we accomplished during the event: 

Problem definition

Novel approach decision

PyBossa set up, functioning

Next steps: 

build parser/importer to populate task stack

build exporter to update task source environment

 

Category: 
Status: 
Programming languages: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 

Pages