Drupal Help Haiti: Day 3

Having finally sorted out our goals (use the Project EPIC Twitter syntax to get targetted information to people who can help, using Drupal as a tool for managing and organising that data), day 3 started with an ambitious set of tickets:

  • Identify and engage with an SMS gateway
  • Configure the Feeds module to create nodes
  • Create views for displaying aggregated tweet nodes
  • Collate list of Haiti resources
  • Install Backreference module
  • Extend functionality of the tweet views for an "add to case" link
  • Configure subscriptions and messaging
  • Add CCK Nodereference field to the Feed Item content type (tweets)
  • Install and configure Deploy module
  • Charity links to donation sites

And I only just realised, the kind of fundamental ticket, "Create feeds for our Twitter searches", was not there - doh! I just added it.

As you can see, today's efforts sort of petered out. Unfortunately I (having spent 2 days on this already) *really* needed to focus on some paid work for a day. I suspect others were in the same boat.

Nevertheless, things started well with fellow Drupaler blogger, Joachim, taking on two tickets in the early morning. Then Frans came up with the goods and got us a Clickatell test account for SMS pushing. Daniel was around all day keeping an eye on the server, installing things, backing up, etc. And Sudhir joined the team, creating some useful documentation for new developers on the project. Of course, Mike and Rob were present as always, with ideas, guidance and so on. (If I missed anyone, I'm sorry.)

Sounds like a lot of people, but when you're ducking in and out, 10 minutes here, 15 minutes there, it's nearly impossible to tackle some of the bigger config tasks. So even though we finally had a solid plan, we really didn't have the resource - the real meat of the project didn't really get much love today. Ironic, since we even sorted our our Unfuddle issues, so could add a million developers to the project, if we could only find them (thanks again to Rob for Unfuddle use).

However, there is good news too! Mike managed to raise Alex and the Zivtech guys and they are back on board. As I type they are working away on the development site, trying to execute on the tickets in Unfuddle. This is a huge boost, and we're relieved to have them, and several other, US developers on board this evening and through the night. We might close some of those tickets before tomorrow yet!

Also James in Haiti has given us a cell phone number with Digicel, one of the local operators, so we can test pushing SMS as soon as the system is ready.

Things are falling in to place. They just can't happen quick enough! I'm personally disappointed we didn't manage to get a working Case Tracker up and running during the European working day, but it just didn't happen. No one's fault - just the way it is.

Tomorrow, surely! Maybe even tonight, if Zivtech and friends can work some magic state side. =)

OH: NEWS JUST IN. SMS is WORKING! Excellent stuff by Frans Kuipers! That just made my evening. =)

And while I'm typing, Steven (who has been helping with the US effort) is lining up to do something cool with Adobe AIR. He has some Flex experience and is keen to give it a go. More on that tomorrow, but it could be really useful.

ushahidi

are you trying to replicate this site: http://haiti.ushahidi.com ?

Actually, maybe

We now have more detail on *exactly* what Ushahidi are doing, and it seems there is a lot of cross-over.

The ticketing side still has value.

Thoughts now:

  • Help hashtag up Ushahidi incoming data with hashtags and push it out again through Twitter (add another stream of potential helping eyeballs)
  • Continue the ticketing idea, as it still has value as a means of processing the Twitter data that already has taxonomy applied to it

Maybe if we can get more volunteers going this way, they can some how liaise with the Ushahidi team?

One thing to avoid would be doubling the messages back to Ushahidi - that would not be helpful.

In a word, no

Someone else asked this too. Here is my response:

Our goals are:

  1. Encourage people to tag up tweets so they're useful to EVERYONE (this kinda emerged last night - we're going to try and either build an app to facilitate this or point ppl at existing apps).
  2. Start linking the data together in a meaningful way - Ushahidi have a great overview, we're trying to make a tool that links in with a case tracker though, for tying tweets together, getting the right people talking, in an organised way that can be handled remotely.
  3. Mike C has a plan to specifically go after doctors and supply centres, using the EPIC tweet syntax as a base to add centre-specific tags on to ... so if we can get word out and educate doctors how it works, and supply centres how to watch, we can get that moving better. Right now, it isn't - doctors are without supplies that actually exist three streets away!

Number 3) is a big ask, in terms of getting buy in - but that's Mike's job and he thinks he can do it. We hope so. Either way, 1) will surely be useful to everyone (including Ushahidi) and 2) ought to be - it certainly goes a step further than anything we've seen to date, allowing ppl to collaborate in solving specific requests.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote>
  • Lines and paragraphs break automatically.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.