[Added] Align Sector codelist with the latest version published the DAC

@andylolz has identified the changes that would be necessary to bring the IATI Sector codelist into line with the current DAC/CRS sector codelist.

These have been submitted to us as a pull request to the Non-embedded codelist repository.

This forms part of Andy’s sterling work to republish OECD DAC codelists in a robust machine-readable format.

As part of the change management process for Non-embedded codelists, the suggested changes are being posted here for review and discussion.

Looking at the content of the proposed changes, Andy had identified that code 15114 may have been reused (previously “Tax policy and tax administration support”, now “Domestic Revenue Mobilisation”).

Also from looking at the pull request diff, it looks like the following new codes are added:

  • 15180 (Ending violence against women and girls)
  • 23110 (Energy policy and administrative management)
  • 23181 (Energy education/training)
  • 23182 (Energy research)
  • 23183 (Energy conservation and demand-side efficiency)
  • 23210 (Energy generation, renewable sources – multiple technologies)
  • 23220 (Hydro-electric power plants)
  • 23230 (Solar energy)
  • 23240 (Wind energy)
  • 23250 (Marine energy)
  • 23260 (Geothermal energy)
  • 23270 (Biofuel-fired power plants)
  • 23310 (Energy generation, non-renewable sources – unspecified)
  • 23320 (Coal-fired electric power plants)
  • 23330 (Oil-fired electric power plants)
  • 23340 (Natural gas-fired electric power plants)
  • 23350 (Fossil fuel electric power plants with carbon capture and storage (CCS))
  • 23360 (Non-renewable waste-fired electric power plants)
  • 23410 (Hybrid energy electric power plants)
  • 23510 (Nuclear energy electric power plants)
  • 23610 (Heat plants)
  • 23620 (District heating and cooling)
  • 23630 (Electric power transmission and distribution)
  • 23640 (Gas distribution)

Thanks for this

Would be good to group (or “TAG”) some of these threads together. Over at this thread, @OJ_ shares:

So I suspect since the last IATI Sector codelist update (in July 2016), 15180 was added and subsequently revised. That would explain any apparent discrepancy.

I should restate – any work on scraping is really just a pragmatic, interim measure to ensure non-embedded codelists are up-to-date. I’d be pleased to see the DAC and IATI secretariat move towards a shared standard for metadata management, as @OJ_ describes.

Hi, great work Andy. @dalepotter I’d like to see a time limit set for consulting on and incorporating changes into the non-embedded codelists. At least for DAC-sourced codelists. The IATI Codelist Management page is unclear about how long it takes from the point that the DAC releases an update to when changes get incorporated into the IATI codelists so that new codes can be used.

1 Like

Hi @andylolz and @dalepotter,
Looks great! Hope that the updated codelist makes it to production as soon as possible, since DAC members such as ourselves are already using these codes in their project administration systems!

1 Like

Hi all. Just an update to say that I have emailed the OECD to get more clarity on the reuse of code 15114 before we proceed with any changes. I will let you know as soon as I have more information.

Ahh – so it’s possible this isn’t reuse of the same code, and is instead just a rewording. I’m afraid I don’t have the domain expertise to know! But perhaps someone else can say.

So previously, the title and description was:

15114: Tax policy and tax administration support

Support to the ministries of finance, revenue authorities or other local, regional or national public bodies on tax policy, analysis and administration (including “non-tax” public revenue).

And now:

15114: Domestic Revenue Mobilisation

Support to domestic revenue mobilisation/tax policy, analysis and administration as well as non-tax public revenue, which includes work with ministries of finance, line ministries, revenue authorities or other local, regional or national public bodies. (Use code 16010 for social security and other social protection.)

Thanks for this, @Herman! I’ve seen other examples of current DAC CRS purpose codes used in IATI data, even though they’re not yet part of IATI non-embedded codelists. If the new IATI validator is to validate codelist codes, then I suppose it’s important for non-embedded codelists to be kept in sync.

1 Like


I have now heard back from the DAC in relation to code 15114 and they confirmed that the code has been renamed (so it is not a case of reusing a code) and the name change has been approved by WP-STAT, which means that we can go ahead with implementing the new code (see information from the DAC below).

In 2016, the proposal to upgrade the dummy code 15114 for “Tax policy and administration support” to a formal code and rename it “Domestic Revenue Mobilisation” has been approved by the WP-STAT [DCD/DAC/STAT(2016)8]

I am still waiting to hear back on a few other questions we have identified following a review of the changes in the pull request. They are mostly in relation to small changes in the narrative of some sector codes. Once those have been confirmed I will post an update in here so that the pull request can then be implemented and codes updated.

1 Like

That’s great – thanks for keeping us updated, @petyakangalova!

I spotted the review of changes, and have commented to add explanations on the minor technical points I’m able to help with. I’ve also fixed one error in the pull request that your reviewer @amys spotted.

Hi all

Any news on getting the updated codes into the IATI list?

I appreciate the difficulties in terms of undertaking and clarifying this - we’ve discussions elsewhere

One thing - the dashboard currently reports that some codes are not on the IATI list, when we know there are on the updated DAC list (we know that, but others might not): http://dashboard.iatistandard.org/publisher/fao.html#p_codelists

1 Like

Second others’ comments on getting this merged.

I think this discussion raises a wider point - this codelist and several others have been out of date for a long time - this particular issue was raised almost a year ago (fixes were proposed over two years ago).

The fact that codelists are out of date means that it is not possible to rely on IATI codelists when building tools. I have to go back and make my own codelists each time or rely on scrapers like @andylolz’. This is frustrating and adds quite a lot of burden to users, when handling the data itself is already challenging.

It would be helpful if we could have some clarity on process here. Is the IATI Secretariat committed to keeping these codelists up to date, or should users be encouraged to consult the original codelists instead?

I think it would be preferable for the IATI Secretariat to do this work rather than each tool developer having to assemble their own codelists manually. I also think the Secretariat should commit to update codelists within a clearly defined time period (e.g. within one week of becoming aware of changes to codelists). I understand the Secretariat has a lot of demands on their time but I think this stuff is really fundamental to the Standard, so it should be prioritised.

Either way, it would be useful to have clarity so that expectations can be managed and we can stop having lengthy and so far inconclusive conversations about this :wink:

Hi all,

Thank you for all of your work in reviewing these changes.

The IATI tech team have reviewed and approved this pull request. We expect changes to be implemented by 9th June.

The IATI technical team contacted OECD DAC members to gain understanding into the changes. The OECD’s response to our question around code 15180 is: - “A new code 15180 - Ending violence against women and girls was introduced in 2017 on 2016 flows (DCD/DAC/STAT(2015)2/REV1”

The majority of outstanding checks relate to the use of footnotes and references within the DAC code lists. For more information about these please contact the OECD DAC.

1 Like

The Pull Request referenced in the first post of this topic has now been merged.

The values will appear on the website when it is next generated (should be later today).

As such, I have marked this topic as [Added].

1 Like