@IATI-techteam is this guidance also going to be added on the website sometime in the near future? Do you want a pull request from me to do this?
Bumping this. I found the relevant bit in the standards day notes (rows 102 and 103):
Proposal: Deprecate the BudgetIdentifier codelist
Discussion: Consensus as codelist has been replaced by expanded CRS Purpose codes
Proposal: Remove reference to the
BudgetIdentifiercodelist in the definition of
Discussion: We would deprecate at 2.03 and remove in integer, although it was noted that there is no process on the deprecation of individual elements. Comms would need to be provided to publishers about this, perhaps as separate guidelines.
I’m not sure what happened with these, but @stevieflow is right in pointing out that neither has been actioned in v2.03.
Relatedly, the aid and budget alignment guidelines were bumped to v2.03, but haven’t been added yet.
One concrete consequence of this not being actioned is the recent report by Cohen and Mekuria that is based on the Budget ID codelist rather than the expanded CRS codelist. That’s a missed opportunity to see what IATI can tell us about aid flows to a specific country.
This is not correct.
If you read the acknowledgements in the report you will see that the methodology was written by Simon Parrish. This would have been before the agreement by WP-STAT of new CRS purpose codes.
The methodology was written by Simon, but the report itself is more recent, having been published in January 2018 (thus presumably written in 2017). Though it does refer to the “common code” as a recent proposal, which is very confusing.
In any case, clearly marking this codelist as deprecated, as decided by the TAG a year ago, and adding the guidelines, would help avoid further confusion for both publishers and users of IATI data.
As part of the Version 2.03 upgrade the Budget Identifier Vocabulary codelist was changed from being embedded to non-embedded.
The plan has always been to implement the deprecation of Code 1 in this list as part of the standard procedures for making changes to non-embedded codelists.
If I could add a personal note on this: It seems to me that a number of comments on this issue are getting close to the limit of what might be called “polite impatience”. Give us a break folks!
[Approved] Mark IATI (`1`) as withdrawn in BudgetIdentifierVocabulary codelist
Gah… Polite impatience is exactly the tone I aim for. Apologies @bill_anderson.
Great! I didn’t see a github issue for this, so I’ve created one:
UPDATE: I think this pull request ought to fix the second accepted proposal mentioned above.
I also want to bump this thread. I am really trying to be polite and patient but we will be celebrating this thread’s first birthday in one month – would be great to know how we can move this guidance forward. Is there a reason why it is taking so long to add this to the IATI website?
@IATI-techteam @petyakangalova @bill_anderson would you like a pull request for adding this guidance the IATI website? I am happy to provide. Please let me know (also if there is anywhere particular you would like it to go).
I’ve written a blog on this topic:
It includes a graph of all (more than 1 million) IATI activities, grouped by their 5-digit DAC sector code:
A large number of activities use sector codes that can’t be aligned to recipient country budgets. A good first step to addressing this would be to get this guidance published.
Hi @markbrough Apologies for the significant delay in adding the guidance. I have now submitted a pull request for the guidance- please have a look and let me know if any changes are required, so that we can approve and merge next week.
This guidance has now been published by @IATI-techteam live on the IATI Standard website:
Now that this guidance is finalised and live, it would be great if:
- publishers can take a quick look at the guidance (it is pretty short and clear) and see what steps they could take towards making their data more useful as part of the budget process at country level;
- organisations using the data can look at how they could stand to benefit from using this data, and how they can begin to integrate into their own systems.
Many thanks to @petyakangalova and @IATI-techteam for getting this on the IATI Standard site, and to all of the organisations involved in the many years of work to get us to this point, particuarly Canada and @YohannaLoucheur .