IATI Consultations Archive

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

provider/receiver-og - adding @type

Both these elements are missing the @type attribute. 

 

http://iatistandard.org/activity-standard/iati-activities/iati-activity/transaction/provider-org/

 

Proposal to add this attribute

 

First discussed: https://github.com/IATI/IATI-Schemas/issues/104#issuecomment-47964332

Have more questions? Submit a request

8 Comments

  • 0
    Avatar
    David Carpenter

    I think this is a candidate for 2.02 as things currently stand.

  • 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

    This could be useful in describing transactions where it is not possible (for whatever reason) to name the organisation, so I think it is a good idea.

  • 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
    John Adams

    I think this is useful. We should do some thinking on how we deal with exclusions more generally, but this is one example where we may not be able to name a supplier, but having a type at least indicates if it is an INGO, local NGO, private sector etc.

  • 0
    Avatar
    IATI Tech Team

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

     

    New attribute: Transaction/provider-org/@type

    • Addition of a new attribute to the activity standard: type

    • Example

      • Current usage:
        <provider-org provider-activity-id="BB-BBB-123456789-1234AA" ref="BB-BBB-123456789">
           <narrative xml:lang="en">Agency B</narrative>
        </provider-org>

      • Proposed usage:
        <provider-org provider-activity-id="BB-BBB-123456789-1234AA" ref="BB-BBB-123456789" type="10">
           <narrative xml:lang="en">Agency B</narrative>
        </provider-org>

    • Add definition:
      ‘The type of organisation providing the funds. See IATI codelist OrganisationType codelist for values.
      This value should be of type xsd:string.’



    New attribute: Transaction/receiver-org/@type

    • Addition of a new attribute to the activity standard: type

    • Example

      • Current usage:
        <receiver-org receiver-activity-id="AA-AAA-123456789-1234" ref="AA-AAA-123456789">
            <narrative xml:lang="en">Agency A</narrative>
        </receiver-org>

      • Proposed usage:
        <receiver-org receiver-activity-id="AA-AAA-123456789-1234" ref="AA-AAA-123456789" type="10">
            <narrative xml:lang="en">Agency A</narrative>
        </receiver-org>

    • Add definition:
      ‘The type of organisation receiving the funds. See IATI codelist OrganisationType codelist for values.’
      This value should be of type xsd:string.

     

  • 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/281

  • 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 pages 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.

Article is closed for comments.