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