About 6 months a go I published Easy Open Data, a tool to make it easy to publish custom-formatted open data from Google Spreadsheets. The response I received was wonderful, and it has been gone on to be used by people to open up all sorts of interesting data.
This project attracted the attention Michael Roberts who works with International Development agencies. He saw that a tool like this was ideal for cash poor, time poor, NGOs who are required to publish aid spend information in the IATI standard he helped to develop. Together we put forward a funding bid for a project to develop the tool, to promote and support it’s use among the ID community. Unfortunately we didn’t receive the funding we needed.
So, that’s the past. Now I want to talk about the future.
Despite this disappointing set-back, we are both still very committed to developing the tool and promoting it’s use.
I have decided to rewrite the code base from scratch, there are a few reasons for this. Some of the feedback I’ve had from users has identified some incredibly useful features that I hadn’t considered in the initial version. To deliver these would require some fairly fundamental changes to the tool. Rather than chopping around the already messy code base, it’s seemed a good idea to start over.
I also wanted to move the product to use Google App Engine. Given that the tool leans so heavily on Google Drive, I thought it reasonable to move closer to that eco-system. Easy Open Data is written in Ruby. As GAE only supports Java, Python and Go, this would have to change. To me Python was the most sensible choice, its a common language among open data enthusiasts, with a strong data mining heritage and used in high-profile products like CKAN.
We will be publishing the tool under an open source licence (TBD, but probably MIT). At present two releases are planned.
Version 0.1 will be the first open release of the code base and is planned for November. This version of the tool will be minimally functional, in a fit state for developers to begin experimenting with, but not end users.
Version 0.2 will be a more polished, featureful, release. The first that is fit for end users. This can be expected early next year.
You can see track the development of these releases and planned features on the issue tracker on GitHub. If you have any suggestions or thoughts, feel free to add them there.
The last big development is the name. I chose “Easy Open Data” without much forethought (I’m no marketeer). But I always felt that this name fails to explain that this is a tool for publishing open data. I also felt that a new name would help to differentiate this new incarnation of the tool from the previous one.
The new tool is called Open Data Press.
“Easy Open Data” will, from now on, only refer to the legacy version.
But what of this legacy? Over the past few months Easy Open Data has attracted a reasonably sized user-base. Some of whom have made impressive use of the tool. If you are among them, I’ll be contacting you in the coming weeks. Asking for your input about the future of EOD and inviting you to join the new Open Data Press project.
Lastly, I’d like to thank everyone who’s offered their support of this project so far. I’m thrilled by how the concept has resonated so well with so many people. Your feedback has been invaluable. I’m really excited for the future of this project, and I can’t wait for you to see what we’ve got planned.