Miami Open211

Project Info

Users' URL
https://miami-ohana-web-search.herokuapp.com
Developers' URL
https://github.com/code-for-miami/ohana-web-search and https://github.com/Code-for-Miami/ohana-api
Stage
Prototyping: Something is being built
README

We're working with Switchboard of Miami and the Open Referral Initiative to create Miami Open211: a platform for directory information about all of the health, human, and social services in our community.

Switchboard of Miami operates Miami-Dade's 2-1-1 call center, through which people in need can call to get referrals to services that can help them.

Switchboard has agreed (as an experiment) to deploy their data in an open platform that can be accessed by external tools and applications. (They'll be one of the first 2-1-1s in the country to do so!)

Read more about the Miami Open211 project here in this blog post. To read much more, check out this memo.

In the first phase of this project, we are going to experiment with the Ohana API.

Already done:

  1. Transformed a demo package of Switchboard's 2-1-1 data into the Open Referral format. Github repo here

  2. Deployed Ohana API (Ruby on Rails)

  3. Loaded transformed 2-1-1 data into Ohana (as per these instructions)

  4. Deployed the Ohana Web Search front-end as a demo.

  5. Got funding to ramp up these experiments!

  6. Deployed a developers' portal for the API

Next steps:

We are in the Code for Miami Slack Team under #open211.

This project is part of the Open Referral Initiative, which convenes in this Google Group. Email bloom@openreferral.org to request an invite to the Open Referral slack team.

Background on Open Referral: The Open Referral Initiative is working to make it easier to share and find information about health, human, and social services. We are supporting local pilot projects in which diverse stakeholders are establishing interoperability between human service information systems (i.e., enabling different systems to "talk" to each other). Our objective is to demonstrate the value of making resource data openly available in a standard format.

Project Activity

Update #8

Our developer's portal is up! http://miami.open.211.adopta.agency/

Posted on by Greg Bloom

Update #7

Our project is ramping up! Check out the new post from @ernie: Welcome to Miami Open211

I've updated the project summary above. Key stuff:

Next steps:

We are in the Code for Miami Slack Team under #open211.

Posted on by Greg Bloom

Update #6

We made great progress over the weekend: a demo website is up! Check it out: https://miami-ohana-web-search.herokuapp.com

A bunch of issues listed here: https://github.com/Code-for-Miami/ohana-api/issues/2

@eddroid posted this update on slack:

For those of you interested in this project, here's an update.

The Open211 JSON API from 2 hackathons ago is still up and running - Code For Miami Heroku: https://miami-open-211.herokuapp.com/api/ - Code For Miami GitHub: https://github.com/Code-for-Miami/ohana-api

This week I've imported more Switchboard data into the API. In particular you may notice more contact information.

I've merged a few separate repos into CfM's Ohana API repo to make things simpler: - Switchboard's original CSV data and our data mapping proposal is now available at https://github.com/Code-for-Miami/ohana-api/tree/master/data/switchboard - My code that imports Switchboard's CSV data into the API database is now available at https://github.com/Code-for-Miami/ohana-api/tree/master/lib/switchboard - A new rake task "rake switchboard:import" was added at https://github.com/Code-for-Miami/ohana-api/blob/master/lib/tasks/switchboard.rake to trigger the import process

Dployed the Ohana Web Search app: - My Heroku: https://miami-ohana-web-search.herokuapp.com/ - Code For Miami GitHub: https://github.com/Code-for-Miami/ohana-web-search

Miami's Ohana Web Search app talks to Miami's Ohana API app to pull data and display it in a human-friendly format.

Create issues if you find bugs or want to suggest enhancements. - API issues: https://github.com/Code-for-Miami/ohana-api/issues - Web Search issues: https://github.com/Code-for-Miami/ohana-web-search/issues

This issue in particular encompasses many separate issues: https://github.com/Code-for-Miami/ohana-api/issues/2

Posted on by Greg Bloom

Update #5

Hi folks, I'm hosting a video chat with Catalyst Miami on March 26th at 3pm about the project. Others might be joining up as well.

RSVP here: https://plus.google.com/events/ci5s2r5mc59fgld6loqaliv6hhs

It would be great to be joined by someone from the Code for Miami team who is working on this project (though not a big deal).

Also, I'm hosting a general Orientation next Friday at 3p, just a general overview of the whole initiative — not for folks who are already involved, but if you know someone who should be involved and would like to learn, please share with them: https://plus.google.com/events/coqeovlhfc1l3i99ajuot40o3us

Posted on by Greg Bloom

Starting at CodeAcross

I’ve coped the repo to https://github.com/Code-for-Miami/ohana-api , and made a handful of starter issues to hopefully tackle today. Please bug me (I’m in the northeast corner of the room in a black shirt, @bryce on slack, etc.) if you need access to the github or slack or whatever :)

Read the full article on github.com »

Published on , shared by Bryce Kerley on

Update #4

Good news: Thanks to the efforts of Chris Scott (@cyberstrike) and Ed Toro (@eddroid), plus our intrepid brigade leaders, we have deployed the Ohana API and loaded a bit of Switchboard's data into it.

Visible here: https://miami-open-211.herokuapp.com https://miami-open-211.herokuapp.com/api/organizations https://miami-open-211.herokuapp.com/api/locations

Ed's forked OhanaAPI repo with mods is here: https://github.com/eddroid/ohana-api

Raw data (not human readable, for use with pg_restore): https://github.com/eddroid/ohana-api/blob/master/data/ohana_api_production.dump

Ed says: I haven't pushed up my scraping code, but it'll go here when it's cleaned up: https://github.com/eddroid/Miami-Open-211

Steps moving forward:

1) Check Ed's first take at field-mapping with Switchboard's tech team. (underway - @greggish)

2) Post and review data-munging code (underway - @eddroid)

3) Transfer into a more official CodeForMiami Heroku account, preferably one validated with a credit card because certain features won't work without it (next step - @rebekahmonson?)

4) Customize front-end of API module (next step - @greggish can help with text))

5) (maybe for CodeAcross) Deploy front-end Ohana Web Search and modify for Miami.

6) scope possible use cases (!)

If all of the above looks good, let's modify the main Code for Miami Open211 README accordingly.

Posted on by Greg Bloom

Update #3

Relevant to this project: the Ohana team posted a page specifically about taxonomy - this might not answer all of our questions but it's a start: https://github.com/codeforamerica/ohana-api/wiki/Taxonomy-basics

Posted on by Greg Bloom

Update #2

I have data! Pls email me at bloom@codeforamerica.org and I will share.

Posted on by Greg Bloom

Update #1

FYI, forgot to mention: I'm hosting a series of video chats this Friday (in the 11am-2p range) where we'll be discussing different aspects of the initiative. It'll be on Google hangout, RSVP here

Orientation for newbies is at 11am, we'll probably be discussing the spec around noon, and the API around 1p. This is all extra-curricular, totally optional, just if you're interested in hearing more, seeing others involved, and asking questions. Lmk if you're interested.

Posted on by Greg Bloom