Welcome to Code for IATI! This website (and corresponding Github page) has been set up to bring together tools and techniques that members of the IATI community regularly make use of when working with IATI data. Some of the tools are solving quite specific or niche problems, but many others are commonly required for interpreting IATI data or for building tools that use IATI data.
By bringing them together in one place, with a brief description of each, we hope to make it easier for us all to share and discover these tools, as well as to sustainably maintain them.
Examples of tools so far
- Replicated codelists: A nice (bilingual) interface for accessing up-to-date third-party codelists used in IATI data, including historical withdrawn codes.
- Exchange Rate Calculator: an online exchange rate converter for historical exchange rates, from the OECD and US Federal Reserve (the underlying data is also available to download).
- Org ID Finder: A tool to find organisation IDs of publishers in IATI data
- iatikit: A python toolkit for using IATI data
Who is Code for IATI for?
Code for IATI is for anyone who finds these resources useful or stands to benefit from using IATI data, and for anyone who would like to contribute and share their own resources. That means both technical and non-technical users. We’re very keen to work with other developers in terms of building and maintaining tools - and that will likely be a big focus initially - but our goal is to build tools that are ultimately useful for non-developers, in order to make it easier to use IATI data across the board:
- to ensure tools are useful, we need a lot of input from those working in policy environments - that could mean anything from detailed knowledge of the meaning of individual codelists to a more high-level strategic vision of how information can help solve problems in the way development cooperation and humanitarian aid is delivered
- to communicate between the technical and policy levels we also need writers
- to translate resources into different languages we need those with language skills (starting with French, but we’re keen to expand to other languages, preferably with some thinking about how we would maintain multiple languages going forward).
How Code for IATI works
Code for IATI is practical and positive. We want to make and do things, and we want to encourage others to make and do things, but we don’t volunteer other people for work. Is there something that doesn’t work the way you would like, or something you would like to exist but doesn’t? Great! Dive in and be the change you want to see :)
We also want it to be fun. There’s an enormous amount of potential of IATI data, and a lot of people in the IATI community with great ideas. We will encourage anyone to do anything they want to with IATI data, and will give open and friendly advice.
We hope that new tools will be added regularly and anyone can submit them. We’re happy to list them here (or include them on the Code for IATI Github repository as requested) as long as they are open source, somehow related to IATI data (even loosely), and interested in collaboration in some form (note, we also have a Code of Conduct).
Sounds cool! How can I get involved?
Well, it’s up to you!
- Want to chat? Join us on IRC: https://webchat.freenode.net/#codeforiati
- Want to talk? Join us for the (approximately) monthly community calls (we’ll announce the next one on IATI Discuss, on IRC and on Twitter)
- Want to suggest improvements or flag issues with tools? Add them on Github
- Want to suggest a new tool or idea? See all existing ideas, or create a new issue here
- Want to to email us? email@example.com