Thanks @matmaxgeds and @andylolz for your comments. We have provided responses to your points below, which hopefully answer your questions. Do let us know if that sounds good to you and we will proceed with adding the data removal guidance to our website at the end of this week.
@matmaxgeds in terms of how often the criteria or such cases might occur, the answer is that there are very few (we don’t have an exact estimation). But it is important to have the guidance out there for publishers when needed, even if there are few cases.
In all cases, if the publisher stopped hosting the file, within 24 hours, (or a tiny bit longer if tools are caching), the data would be removed anyway?
Yes, that is correct. The guidance is there to make this clear to the user.
It also doesn’t seem sensible to me that so many of these features are built into the registry - that seems to add another layer of complexity compared to a publisher just removing the offending file from where they host it? Or is this difficult for some publishers?
This is a sensible point, but the guidance follows current processes and we need to make it clear to the publishers how the IATI Registry works and what options publishers have if they want to remove data. If there are changes to the Registry, then the guidance will be updated.
@andylolz this guidance is on data removal, which is separate from data retention, which sets policies on, for instance, how long a dataset is retained for in a specific application. We have mentioned that we can look at this in the future, but at the moment the priority is on data removal. We decided not to include guidance for third party applications as they are out of our scope of responsibility.