(Added) Rules for reporting multiple countries and regions - proposed bug fix

(Amy Silcock) #1

Issue

In the activity standard and surrounding guidance it is unclear whether or not recipient-regions from different vocabularies are included within the 100%.

For the example below:

  • If the reported region vocabulary makes no difference, then the percentage total equals 150% which is invalid
  • If the reported region vocabularies are treated separately. Then country + region percentages equals 100%, which is valid.

<recipient-country code=“AF” percentage=“50” />
<recipient-region code=“489” vocabulary=“1” percentage=“50” />
<recipient-region code=“A1” vocabulary=“99” percentage=“50” vocabulary-uri=“http://example.com/vocab.html” />

There’s been some discussion on GitHub about this already: https://github.com/IATI/IATI-Extra-Documentation/pull/516

We propose that the latter option should be implemented as a bug fix.

Solution
To make it clear that vocabularies can be used independently of each other, we have made text changes to the rules in the IATI activity standard, changed the guidance for recipient-region and recipient country and updated the overall geography guidance. These proposed changes can be seen on GitHub and are linked to the following issue:

Use cases:
Organisations may need to report using different region vocabularies for different stakeholders. E.g. UN CEB requirements require publishing using the UN region codelist, and their DAC reporting requires use of the OECD DAC region codelist.

Organisations may need to report using the OECD DAC region codelist as per their grant agreement. However, internally their region mapping is different and would use the vocab option 99 to demonstrate their own regions based on partner networks

Who would be affected?
If this bug fix goes ahead, it means that the rule will be included in the IATI validator.

I can find one organisation which has one activity that would be breaking this rule:

The IATI tech team will get in contact with them to let them know of the change and what changes are needed to their data.

Next steps
If there is no objection to this bug fix within 7 working days (excluding bank holidays for Easter) we will implement the changes. This will include version 2.01, 2.02 and 2.03 of the IATI Standard. If objections are raised we will go into consultation about how this issue should be resolved.

(Amy Silcock) #2

As there has been no objection to this fix on Discuss nor on GitHub, the IATI Technical Team will implement this fix.

(IATI Technical Team) #3

This fix has now been implemented

(IATI Technical Team) closed #4