Record and display whether the `reporting-org/@ref` matches the `organisation-identifier/text()`

[andylolz]

The approach here differs from the one described by @stevieflow in his IATI discuss post in the sense that we record information for all organisations we find – not just the ones where the reporting-org/@ref and organisation-identifier/text() match.

However, I think I prefer Steven’s approach, because publishers are responsible for their own data. So we can take as ground truth that a self-reported organisation identifier is correct. And if it’s not correct, it’s clearly for the publisher to fix, so we could pass that work on to them (thereby making this approach more streamlined, more sustainable, while also helping to improve IATI data). For identifiers reported on behalf of another organisation, I suppose it’s a bit less clear who’s responsible.

This ticket represents a halfway house… We record and display that an organisation identifier is self-reported, but we continue to store and display all organisation identifiers we find in org files.

[andylolz]

Good demonstration of the importance of this check:

The org file for TradeMark East Africa currently reports an organisation named “DFID” with org ID GB-1. This is DFID’s old org ID – they refer to themselves as GB-GOV-1.

[andylolz]

Fixed in a777f17f24b4f9649e9f480f8c49fbb677f33062.

I’m doing this the @stevieflow way now – i.e. only listing orgs where reporting-org/@ref matches the org ID.

[andylolz]

Okay, I’ve modified this so that if the org ID and reporting-org/@ref don’t match, it’s still stored, but with self_reported=False set. The frontend now only shows org IDs that are self-reported.

[andylolz]

The org file for TradeMark East Africa currently reports an organisation named “DFID” with org ID GB-1. This is DFID’s old org ID – they refer to themselves as GB-GOV-1.

I got in touch with [support@iatistandard.org]() about this. They told me to contact the publisher directly.

[notshi]

http://org-id-finder.codeforiati.org/#UG-NGB-5914-1107

The org file for Stromme Foundation currently reports as both "DFID" and as themselves with org ID UG-NGB-5914-110. Their current org ID is XI-IATI-5914-1107.

[andylolz]

Hi @notshi, thanks for this.

This was discussed on twitter last year: https://twitter.com/andylolz/status/1049937645370007552

…and before that, on IATI discuss: https://discuss.iatistandard.org/t/getting-to-a-list-of-organisation-references-for-iati-publishers/1060/15

I don’t think there’s anything more I can do about it. I think I got in touch with support a couple of times. You are welcome to do the same, or get in touch with Stromme Foundation directly (genuinely, that would be cool as it would be cool to resolve this bug!)

[andylolz]

Their current org ID is XI-IATI-5914-1107.

…on the registry, you mean. Important to clarify this, because org IDs on the registry are by no means canonical. In this case, XI-IATI-5914-1107 does not feature on the XI-IATI list, so we can be sure it is wrong.

[notshi]

Ahh! Wasn't aware of the twitter discussion - I followed your template "The org file for xxx currently reports as xxx with org ID xxx." and thought it'd be good to raise here for posterity by adding to the closed issue.

[andylolz]

Aha, I see! Absolutely – no harm in adding it here for posterity.

I haven’t checked in on it for a while – perhaps I should send another message to try and get the issue resolved.

[notshi]

Would be good to have a template email to send to publishers for issues like this. Might be helpful for citizens/journalists when they encounter data issues.

[notshi]

ps: I've sent an email to the contact (May Kamoga) - hopefully, something comes up.

[andylolz]

Sounds good. I’d also suggest looping in the secretariat (support@), just because it’s probably useful for there to be some centralised log of publication issues.

[andylolz]

The org file for Stromme Foundation currently reports as both "DFID" and as themselves with org ID UG-NGB-5914-110. Their current org ID is XI-IATI-5914-1107.

Since this is a data issue, it would be cool to raise it on https://github.com/codeforIATI/iati-data-bugtracker . (At some point soon, I’ll add some more explanation to that repo to make it a bit clearer what the vision is!)