IATI Consultations Archive

Live discussions and consultations can be found at discuss.iatistandard.org.

Broadening sector codelists

Background
Reporting organisations can use whichever sector codes they want
They should also be encouraged to publish data using their own internal sector codes as they are likely to be more precise and accurate than the DAC sector codes (e.g. WB Themes and WB Sectors; DFID sector codes)

Problems
Using different codelists presents significant challenges (or barriers) to re-use of the data, especially if the entire codelist is not public.
Donors are encouraged to use the “RO” vocabulary code if they are using their own codelist. Does this make it harder for this to be used (as opposed to putting something more unique to that codelist in the vocabulary code)?
It would also make the budget identifier much more straightforward if both reporting organisations and info-/intermediaries could take a reporting organisation’s sector codes and map them across to recipient country budget classifications.

Proposal
All reporting organisations should publish a comprehensive list of their sector codes (text and code), if they are using their own internal code lists.
Perhaps:
reporting organisations should map this list of sector codes to the DAC, or another common set of sector codes?

 

Proposed by Mark Brough

Have more questions? Submit a request

6 Comments

  • 0
    Avatar
    Bill Anderson

    RO seems to adequately cover this case at the moment, so this will not go forward to a decimal upgrade.

  • 0
    Avatar
    IATI Tech Team

    This item has been moved to the '2.02 Decimal Upgrade Proposals' forum for inclusion the upcoming decimal upgrade.

  • 0
    Avatar
    Bill Anderson

    I recommend we drop this

  • 0
    Avatar
    IATI Tech Team

    This proposal has been discussed amongst the IATI Technical Team following the end of the initial suggestion phase of the v2.02 upgrade.

    The IATI Technical Team do not plan to include this in the upgrade at this time, on account of existing sector codes.

  • 0
    Avatar
    Scott Stewart

    Agree migrating existing sector codes will be problematic--we (AidData) try to map to DAC5 for all the datasets we produce. This mapping can be non-trivial and in some cases probably mask a richr codelist. In the end, we decided comparison was of higher value..

     

    Also the nascent SDG methodology we have developed requires a DAC5 purpose code. Sending John and Bill the methodology under seperate cover today/tomorrow.

  • 0
    Avatar
    IATI Tech Team

    This proposal has been archived as it is not being taken forward in the version 2.02 upgrade of the IATI Standard.

Please sign in to leave a comment.