[Feature request] allow uploading an IATI xml file rather than typing in each activity-id

[matmaxgeds]

I am guessing that a use case is that publishers prep a draft IATI xml file but as the validator does not currently check for ID conflicts, this would allow them to quickly check a whole file before clicking go on publishing it.

[stevieflow]

@matmaxgeds yes, I think this is a good use case

For info, I've been looking at this idea via: OpenDataServices/cove#1339

I think we may find some overheads and difficulties in doing this though - as in, what if we want to check a file with thousands activities, each with external identifiers (in the relevant elements*)

We'd then want to think about not only how to handle those requests, but also the return to the user (esp if there is a fail)

All good stuff though. I think @HermanvanLoon is also interested in such ideas

*relevant elements:

participating-org/@activity-id
transaction/provider-org/@provider-activity-id
transaction/receiver-org/@receiver-activity-id
related-activity/@ref