Somewhat related to my previous post (on forward data Using forward data).

Attached is the type of templates provided by partner countries to collect data for their aid management platform (AMP, AIMS). We receive such requests rather frequently, from an increasing number of partner countries. While they’re not identical, most/all templates require information such as dates, budgets, past and future disbursements.

Unfortunately, the D-Portal does not provide the data needed to fill this template. Neither does the Datastore CSV Query Builder, since we are missing planned disbursements.

As we work together to develop guidance, tools etc to promote data use, it would be good to keep this template in mind - this is a real, current need that could be filled with IATI data. (Talking here both of the donor officials who put this information together, but also country officials who use it.) The end goal is data imports into AIMS, but we’re quite a way from there.

Efforts to raise awareness and encourage use of IATI data in partner countries will be more effective when we can demonstrate how the data can help them do their work faster or better.

How best can I help my colleagues in Dar or Maputo or Jakarta use IATI data to fill this template (ie respond to partner country requests)? Or better yet, help officials from Tanzania, Mozambique or Indonesia access the data themselves? I don’t know whether it’d be better to improve the D-Portal, or Datastore, or both, or develop something else entirely. What do you think?

IATI_-Quarterly_Report_AIMS-Generic_Template.XLSX (46.7 KB)

Comments (7)



I am extremely interested in this topic.

I am currently working on the aid reporting for the AIMS in South Sudan and Somalia (and previously Mozambique and Sierra Leone) - see attached sheet example for South Sudan (very similar to Yohanna’s generic one). As Yohanna explained in her other post - for these exercises, forward data is probably of more importance than backwards data (OECD mindset vs partner country needs!). So far, the best use we have been able to make of IATI data is to identify donors/projects that we are missing.

I am very willing to test any suggestions with my counterparts (in a production environment) and provide feedback.

As with our work in Bangladesh (which is using IATI data in production - although I think not planned disbursements yet Mark Brough ), donor country office staff are likely to be the main beneficiary in terms of time saved filling these systems in. For aid recipient countries, they will want real contact details to follow up with (not just generic email addresses) and an indication of whether the data is the donor’s "official: figures and therefore reportable. Plus the usual difficulties on adjusting the FY and aligning to government budget sectors (both solvable with mappings and value-dates).

Thanks a lot for pushing on this Johanna,

MoFEP South Sudan 2017-18 data request - Template for IATI.xlsx (20.7 KB)

Yohanna  Loucheur
Yohanna Loucheur

Wonder if we can get more interest in this post - data needs of partner country officials are, after all, supposed to be THE whole point of IATI…

Real-life request received last week from a colleague:
"Our mission in Kabul (Afghanistan) has requested a list of all GAC disbursements to Afghanistan for the first six months of 2017.

We would need this information as soon as possible in response to a Government of Afghanistan donor contribution exercise."

How to respond? As far as I can tell, this fairly simple query cannot be easily answered via the Datastore CSV Query Builder. There is no way to filter projects with a given status (eg operational), or with disbursements between such and such date. I can download all our Afghanistan data to play with in Excel, but choosing one project per line doens’t work if I need details on disbursements, and choosing one transaction per row makes the data unworkable (at least at my level of skills).

There is no way to get this data from D-Portal either, except by looking up projects one by one.

What should I tell her?

Reid Porter
Reid Porter

I believe these and other similar use cases (being able to query any and all fields, and extract data + documents from the registry with no specialized skills) are being addressed in the portal that we’re working on with Tristan Vaessen , [~379], and Vincent van 't Westende from Zimmerman & Zimmerman, but that doesn’t help you (or her) now unfortunately.

Wendy Rogers
Wendy Rogers

Thanks Reid Porter and Yohanna Loucheur and you should be able to get this information from the datastore by downloading all transactions for GAC and then sorting and filtering on transaction-date and transaction-type (where type = 3 for disbursements). However, i do appreciate that you do need to be familiar with the IATI Standard to do this.

Yohanna Loucheur I’ll send you the file of data I downloaded and edited as above separately

Yohanna  Loucheur
Yohanna Loucheur

Thanks Wendy. Indeed, playing with the Excel file I had gotten to a similar point - with an additional sorting step on Activity ID to group all disbursements by project, as this is how it gets reported.

I realized in the process that one of the complicating factor for a low-skilled user is the way columns are ordered and labeled. I’m sorta used to download data in the one-project-per-line format, so got used to how the data is presented (and can more quickly remove the gazillion irrelevant columns before getting to work on the data). One-transaction-per-line arrives in a totally different order, so it took me more time to find my way around and clean the file. Would there be a way to make the presentation more standardized?

And I think we can all agree that the labels are not all that intuitive (in fact I had to check the standard for some, I had no idea what they meant). Not sure what can be done here, but it’s something to keep in mind when we send unsuspecting users to the Datastore. Perhaps someone will have a brilliant idea to make users’ life easier on that front.

Yohanna  Loucheur
Yohanna Loucheur

Bumping up this thread (which I had forgotten) as it provides user feedback that I think is very relevant to the Datastore redesign exercize.

Please log in or sign up to comment.