@KateHughes thanks a lot for the reply! While I appreciate you may not have any more information for us right now, I do want to second @matmaxgeds concern – this is something we have been raising for over one year and have never actually had an answer to.
My assumption was that that radio silence meant that the new Datastore would ensure that existing systems using IATI data via the Datastore would not break. For example, the Bangladesh AIMS has been importing IATI data for about 3-4 years now using the IATI Datastore. I’m not involved directly with it anymore, but I know that it is still working and frequently importing/updating data via IATI. This is great, and something that we should be encouraging, rather than breaking systems at country level and forcing them to spend money and conduct procurement to get the system working again. Probably in some cases, the country will just give up.
So I really do want to emphasise the importance of getting this right and maintaining compatibility with existing endpoints to ensure we are not quite significantly harming efforts to use the data at country level. We really do need to have stable and reliable central infrastructure if IATI is going to work.
@siemvaessen, I think forced pagination will also be a problem, because that is not the way the existing Datastore works.
UPDATE: I also just remembered that this was included as a recommendation in the technical audit:
Where possible, maintain consistency in API endpoints between the old Datastore and the new one, to avoid breaking existing applications.