I’ve been taking another look at “traceability” - especially following the excellent presentation of @Herman at the TAG (https://www.dropbox.com/s/rlb4hdoicvdwztb/linking%20iati%20data%20v7.pptx?dl=0 ) -
I have put some slides together: http://slides.com/opendataservices/traceability - which centre on org references, activity identifiers and transaction encoding to link data between different publishers.
In discussion with others - a point was raised about the use of the related-activity element to express links between activity data published by different organisations - especially the use of code 5 (“Third Party”: http://iatistandard.org/201/codelists/RelatedActivityType/).
Im not sure. Checking the dashboard, nobody is using this code atm:
Regardless - would others in the community utilise related-activity to do this? One of the drivers to this would be that the only other method to express direct links between activities is within transactions. At the participating-org level this is not possible (I’ve raised this here: http://support.iatistandard.org/entries/82377659-Add-activity-id-attribute-to-participating-org-element)