IATI Consultations Archive

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

Org Standard - recipient-region-budget

In the same way that the activity standard has an recipient-region element, could a recipient-region-budget be enabled within the Org standard?

 

(feedback gathered via creating new org files with some publishers)

Have more questions? Submit a request

8 Comments

  • 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
    Herman van Loon

    I agree since budgets can (and are in our case) be allocated to regions.

  • 0
    Avatar
    Bill Anderson

    Agree. No-brainer.

  • 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 support this proposal.  Further updates on work towards the practical implementation of this proposal into the version 2.02 of the IATI standard will be posted as part of this thread.

  • 0
    Avatar
    IATI Tech Team

    Please see below for the technical implementation that is suggested in the Version 2.02 - Formal Proposal:

     

    New element: recipient-region-budget [MODIFIED 27-Nov-2015, with improved definition]

    • Add new element to the organisation standard: recipient-region-budget

    • Example 1

      • Proposed:

    <recipient-region-budget status="1">
      <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
      <period-start iso-date="2014-01-01" />
      <period-end iso-date="2014-12-31" />
      <value currency="USD" value-date="2014-01-01">25000000</value>
      <budget-line ref="1234">
        <value currency="USD" value-date="2014-01-01">2000000</value>
        <narrative xml:lang="en">Budget Line</narrative>
      </budget-line>
    </recipient-region-budget>

    • Add definitions

      • [Definitions to be broadly in line with those for the recipient-country-budget element together with its child elements and attributes]. Notable exceptions:

        • recipient-region: The recipient-region-budget element allows for the reporting of forward looking budgets where the organisation maintains region-wide, rather than or in addition to country-specific budgets. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient region. This must NOT include an aggregation of budgets reported in the recipient-country-budget element. It is strongly recommended that publishers report to existing defined regions wherever possible.

        • recipient-region/@vocabulary: An IATI code for the vocabulary from which the region code is drawn. If it is not present 1 - ‘OECD DAC’ is assumed. The value in recipient-region/@vocabulary should appear within the RegionVocabulary codelist.

        • recipient-region/@vocabulary-uri: ‘If the vocabulary is 99 (reporting organisation)’, the URI where this internal vocabulary is defined’

        • recipient-region/@code: Either an OECD DAC, UN region code or (if code ‘99’ Reporting organisation is selected for recipient-region/@vocabulary) a code from your internal vocabulary. The codelist is determined by vocabulary attribute. The value in recipient-region/@code should appear within the Region codelist, if the vocabulary code 1 (OECD DAC) is used.

      • See the proposed v2.02 summary table spreadsheet for full proposed changes.

    • Add guidance:

      • [Guidance to be broadly in line with those for the recipient-country-budget element together with its child elements and attributes]. Notable exceptions:

      • recipient-region, recipient-region/@vocabulary & recipient-region/@code: Guidance to be based on the recipient-region element

  • 0
    Avatar
    IATI Tech Team

    In light of discussion in the public consultation calls, the IATI technical team suggest amending the definition for the iati-organisation/recipient-region element from:

    • "The recipient-region-budget element allows for the reporting of forward looking budgets for each region in which the organisation operates. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient region."

    ...to: 

    • "The recipient-region-budget element allows for the reporting of forward looking budgets for each region in which the organisation operates. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient region. We strongly recommend that publishers report to existing defined regions wherever possible."

    The formal proposal and proposed v2.02 summary table spreadsheet have both been updated in this regard.

  • 0
    Avatar
    IATI Tech Team

    This proposal has been added as a GitHub issue, for inclusion in the version 2.02 development branch of the IATI-Schemas: https://github.com/IATI/IATI-Schemas/issues/283

  • 0
    Avatar
    IATI Tech Team

    This proposal has now been incorporated into a version 2.02 code repositories (see the above GitHub issue link for technical details). The relevant page on a development version of the 2.02 reference and documentation site is available to view here.

    We welcome scrutiny on the implementation of this proposal and encourage the community to feedback and suggest solutions for any errors, omissions and problems. This should be done before Monday 7 December, when the process will commence to release version 2.02 as a live version of the IATI Standard. More information on the inspection phase is available here.

Please sign in to leave a comment.