Skip to content


Solidarity Epidemic: Pastilies Map

[Guest post from Vassilis Chrysos from Doctors without Borders Greece, Pastilies Map, previous Deployment of the Week] 

pastilies-ushahidi-en

On February 2013 a new Ushahidi deployment called the “Solidarity epidemic“, was released in Greece by the greek section of Doctors Without Borders. The organization has launched a campaign since last November (2012), under the title “Pastilles for the other people’s suffering“, aiming to build awareness to the Greek society on the suffering of people excluded from basic medical healthcare around the world. The “vehicle” for this campaign is a small box containing six pastilles, which can be bought in pharmacies all over the country. These pastilles are plain caramels, which people can buy to ease other people’s suffering. For every box bought, €1 is donated to the organization, funding its projects in Greece and around the world.

Early in the launch phase of the campaign we considered using the Ushahidi platform as a tool to both facilitate participation and networking as well as visualize the campaign’s impact to population across the country. A critical parameter for this decision was the fact that it is an open source software. This meant less cost for us and freedom to configure it according to our needs. It was very important for us that the plan was already in place and Ushahidi eventually managed to play its role as a tool to help achieve these objectives. One month after the platform’s deployment we have managed to gather feedback from over 200 people, which is a relatively small number, taking under consideration the overall campaign impact. We assume that one of the main reasons for this is the poor integration of social media tools with the platform.

Our audience is much more vocal when using Twitter or Facebook, thus it is very important to offer them the appropriate functionality. Recently, thanks to guidance from Brian Herbert, director of Crowdmap.com, we integrated the AddThis plug-in which we consider a step towards the right direction.

In any case we consider the Ushahidi platform a valuable interactive tool to communicate with our supporters. Apart from its apparent functionality, the resulting map will remain online as a “historical testimony” of the campaign’s impact and as a valuable feedback resource for future reference.

Posted in Community, Crowdmap, Deployment, Ushahidi, Ushahidi Users.

Weekly: Uchaguzi Hangout, Code of Conduct & Testing 2.7

Happy Week! We are a mission to share best practices and co-create a Code of Conduct. Plus, we have two Deployments of the Week from Venezuela. The biggest Ushahidi news this week is that we are in TEST MODE for 2.7. After months of bug fixes and many long nights/days, the developer team has crushed bugs and need your help to test before we launch. We are also tackling an intermittent bug in Crowdmap for logins. More in the report:

Uchaguzi – Election Monitoring Google Hangout

Join Daudi Were and the Ushahidi team to talk election monitoring, research, and learnings from the Uchaguzi Kenyan Election:

Date:
Monday, April 22 2013
Time: 15:00 EAT, 08:00 EDT

To join:
Uchaguzi Election Hangout

Code of Conduct

Ushahidi used a Code of Conduct/Collaboration for the Kenyan Elections. We would like to propose this Code be used for the Ushahidi community. Please provide any feedback and edits by April 30th either in the comments of this blog post or on the wiki. Or, please feel free to drop me a line – hleson@ushahidi.com. We have a skype Ushahidi Community group and will open up the discussion there. Please add heatherleson to be connected.

Draft Ushahidi Code of Conduct (draft)

Deployment of the Week

The Elections in Venezuela continue to be debated. In the past month, there have been two projects focused on giving voice to occurrences surrounding the Venezuela Elections:
Votoreporte and Defiendetuvoto. We recognize these projects both as Deployments of the Week:

VotoReporte (Venezuela)

Defiendetuvoto (Venezuela)

Help Wanted

In Southern Italy, thanks to crime in toxic waste traffic, people are over-exposed to high risk of several diseases and dying as a consequence of a massive environmental pollution evolving the food chain, the soil, the water and the air.” About La Terra dei Fuochi Project. (Facebook page)

The team is seeking programming expert volunteer in PHP and iOS with knowledge of the framework Kohana and Ushahidi. Please refer via Skype to: angeloferrillo or via Email to: direzione@laterradeifuochi.it.

Research

Matt Stempeck is working on his MA at the Center for Civic Media (MIT). He is building a workflow to aggregate crisismaps and other online volunteering projects that respond to major crises.

Would you help a community in crisis via the internet? Do @mstem a favor and take this survey to help his research.

Into the Code

Reminder: The next Ushahidi community developer call is scheduled for April 23rd, 2013.(North/South America and Asia friendly timezone). Be sure to join us, and bring a friend if you can.

Ushahidi v2.7: Upcoming Code Release

As we prepare for the 2.7 code release, there will be a code freeze from April 18th, to pave way for testing.

Key dates:
Code Freeze: April 18, 2013
Community testing: April 18 – 23, 2013.
Bug Fix April 24 – 26, 2013
Crowdmap upgrade to 2.7 code: April 27-29, 2013
Ushahidi 2.7 Code Release Date: April 30, 2013

We need your help testing all the bugs/features that the dev team has been working so hard to get fixed! Add your findings on this testing spreadsheet. Also, please join us via Skype or irc to co-test. As always, we promise to dig in and followup.

(photo credit: Sean Percival)

(photo credit: Sean Percival)

Ushahidi v3

Didn’t get a chance to here about what the 3.0 team is up to? Robbie Mackay explains it in his blogpost here.

The team needs help with handling API Authentication and adding support for other databases, particularly PostgreSQL/PostGIS. You can share your thoughts and suggestion on the dev mailing list, on the github repository, or by getting in touch with anyone on the team directly.

Crowdmap

The team is working on an annoying intermittent bug that forces users to get constantly logged out of their Crowdmap Classic deployments, or throws an ORM error. It’s been hard to figure out the problem, as it does not happen all the time, and there hasn’t been a definite course on reproducing the bug. We have a hunch it may have something to do with corrupt cookies, but will get to the bottom of it. We’re working very resolve this issue, and apologize profusely for the deep inconveniences caused by this. We’ll keep you posted on progress!

Workaround: Clear Crowdmap cookies from browser session.

Remember: You can sign up for a beta account for new Crowdmap.

Swift

Team Swift is working hard on building in analytics into the application over the coming weeks, as well as fine tuning search functionality and rolling out the new UI soon. Be sure not to miss out on the upcoming SwiftRiver event on the (April 25th, Nairobi based, not online). We’ll host a larger online event on May 11th, 2013.

Mobile

Henry’s been polishing up on Google Map v2 integration into the Android app. He’s also managed to fully integrate the Java SDK into it as well (woohoo)! Stay tuned for documentation on how to build the Android app and SMSSync from the source.

Posted in Code Releases, Community, Crisis, Crowdmap, Deployment, Elections, Reporting, Testing, Ushahidi, Ushahidi Users. Tagged with .

API Wrangling: Designing the API for Ushahidi v3.0

[Cross post from Robbie Mackay's Blog]

Following on from my Building 3.0 blog post, here’s another update on Ushahidi 3.0.

We’re currently still pushing on finishing the 3.0 API, or at least the first cut at it. The original due date for this was March 30, but thats slipped to mid April. Conversations have quieted down a little as we get to work on getting things done. Thats good, but means we need to keep working hard to keep the community up to date on our progress.

API design primer

Designing an API seemed simple.. but once you get into the weeds and start building things there are a lot of questions to answer. I’ve done a chunk of reading as I tried to figure out:

  1. What a proper RESTful approach would look like,
  2. What’s normal practice, ie. where do developers often cut corners? why? is this good or bad?

A few valuable resources:

Progress

The last couple of weeks have been dominated by the thousands of tiny decisions made at each step of building the API. I’ve tried to keep the wiki updated with the general patterns of our API. This gives a few guidelines

  • What methods to use, and how to accomodate more complex queries (ie. search)
  • What HTTP response codes to use
  • What to cover in functional tests
  • How to expose relations and links beteen resources

We’ve got the basics in now:-

This gives us enough to start experimenting, but there are still a lot of loose ends. The next things we’re looking at are:

I’ve built out most of the translations and revisions support already, but it still needs polish and documentation.

Authentication

This is probably the next major decision. How do we handle API authentication? do we use OAuth? 1.0 or 2.0? Where do we handle actual user login/registration?… the entire app is going to be built on the API.

At the moment I’m leaning towards OAuth 2.0, primarily because its what Swiftriver uses, and consistency between products is important. However OAuth 2.0 has some issues:

  • The editor for the spec withdrew saying OAuth 2 had failed
  • There are a few ways to mess up an implementation security wise
  • and one implementation isn’t guaranteed to be interoperable with another

That said the many almost-oauth APIs out there probably have more, and similar problems: rolling our own is not an option.

OAuth 2 is probably still going to get a lot of use, and there are good resources appearing on how to do it right, and a couple of good oauth2 clients.

One recommendation that stuck out was “If your API can require HTTPS, use OAuth 2.0 with bearer tokens. Otherwise, use OAuth 1.0a”. I need to dig into the details of this, but given deployers won’t always use SSL this is worth considering.

Stumbling blocks

In my last post I mentioned adding support for other databases, particularly PostgreSQL/PostGIS. I’ve already hit the first snag with this: minion migrations doesn’t handle other database engines at all. There are a few forks on github that try to solve this, but its mixed in with some other major changes. This isn’t a show stopper, but there’s some unpicking to be done and for now we’re concentrating on building a working API.

If anyone has working PostGIS knowledge and whats to have a go at getting this working, grab the codeleave a note and hopefully send a pull request. I’m happy to walk you through the existing code and answer questions.

Posted in API, Community, Design, Development, Product, Ushahidi. Tagged with , .

Weekly: Hiring, Inundaciones (Argentina)

Happy Week! In this week’s Community Report, we’re happy to say we are hiring, Congratulations to the hard working folks from Argentina (our Deployment of the Week), a new SwiftRiver event and thanks to our amazing community from Grant MacEwan University and Nepal.

Deployment of the Week

We recognize the tremendous effort by our Deployment of the Week from Argentina: Inundaciones 2 abril:


See more Deployments of the Week.

Help Wanted

globe
Know any designers great at both design and markup? We’re hiring at Ushahidi and don’t care where they live, just that they’re good and can work autonomously. If so, please shoot them this link:

Design@Ushahidi (Click to learn more)

One of our community folks needs testing help with his Ushahidi Geohazard android app. Give it a spin?

Into the Code

The next Ushahidi Developer call is April 23rd. Join us to talk shop on Ushahidi, Crowdmap, Swiftriver and your projects.

SwiftRiver has been evolving. We’ll be hosting a few events in the coming months for both Nairobi and global community folks. The first Nairobi based SwiftRiver Event on the 25th of April, 2013 at the ihub. Register. (Hold this date: a larger Nairobi/virtual event is being planned for May 11,2013.)

Alerts has been a hot issue, with ongoing discussions on fixes on github. Our community is addressing this issue, with Neil Horning of NepalMonitor is taking hold of the reins by hiring someone to help fix this issue.

Having issues with KML/KMZ layers on IE7? Talk to us

Version 2.7 release is scheduled for 30th April 2013. Linda and Robbie have been on a serious bug-fixing sprint over the past few weeks. You may have noticed a few issues being closed out. If you think we’ve closed an issue that’s still important for you, just let us know: comment on the ticket (and maybe reopen it).

Here’s a teaser for an upcoming Twitter fix.

Demoing GeoRoles via skype

Demoing GeoRoles via skype

We are happy to announce that Cam Macdonell and his software developer class of Grant MacEwan University in Edmonton,Canada is close to completion on their second foray into teaching using Ushahidi. On Monday, the class held demos, which I had the honour of skyping in to review. There were four great tackles of tickets from github including “Basic custom css” and “multiple colour displays of categories”. Two teams also answered Francesco Bartoli’s post post request for Georoles. Each team handled the issue differently. The code will be available soon once the student finish up. We’ll be sure to review and see how we can potentially merge.

See Cam’s previous post about the 2012 Ushahidi software developer class.

News and Research

Patrick Meier wrote up a summary about the report from OCHA Policy and Studies Series: Humanitarianism in the network age, including World Humanitarian Data and Trends 2012. The main headline is that Crowdsourcing can be considered useful with the strategy and action plan.

The report is available for download on the Relief Web site. All 120 pages. (PDF). Can we say weekend read?

Brac featured their work with Ushahidi in their piece: Crowdmapping the World we Want.

Ushahidi was featured in Emergency Journalism (blog). Thanks!

Janet Marsden wrote “ http://www.sciencedirect.com/science/article/pii/S138904171200040X” (This article appears to require a fee for the journal)

Posted in Community, Crowdmap, Crowdsourcing, Deployment, Development, How to Help, Jobs, Research, SwiftRiver, Ushahidi Users. Tagged with , .

Increased Levels of Online Hate Speech in February and March 2013

Hate Speech Incidences Captured by Umati Team

Hate speech has garnered growing interest in Kenya since the 2007/8 Post Election Violence where it was seen to have played a significant role. As a result, the Umati project was initiated in September last year to monitor the Kenyan online space for hate and dangerous speech, and will continue to run until May this year.

Find attached our second report this year, which highlights the effect of the March 4th elections on our research.

Between November 2012 and January 2013, Umati saw a declining number of extremely dangerous speech statements on the Kenyan online space. However, in the weeks leading up and following the elections, we saw an increase in such dangerous speech. Reasons for the increase can be credited to the 5 additional monitors on Saturdays and Sundays as well as the high use of social media during the election period. Even after adjusting for the increased volume due to weekend monitoring, we still see a doubling of hate statements collected in March as compared to those collected in February.

Umati March Report (PDF)

We look forward to your feedback and continuous support. We will be releasing our final research report by early June 2013.

Posted in Community, Elections, Kenya, Uchaguzi, Violence. Tagged with .

De olho nas emendas: Ferramenta de transparência e participação popular

[Guest Post by Diego Ramalho é Coordenador de Projetos do IFC
Dênis Mouras é Diretor de Programas de Promoção da Transparência nas Contas Públicas do IFC e membro do transparência hack. (Diego Ramalho is Project Coordinator of IFC and Dennis Mouras is Director of Programs to Promote Transparency in the Public Accounts of IFC member and transparency hack.) Their Anti-Corruption project is Eufiscalizo (Ed. Note: this post was submitted in Brazilian Portuguese. I took the liberty of using Google Translate (see text below) for those who speak/read English.)]

Nos últimos anos o mundo vem aprofundando os debates sobre transparência pública, combate à corrupção, lei de acesso à informação e participação social, basicamente temas que o Instituto de Fiscalização e Controle (IFC) vem debatendo nos oito anos de sua existência.

E como integrar tudo isso, envolvendo o cidadão? Como transformar milhares de dados em informações simples que qualquer cidadão poderá pesquisar e exercer seu papel ajudando a fiscalizar os recursos para as políticas públicas de sua cidade? Esse foi o objetivo do Instituto em parceria com os voluntários do Transparência Hacker em 2011.

A ideia foi bem simples: identificar um gargalo, que para os moradores de Brasília (Brazil), fosse obscuro, onde verdadeiramente necessitaríamos de mais transparência e principalmente uma participação ativa da sociedade civil.

Com essa análise chegamos à conclusão que deveríamos criar uma ferramenta que seria de fácil acesso ao cidadão identificar o que sua cidade recebeu de recurso através das emendas parlamentares, quais foram as áreas contempladas e principalmente identificar quais foram os deputados.

Isto porque percebemos que as Emendas Orçamentárias poderiam estar sendo utilizadas pelos Deputados Distritais para desviar Recursos Públicos. Uma emenda para realizar um evento festivo, por exemplo, poderia declarar o gasto de R$300.000,00 e de fato pagar, “por debaixo dos panos”, apenas 10% (R$30.000,00) enquanto o Deputado embolsa pra si os 90% restantes. Cada Deputado tem direito a propor 13,5 milhões em emenda e a Câmara do DF tem 24 parlamentares. Então, potencialmente, podem ser desviado mais de R$290 milhões atraves deste tipo de esquema de cortar um zero no gasto real e acrescentar um zero na prestação de contas.

A primeira missão foi identificar uma plataforma existente que encaixaria com o projeto, então escolhemos o USHAHIDI que é referência em geolocalização. Depois tivemos que solicitar mais de mil emendas em formato aberto, o que não aconteceu.

Encontramos muitas dificuldades quando criamos o ONE para Brasília, dificuldades essas já sanadas(As emendas foram publicadas no Diário Oficial como fotografias de documentos e seria trabalhoso digitar as milhares de emendas. Tivemos que fazer OCR pra converter os PDFs em texto puro e codificamos um raspador de dados com o Scraperwiki(1)); o próximo passo agora é expandir para a esfera federal, mostrando para a população todas as emendas do país.

Nosso próximo passo para 2013 é criar um grande mapa com dados da saúde pública do Brasil. Esse dados estão sendo compilados e trabalhados para melhor atender o cidadão brasileiro.

(1)https://scraperwiki.com/scrapers/raspador_de_texto_das_emendas_parlamentares_do_df_/

eufiscalizo

Eyeing the seams: Tool of transparency and popular participation

In recent years, the world has deepened the debate about public transparency, combating corruption, law on access to information and social participation, basically issues that the Office of Surveillance and Control (IFC) has been debating the eight years of its existence.

And how to integrate all this, involving the citizen? How to turn thousands of data into information that any citizen can simply browse and play its role helping to oversee the funds for public policies in your city? That was the goal of the Institute in partnership with volunteers Transparency Hacker in 2011.

The idea was simple: identify a bottleneck which for residents of Brasilia (Brazil), was unclear where truly would need more transparency and mainly active participation of civil society.

With this analysis we concluded that we should create a tool that would be easily accessible to citizens identify what city received its appeal through the parliamentary amendments, which were the areas covered and mainly identify what were the deputies.

This is because we realize that the Budget Amendments could be being used by the District Representatives to divert Public Resources. An amendment to hold a festive event, for example, could declare the expenditure of $ 300,000.00 and actually pay “under the table”, only 10% ($ 30,000.00) while Mr pockets for itself 90% remaining. Each Member is entitled to 13.5 million in proposed amendment and the Chamber of DF has 24 MPs. So, potentially, can be diverted over $ 290 million through this type of scheme a zero cut in real spending and add a zero accountability.

The first mission was to identify an existing platform that fit with the project, then choose the Ushahidi which is in reference geolocation. Then we had to ask more than a thousand amendments in an open format, which did not happen.

We encounter many difficulties when creating the ONE to Brasilia, now resolved these difficulties (The amendments were published in the Official Gazette as photographs and documents would be laborious typing the thousands of amendments. OCR We had to convert PDFs to plain text and code a scraper data with Scraperwiki (1)), the next step now is to expand the federal level, showing the population of the country all amendments.)

Our next step is to create a large 2013 map data with public health in Brazil. This data is being compiled and worked to better meet the Brazilian citizen.

Here’s a video about Eufiscalizo: One’s hack day:

(1) https://scraperwiki.com/scrapers/raspador_de_texto_das_emendas_parlamentares_do_df_/

Posted in Community, Corruption, Deployment, Reporting, Ushahidi, Ushahidi Users. Tagged with , , .

Community Update: Environmental Mappers, 2.7 in the Hopper

What an amazing journey to spend this past month with three of our largest community bases: Election monitors, anti-corruption and crisismappers. Each have unique and, sometimes, similar needs. Each has provided input into software, toolkits and programming needs.

Before I get into the community round up:

Have you sign up for your Crowdmap Beta account yet?

Getting connected

We are making some changes to our wiki, forums and community sites in the coming month. These are improvements to meet the feedback from the community survey. Stay tuned.

In the meantime, here’s a quick reminder of the Community Connection chart.

We have a number of real-time skype chats and an IRC (#ushahidi on freenode). Meet folks from around the globe: Ushahidi developer community, Ushahidi Mobile Chat, SwiftRiver Chat, Ushahidi Research and, happily, a General all things Ushahidi Community chat.

Metodi presenting the work of Transparency International Macedonia

Metodi presenting the work of Transparency International Macedonia

From the Community

Deployment of the Week

Spring is on my mind as I think about Deployment of the Week and environmental mappers. We’re happy to recognize two new Deployments of the Week focused on reuse and protecting our planet. As well, we recognize our friends from Transparency International and Anti-corruption mappers.

April 2: Wish20: Ecocide: A global citizens initiative to end ecocide by 2020 (global)

Wish20

March 26: Trashwag: Wood and Materials Salvage (Toronto, Canada)

Trashwag received some tremendous coverage. The team will be building on this in the coming months. Also, they really do win for spring cleaning planning.
CBC radio here and now.
Techvibes
Wired
Fast Company (FastCoexist)
BlogTO

March 19: Draw a Red Line: Join the Fight against Corruption (Macedonia)
(See last week’s post from the Draw the Line team)

Help Wanted

Lidia Cibor needs your help. She started a project named ‘Health and Diseases – real-time reports from Africa’. They want to monitor the health situation in Africa: outbreaks, health system improvements. Website is based on Ushahidi-crowdmap. They need folks to manage news, searching info and to manage Facebook fanpage. If you want join to the team, please send information to: africacrowdmap@gmail.com.

in the news

Tech President interviewed Daudi Were for their article: “Kenya Technology proved useful, not reason for Peaceful Elections.”

Uchaguzi community team member, Bradley Cleveland wrote about his experiences in “Social enterprise working for democracy and humanitarian relief.

Professor Colette Mazzucelli is quoted about crisismapping in Shari Smith’s article on “Deconstructuring Prevention: the theory of policy and practice of Mass Atrocity Prevention“.

One of the longest running and successful deployments from the Louisiana Bucket Brigade was featured in this recent piece. “St. Bernard Parish sulphur dioxide spikes lead to calls for better DEQ alerts.

We will be hosting an Ushahidi Research discussion in the coming week featuring some of these topics. Stay tuned for more details.

Into the Code

We have some great things coming in the code. The next release for Ushahidi platform is a bug fix release (2.7) set for the end of April. See github for details.

Take a listen to March’s Community Developer call to hear the latest about Ushahidi 3.0, Crowdmap Beta and SwiftRiver. (audio recording link on the wiki.)

The next Ushahidi Developer call is April 23/April 24th pending your timezone. Come with your questions, discuss your projects and more.

Sign up to join the next Ushahidi Developer call.

Happy Mapping.

Posted in Academic, Code Releases, Community, Deployment, Development, Elections, Kenya, Research, Ushahidi, Ushahidi Users. Tagged with .

Verification and Quality Control: Key Elements for Effective Anti-Corruption Crowdsourcing

[Guest post about Draw a Red Line from Metodi Zajkov, Secretary General for
Transparency International - Macedonia and Dimitri Neos, Executive Director from Center for International Relations . Ushahidi would like to extend our Congratulations to Deployment of the Week and Transparency International (TI) grant recipient, Draw a Red Line. They are investigating how to connect their map data with TI's database. See more about other winner's The Engine Room.]

A joint effort by Transparency International-Macedonia and the Center for International Relations deployed in 2012, its Transparency Watch project utilizes Ushahidi to empower citizen reporting of alleged acts of corruption. Ushahidi is used as a central focus of a general anti-corruption campaign, providing a platform for citizens to report corruption via the Ushahidi web site and mobile apps (Android and shortly, an iPhone app) as well as phone and email.

Citizen reports have resulted in investigation of 121 reports, 37 of which have been verified to date.

Results of these efforts have included:

  • A citizen report that led to an investigation of electrical counter utilization charges and associated violations of consumer electric energy charges. As a result, preparations are being made to challenge the constitutionality of the Energy Regulatory Commission of Macedonia Tariff.
  • A report that led to investigation of improper property taxes that was determined to have occurred over the last five years in the Skope Center 2 region. Upon finishing the analysis, TI-Macedonia informed the region’s citizens of their rights to request recourse from the city.
  • A report regarding the abuse of worker’s rights resulting in a government inspection. Their findings supported the allegation and a notice to desist all irregularities was effected.

From its inception, we identified key requirements to ensure vetted reports were identified for display on the site and provide safeguards for citizen’s personal information throughout the process.

draw a red line

Processing Anti-Corruption Reports With Due Diligence

Transparency International – Macedonia provides all of the on-the-ground investigations of corruption reports. A rigorous investigation process TI-Macedonia has in place determines the validity of the report. This initial investigation is performed within a week of the report received date. A determination is made whether the report has merit for further investigation or whether it should be passed on to a different entity/organization. After this, further investigation (gathering additional information from holders) of the report may be needed which may last months before resolution. TI-Macedonia works closely with the citizens throughout the process and, in many cases, provides consultation on steps for legal remedies. TI-Macedonia cooperates on institutional level with various governmental entities to provide necessary information on the merits.


Presenting a true picture through report metrics and related details through Ushahidi can be an involved process, starting with identification of what metrics provide true measures of the project’s activities, objectives, and outcomes.

Poorly identified (and displayed) data not only gives the public a false picture of what’s really being reported but does not provide the organization accurate information views that can be used monitoring and evaluating the project. In our project, that has included effectively analysis of cases and reporting patterns; and managing project campaigns better.

The default setting of Ushahidi provides a raw count of citizen reports in its displays. While we have found this useful, we needed another subset of data: verified reports. Listing all citizens reports received can result in a number of issues including:
•Unsubstantiated and false reports inflating numbers
•Unsubstantiated and false reports providing incorrect and possibly injurious information

For this reason, we have split out the types of reports into two categories:

Received reports – Raw count. This raw count is displayed on the site but no details about individual reports are shown unless verified by the TI-Macedonia staff.

The successful outcome of the information gathering stage may be intercepted by early warning (i.e. publishing the received report on the list. Hence, there is always a significant number of reports waiting for the conclusion of the investigation process to become readily visible on the web list of received or verified reports.

Received reports – Listed. As mentioned above not all of the reports are verified at once. Some never get verified at all. Never the less, all the reports that may not interfere with the investigation phase are listed together with reports that do not get verified. However those reports get attached the information from holders that show the suspicion was not reasonable.

Received reports – Verified.
Only those reports that have been verified are displayed. Details of the report may be shown on the site after being agreed-to by the citizen. The report is being verified after the investigation stage showed sustained proof for the reasonable suspicion eider explicit or implicit to be further examined by the authorized bodies.

Both Listed and Verified reports are usually supported by comment of the TI-Macedonia staff.

Safeguarding Identities

Reports of corruption are inherently of risk to the person reporting it. Ensuring personal identity information is secure and is of paramount importance. To protect citizens, details of reports are only shown on the site when approved for displays by the reporting party(s). Moreover, any personal information is not displayed on the site.

Making It Work

Understanding business needs, processes and objectives are crucial to developing a good Ushahidi design. In general, our project has found these high level steps to be useful:

  • Identify and define what you want to measure
  • Identify and define processes to accurately capture, monitor and evaluation that data
  • (including roles and responsibilities of involved parties)

  • Ensure the safety of personal identifiable information of the reporting party.
  • Refine business processes and activities based on data captured.

The work is always iterative and all data and business processes must be monitored and evaluated to refine not only Ushahidi but the project itself. Using metrics that accurately reflect the business while safeguarding citizen information provides a strong start to successful projects.

Posted in Community, Crowdsourcing, Data, Mobile, Ushahidi. Tagged with , .

Building Ushahidi 3.0

It’s been a while since we first started working on Ushahidi 3.0, and a few people may be worndering what’s happening. There’s always a lot going on at Ushahidi, and I certainly remember it was hard to keep track as a community member.

Last year we did a lot of good work on the 3.0 workflows, and we started laying out plans for 2.x – 3.0 migration during our annual planning retreat in January. However progress since then has been a bit derailed by Uchaguzi – an election monitoring deployment for Kenya. Now Uchaguzi is done we’re getting moving building API, and starting to dig into the workflow details. Watch our progress on the wiki and on github.

Building a good foundation

Ushahidi 3.0 is a ground up rebuild of the Ushahidi platform. While some keys aspects will remain the same, the underlying code is getting a complete revamp. There are a few reasons contributing to this decision, but underlying all of this is the desire to give the platform a solid, extensible, maintainable foundation. The 2.x series code works well, but we’ve reached a point now we’re its hard to move further forward while also ensuring we don’t introduce new bugs.

Things to look forward to in 3.0:

Kohana 3
Ushahidi 2.x was built around the Kohana framework . However, it was built on Kohana 2.x. We upgraded the core to Kohana 2.3 but when Kohana released version 3 there was no real upgrade path. We’ve ended up maintaining our own hacks and changes to the Kohana 2.3 core, some of these were backports from Kohana 3, others just fixes to key issues like running Ushahidi on PHP 5.4. Going forward we’re building on Kohana 3.3 which is both a much better framework and is actively maintained and used.

API driven
The API in Ushahidi 2.x was always a bit of an afterthought. As such it reproduces a lot of code, misses key REST api concepts and simply requires too much effort to work with. The web has moved on, becoming more focused on mobile and custom apps with multiple data sources. Having a solid API is now a must have. In 3.0 the API will be the core of the system, driving both the frontend and other clients.

Behat tests
Behat gives the ability to write simple human readable tests. It’s providing the primary method for testing the API in 3.0, and is already proving invaluable.

Database Upgrades Minion Migrations gives us a solid framework for database migrations. This should help us provide robust upgrades and downgrades in future versions.

Support for other databases
Support for PostgreSQL and other databases has been a long running request for Ushahidi. We aiming to support this from the start in 3.0, a much easier task than trying to shoehorn support in later.

Tracking the build

We’re trying to keep the processes lightweight, however there’s still a lot to build. I’m tracking a backlog of features and other issues through github issues.
As each feature gets started we’ll be adding rough spec details and comments to the ticket description, and when features are complete they’ll be code reviewed using Github pull requests. Each of these steps is a chance for you to comment on how we’re doing and suggest improvements.

Most tasks will get assigned to and built by the internal team. But if you want to get involved in v3 development chime in on a ticket and let us know where you can help.

A lot of discussion is happening between the core team at the moment, but as we get further in we’ll be trying to open that up and get community feedback as well.

Early targets and migration

As we’re pushing forward with v3, one the big items is going to be migration from Ushahidi 2.x.
To ensure this works smoothly we’ve set a couple of early targets:

3.0 Alpha - due end of May/early June –  will try to cover core 2.x features and include an import script to pull data from 2.x. This will really be for developers and hard-core testers only. At this stage we won’t be aiming for a nice import UI, just a solid import so we can start testing and ensure we don’t lose data.

3.0 Beta - due end of June/early July – will go further on migration. Migrating from 2.x will mostly likely be integrated into the UI of the installer. The UI may not be polished at this stage, but it should be enough have early adopters trying out the process and getting running.

Shout out if you have any more questions on the 3.0 build. We’ll be posting regular updates and discussions to the developers mailing list as we continue to build.

Keep on mapping!

Posted in Development, Ushahidi. Tagged with , .

Released SMSSync v2.0.2

pending

Without much hesitation, we are very much pleased to announce the immediate release of SMSSync v2.0.2 on the Google Play store.

This release includes a ton of bug fixes, minor features and improvement to the existing features. Notably, there is now Regular Expression support for filtering out messages sent to SMSSync.  See the change log for a complete list of changes.

We received huge contributions from our community. Without them, this release would not have come sooner. We hereby thank their efforts in making this release a reality.

Posted in Code Releases, Development, Mobile, Uncategorized. Tagged with .