Migration of OrganisationRegistrationAgency codelist to Org-id.guide (included 2.03)

This proposal is part of the 2.03 upgrade process, please comment by replying below.

Activity and Organisation

**Schema Object** All elements containing an organisation/@ref

**Type of Change** Codelist management

**Issue** All organisation and activity identifiers must be prefixed with a code from the IATI-maintained OrganisationRegistrationAgency codelist. As the result of collaboration between IATI, Open Contracting, 360 Giving and OpenCorporates administration of this list will be transferred to the jointly governed http://org-id.guide.

**Proposal** For information only. There is no change to the standard.

**Standards Day** No information available

**Links** Previous discussions - https://discuss.codeforiati.org/t/tech-paper-codelist-management/538/4

Since the org-id methodology seems to support multiple lists of org id’s, isn’t there a risk that the same organization is being referred to with different identifiers?

The org-id methodology is based directly on the existing IATI methodology - which already has the potential for a single organisation to be referred to with different identifiers.

What org-id.guide adds is the meta-data required to discriminate between the possible sources of identification for an organisation, and to choose preferred sources of identification.

I’m supportive of this change. It would reduce pressure on IATI to handle organisation identification requirements of other standards (which are currently deferring to the IATI list) and will open up the possibility of creating additional tooling to improve validation and quality assurance of organisation identifiers.

(Full disclosure: I wrote the original IATI organisation identification methodology, and have been working on the development of org-id.guide)

At the moment, the Organisation Identifiers methodology states that The namespace code (1) may contain a dash - and the ORA Codelist contains only codes with a single dash. The Base Identifier is then joined with the Namespace Code by a dash to create an Org ID.

Looking at the org-id list, there are some codes with multiple dashes, which is not permitted within the IATI methodology (not looked to see if there are any with no dashes, which is technically permitted but would be inadvisable).

@TimDavies Are there checks within the org-id methodology to ensure Namespace Codes may be unambiguously extracted from an IATI-format Organisation Identifier? For example, if there is a code AE-AJ-CR, there may not be codes AE or AE-AJ, but there may be code AE-A or AE-AJ-C.

Along this point, this proposal does change the Standard because (assuming values currently present in the org-id list are permitted), it changes the permitted format of a Namespace Code.

@Hayfield Thanks for flagging this.

This is a really good point. The AE codes were imported from
OpenCorporates, and are not yet in the confirmed list - but I believe we
had wrongly cleaned up some Canada codes on a branch to be CA-MB-MBT for
example, when this should be:


I think here we need to clarify the methodology so that:

  • First two digits are national jurisdiction
  • If a sub-national jurisdiction is used, this may be given following _
  • The abbreviation of the list should be provided following a dash

When back online I’ll check that the master branch is consistent on this
for all confirmed codes, and will look at getting the AE codes updated too.

This topic is primarily for information purposes only. It has been included in the formal 2.03 proposal to allow for the modification of the @ref definition.

1 Like

Notes from consultation calls w/c 3rd July

The IATI technical team explained a bit more on the process for transition to org-id.guide and clarified that there will be no change to the structure of the IATI organisation identifiers.

The proposal was reviewed by those on the call and there was no objection from the group.

To be able to do proper data validation on usage of existing registration agencies, the full list of registration agencies should be available in a machine readable format, preferably the default IATI codelist XML format ( http://iatistandard.org/202/codelists/downloads/clv3/xml/OrganisationRegistrationAgency.xml ).

Example on this validation being applied; http://www.iatibugtracker.org/datasets/2951

@TimDavies is there such a list available from org-id.guide ?

@VincentVW Yes - org-id.guide will output IATI codelist XML format.

1 Like

Awesome. The current list seems quite incomplete so I’m looking forward to this.