Hi all. I’m here as part of a revamp of openeconomy.org.au in which I propose to replace the existing backend with OpenSpending (the next generation). OpenEconomy is slightly different from other OS-style projects in that it’s not really a transparency project driven by budgetary organisations, but a “tool for winning arguments” that lets you compare different organisations (and parts of their finances) against each other.
It’s also somewhat unique in that it covers the spread of revenues/expenses/assets/liabilities, and has a certain visualisation style that lets you visually characterise an organisation (eg, high debt but high revenues, or balanced revenues/expenses etc).
Anyway, in order to use OS as the backend, obviously OS would have to support assets and liabilities in the data model. Rufus and Paul have given their cautious support to this idea but want more details, and sample data.
I’ve uploaded all the sample data here: https://github.com/stevage/openeconomydata/tree/master/hjson
My general plan of attack from here would be:
- Work out how to represent assets/liabilities in OpenSpending Data Package
- Convert existing data to that format
- Build datavis and site around that format (well, a colleague will be doing this)
- Temporarily store that data in Github if OS Next isn’t ready
- When OS data store and API is ready, switch over to using that, moving the data there and hooking into its API
- Explore how the worlds of OE and OS can mesh more deeply - ie, can our new vis be useful to other communities, and can the existing data be useful for comparisons etc within OE.
But right now, let’s talk about 1.
- Has this been discussed before?
- Are there any big blockers to doing it?
- What would need to change in the data model?
- Does anyone else want this?
- Any objections?