Tag Archives: freedom of information

Better local government through open data

Local government seems to be in a perpetual state of competition – while the most efficient use of resources would be to collaborate. So how could open data help facilitate that?

 

One attendee talked about formalised co-ordination roles. There have been some pockets of good stuff: the Cabinet Office nominated over a dozen councils as their open data champions, with some mixed results. Redbridge’s data sharing platform DataShare, part funded by the LGA, seems to be well-liked by those who have used it. Some other user authorities are using it – but it’s often not as well implemented as the Redbridge implementation.

Continue reading Better local government through open data

Crowdsourcing the perfect FOI request

Warning: Liveblogging – prone to error, inaccuracy, and howling affronts to grammar. This post will be improved over the course of a few days.

Gaia Marcus has been working on a dashboard to show the scale of youth homelessness in the UK. It’s not necessarily just street homelessness – that’s fairly unusual in this country. There are plenty of other, more common, kinds of homelessness.

There are a whole range of problems with getting data via Freedom of Information, including tine restrictions, format issues and the dreaded PDF response. To counter that, they’re building a form for an FoI request that seeks to shape the request in a way that deals with those problems.

This is part of a campaign to get bodies to report this data better. They tend to both store and share it in a deeply static format right now – we need to get it in a more open, useful format.

The Human Factor

The discussion focused around dealing with non-expert FOI recipients, who need as much help as possible to produce a quick, useful response. Here’s some key points from the discussion:

  • How deeply should we ask for specific formats? Yes, we should probably ask them to return it in the spreadsheet we sent.
  • Excel versus CSV? Some preference for CSV, but there are good reasons for going Excel – familiarity is one, for example. Google Docs is out due to restricted access. Maybe Excel for those who can’t and CSV for those who can…
  • In extremis you could use SurveyMonkey or Google Docs to allow people to fill in the data directly for you. It does introduce a risk of human corruption of data – but that’s the risk at every stage humans are involved.
  • You should also specify that it should be published as open data on the website – and that saves you the cost of future FOI requests. There’s allegedly some research from Leeds City Council that their FOIs went down since they’ve started publishing Open Data. No-one here’s seen it, though.
  • In case of refusal, is capturing the reason why they can’t fulfil the request useful? The consensus seems to be “yes”.
  • We need to confirm the licence of the data – and ideally it should be Open Government Licence (and you’d need to link to an explanation of that). That way you could publish the data yourself, which you can use as part of a cost argument (fewer FOIs, because we publish this as open data for you).
  • Reference similar requests and highlight why what you’re asking for is significantly different.
  • Beware being classified vexatious by overwhelming authorities with requests.

Here’s the working document used to capture the FOI session input

11 Horror Stories of Open Data

A cathartic session of data ranting, where Open Data Camp attendees shared their data horrors under the Chatham House rule:

Horror: A PDF full of screenshots

Looking for the location of fire hydrants? If you make FOI requests, you’ll be told they’re national security, or private data or… One council did send the info – but as a PDF. And in the PDF? Screenshots of Excel spreadsheets.

Lesson: Ask for a particular format…

Horror: Paved with good intentions

A government ministry was asked for its spending data, but had to be fought all the way to the Information Commissioner, because they argued that they had intended to publish, and that was enough to give them leeway not to publish. he Information Commissioner disagreed.

Lesson: Just saying “intent” does not let them off the hook

Horror: Customer Disservice

An angry Twitter user asking about his broadband speed was sent a huge dataset of broadband speeds by postcode, as a zipped CSV. And was a bit cross when he realised he couldn’t use it. So a member of the organisation helped out by creating way of reading it – and got told off by his manager for helping the public.

Lesson: No good deed goes unpunished.

Horror: The art of the inobvious search

Googling a list of GP locations, they found an NHS search service – no place to download it. ONS? 2006 data. It took her getting angry, walking away from the computer, and coming back and making a ridiculous search to find it. If you aren’t make it accessible, why bother?

Lesson: Just creating data isn’t enough.

Continue reading 11 Horror Stories of Open Data