1. Data sets. Maybe it's time to do our own scorecard on which
departments are dragging their feet. At some point, the web dev folks
can only put up what each department's public servants release. The
DataSF departmental scorecard was a recommendation in one of our
position papers. We should check in to see where on the development
backlog said scorecard is; perhaps Matt knows if the Socrata software
platform that powers the portal might be able do due this if a
configuration 'switch' is turned on.
We should also have a strong question about this in this season's
candidate questionnaire.
We also need to do a better job as OpenAustin (or at least I feel I
personally do!) of conveying to the non-tech City staff that we can't
build the Austin civic hacker community if there's no data and no
urgent problems they want to collaboratively solve through the types
of tools open data-powered software can build. I think the CfA
hackathon will be inspiring and move us forward, but we've got to as
an organization keep advocating for things that will institutionalize
open data and open government moving forward. The resolution and
empowering of CTTC are good steps. Perhaps we need an Innovation
Officer/Urban Mechanics initiative/Chief Digital Officer that is
closer to the City Manager and empowered to internally advocate these
priorities as their no.1 responsibility.
On a related track, we need to push collaboration between the City and
CapMetro if we are going to catch up to other towns on transit tech.
You are muck more knowledgeable about transit than myself, so I look
to your leadership on this.
2. Open Austin to Open Government. I think I raised this either in
the facebook group back in the day before the google group or on this
one and the limited feedback I got agreed that having the CoA portal
have our group name would be confuse our different missions. I agree
with that reasoning but have an open mind if you think this was the
wrong way to go...
JGA
Thanks for the quick response,Mateo.
I will compile a list of (mainly transportation-related) datasets that I would like to see added to the portal.
Thanks for the quick response. Would you know if there's a Socrata
person that might know if one of there client's out there has already
utilized the SODA API to build an web app that reports a department by
department count of data sets? I am looking for a civic app project
that's simple and has quick impact and this one seems right up my
alley!
Julio
Julio,
Tomorrow morning, I will begin asking @austinmobility & the transit community for ways that we can help staff get important datasets onto the portal. Jacob has always been more than helpful in gathering and sharing any information requested; way more than other dept staff, IMHO. I will also try to contact CapMetro to get the ball rolling on that side. I'm not sure how it's going to work with CapMetro, as they're not directly under the City of Austin.
I completely agree w the decision to change the tab name, just wanted clarification.
Thanks
I agree. As Vice Chair of the CapMetro Customer Satisfaction Advisory Committee, I can work to convince the other members to pass a resolution advising the Board to adopt similar policies. This, in conjunction with contacting the particular subcommittee, should help move us forward.