I use d-portal a lot - it’s very helpful to find good data, I find
I wanted to share this recent insight that digs into how the standard is implemented, and what this means for a) a data use project such as d-portal and b) a data user using a data use project!
This might seem quite a minor aspects of the standard, but I think interesting nevertheless, and they certainly have an impact on the end use. Many thanks to shi at d-portal for the prompt replies and actions
When we describe an organisaton with a org reference, should we include the name too?
When looking at one activity, I was presented with the following:
As much as I like organisation references, I dont think I can recall who NL-KVK-41198677 is !
The reason for this , is that the publisher had not included the org name in the XML:
<participating-org ref="NL-KVK-41198677" role="2" type="21"/>
<participating-org ref="XM-DAC-7" role="1" type="10"/>
<participating-org ref="NL-KVK-41198677" role="4" type="21"/>
Hence, d-portal couldnt tell us the name of the organisation, as it wasnt in the data.
Thankfully, shi found a solution, and we now have:
But - the fact remains that this data (and no doubt others) misses the org name. This would potentially cause headaches for data users.
Do we therefore insist on the name being included in the XML? Or … is there a need for a central look up of references, which isn’t as straightforward as it might seem.
But, at the publisher end, it probably makes sense to keep things simple, and avoid repetition, particularly is you are talking about the same organisations time and again. We only need to say NL-KVK-41198677 = Hivos once, right? After all, we want the machines to read the machine-readable data?
Any thoughts welcome
Would be interested to know more —> Vincent van 't Westende ?
I think the wider issue persists though - publishers are having to repeat the same thing again and again in their data – and that seems because humans are reading it (whether in the XML or via d-portal, for example)…
Ah yes that is a bug and we’ve got an open issue on OIPA to fix that. [short explanation as to whats wrong] It now looks at the Organisation file -> name element and if that is missing (or invalidates) it should fall back (but doesn’t) on displaying the publisher activity -> reporting-org narrative or IATI registry publisher name ( We might make the latter the preferred name since it always exists ).
To get more back on topic: totally agree that we can’t avoid using participating-org narratives for all organisations that do not publish yet for the reason that we can’t validate the name with the ref.
A ‘do not repeat yourself’ solution would be to make it mandatory to report all the orgs you name in activities in your organisation file (that’s already possible atm right?). Not sure if that makes things easier for publishers nor developers though. It would increase consistency in naming.
A central lookup using org-id.guide sounds like the best option to make it easier both on ‘search a org ref’ and ‘auto ref to name lookups’ in IATI visualisation tools. Also would be easy to integrate in publishing tools that use a CSV to IATI approach (pivot tables?) and AidStream. Any big issues with feasibility on this that you ran into at MA discussions Andy Lulham Steven Flower ?
In case anyone is curious, this is how we do it:
Using the IATI Registry API - we suck down all the publisher metadata.
You can find it here - this list is updated nightly-ish.
Refining the data from here is, of course, an obvious and easy step; ie. turn publisher_iati_id into the org list.
Bonus points - Since this is under source control, you can see the history of changes in the IATI Registry over time.