It’s been a busy year at Publish What You Fund. As is traditional at this time of year, we’ve been reflecting on what we’ve achieved and what we need to do next. Here’s our quick roundup of what the team has been up to – from the influential Aid Transparency Index, and on the ground research into aid flows in Liberia and Cambodia, to developing new tools to increase access to aid and development data.
The new US Development Finance Corporation provides a rare opportunity to set up an agency from the beginning. We can learn from other development finance institutions (DFIs) as to what worked and what did not. This is an opportunity to reach higher, to innovate more, and to truly set a gold standard for transparency.
How do we balance supply and demand? We have a dilemma. How do we balance the supply of a functioning, usable aid transparency architecture with the growing demands of the numerous and increasingly competent users. How can we all ensure existing users receive the support they need to access data, and at the same time […]
The aid transparency community has a decision to make. All at once we need to raise awareness of the presence of huge volumes of aid and development finance information, and at the same time support new and existing users when they have challenges accessing it. In short, as more people look to IATI as a […]
Last week more than 150 aid transparency professionals met in Kathmandu at the IATI Technical Advisory Group meeting. Traditionally this meeting was a space for discussing the more technical aspects of the underlying infrastructure that supports the global aid transparency movement including the IATI Standard and the visualisation tools and mechanisms which support it. Today […]
Introducing IATI Decipher – A Breakthrough in Data Usability We have just launched a new tool that uncovers 22,300 strategic documents and $2.6 trillion of aid and development budgets! If you have ever tried to access the treasure trove of data within the IATI Registry’s organisation file, but been baffled by the xml code, then […]
