This issue has been raised from zendesk ticket 18. See https://iati.zendesk.com/agent/#/tickets/18
We need to include additional fields within the schema to better describe the role of a publisher who is publishing data on behalf of others. The Activity files needs to support secondary publishers. There are three scenarios that need to be covered:
- Aggregator publishes a donor activity that it has imported (unchanged) from another aggregator
- Aggregator publishes a donor activity that it has imported (unchanged) from the donor
- Aggregator publishes a donor activity that it has imported and modified
(Originally reported at https://github.com/IATI/IATI-Schemas/issues/43)
This proposal has been archived as it is not being taken forward in the version 2.02 upgrade of the IATI Standard.
This item has been moved to the '2.02 Decimal Upgrade Proposals' forum for inclusion the upcoming decimal upgrade.
In my opinion publishing data on behalf of others make the processing of the data for real world purposes very complex. The need for an additional field in 2.02 illustrates this. It also makes it unclear who is responsible for the data quality of the published data.
Therefore I sincerely doubt if the IATI standard should futher support the publication of data for which you are not the owner. The examples of Ben Webb above clearly illustrate the kind of complexities you have to deal with when you are going further along this road. Is the cure not worse than the disease?
I think that the existing reporting-org/@secondary-reporter flag is now sufficient.
What we are still lacking is a means of discovering data published by a secondary source that is not available from a primary source. For example there are some activities reported by UNOCHA's Financial Tracking Service where the donor or agency does not report to IATI. How to we find these 'non-duplicates'?
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 do not plan to include this in the upgrade at this time. As noted above, the reporting-org/@secondary-reporter attribute already exists within the standard.