Our communities are very lucky that there are so many innovative and incredibly smart people who are so dedicated to either working for government or with government to make it better.
As for the ideas discussed, from the sessions I attended people are looking for how to open data, convince the organization to embrace all of this, what the limitations or opportunities are for developing and using open source apps, and then learning about all the sites and existing apps out there that can help us.
It has been an incredible and awesome experience!!
Hi guys. I would have liked to attend this weekend's CityCamp. But from what I followed on Twitter and as Andrew sums up in his reply, I tend to agree. However, what are citizen needs? Is it about data? Really? Perhaps "data" is an insider's perspective and citizen needs still need to be defined. Or there's the risk of spending energy developing an open government strategy around an issue that the public does not embrace or identify.
I also wish I had been at the conference. I think data has to be given a context to be meaningful to anyone, let alone anyone in the general public. Data has to be linked to something, not just numbers.
For me data has to tell a story of some kind. It also can be qualitative or quantitative and is often linked to evaluation. Evaluation of what? For who and for what purpose.
When asked to "evaluate" a program, it is often seen as 'counting', we had these many people who visited our program, how many times for what. That does not tell us what happened and is not necessarily attached to the real story.
If data isn't related it can be very difficult to understand and become another barrier to public participation.
This is a subject I am very interested in discussing...I'm starting a group on evaluation.
We're onto something here. Open datasets alone are not the key.
As a grant writer, I always used data to tell a story. How many people have HIV/AIDS? Where do they live? Where are the clinics located and are they co-located with the target population?
It was never about numbers. It was about articulating need...why THIS city or this school district or this non-profit needs the money...
The same is true for cities opening datasets. Can developers transform these datasets for better visualization and planning - enabling the key stakeholders in the community to see and understand the situation and make better decisions?
If not, what's the point of open government? Transparency alone is not enough...
I feel our city's first responsibility is to make the data available. We can't compete on the web. Web development is not a culture that local government is comfortable with. The web is too agile and fast paced for local governments to concentrate on development. What are we going to do? Continue to listen to some salesperson from one of the various enterprise corporations tell us that using their proprietary web development tool is the best solution? So we spend thousands of dollars because they know whats right. Meanwhile, some 24 year old kids are cranking out websites in weeks using open source web frameworks and databases.
I love to write web applications. I'm just tired of dealing with the limitations I'm given. Both in hardware and software.
I'm more interested now in making data sets available. Lets get the data out there. Let the kids do some amazing stuff with it.
I think there are probably a few stages with opening data.
-Open up current data better
-Find more data sets
-Improve quality of data
-Improve consistency of updates of data
-Provide some user interfaces to data (some gov, some non-profit, some for-profit)
One thing I saw at times this weekend was an almost unwillingness by some people outside government to accept that from govt. perspective, it is not necessarily free or "easy" to "open" data. We aren't really talking about open data anyway in a lot of cases. Most of this data is available to the public already, just maybe not in the "ideal" form (ie, its in pdf form, or it costs money, or you have to request it by email or in person). What I noticed people talking about most was essentially real time updates/access easily accessible for free online.
For those outside govt that want these data streams, apis, etc and think its the govt's responsibility to make it available, maybe one area to look at instead of just developing applications that make use of the data- help create applications that make it easy for govt to put the data out there. Start researching the software/hardware/database setups that various departments of a govt organization use. Find out what features the govt employees need/want in order to do their job properly. Then collectively create open-source free software stacks that handle the govt needs as well as automatically provides the data exports/streams/api/etc that the gov2.0 community seeks.
You are so right on with your comment. What I keep thinking is it would help so much is to go through it in these steps which are really just a more detailed listing of the steps suggested by Steve:
1. I don't think many people, even some in govt, realize just how much data there is. It is almost overwhelming just in my department. So we really need to have a list somewhere of what data a typical city generates, what format it is typically collected in, and what format it needs to be in to be useful.
2. Once a city has a list of guidance like that which shows where we begin and where we need to go, we can start prioritizing. As you point out, Josh, no one has really focused on developing tools that allow us to go from collection/creation to publication very easily. So right now for this step we have to look at time to spend on getting this data to the format it needs to be. This can be anywhere from a day to 4 years depending on the data. (For example I had 10+ years of VCR tapes of sewer videos with paper reports - it took us about 4 months to log the videos, get them into MPEG format and the reports into pdf. That is one set of readily available raw data - two people, 4 months to get it to where we could find it and share it.)
3. Next we have to realize this data is needed for three primary reasons: first, for us to do our job, second, for other departments within our agency to do their job and third, for the public. So it would be helpful to target use groups and uses for each data set (the question of data uses kept coming up too this weekend).
4. This is a critical step that builds on the first three - prioritize the publishing of each data set based on your own agencys' ranking of time to transform data, proposed use for the data, and need by specific use groups. For example some city might decide to put out data first that only takes a few days to transform, is needed by a specific work group in that city, and will result in significant increase in economic development in the city.
5. Begin working down your prioritized list and hope that developers are also looking at these lists. Hopefully they will see where certain data sets take years to get from raw data to published data and then create a tool that streamlines the process like you suggested.
I think most of us in government want to open the data, but like you said, it isn't as easy as just walking over to it and throwing it up on a website. The problem is it is overwhelming and takes significant time, and there is no plan or guidance for how to do it and why. This process also helps establish some sense of value which increases incentive to do it. And we totally need developers help to make it so much easier.