IATI Datastore: Redirects Testing

As you are aware, the IATI Tech Team has been working on delivering the new IATI Datastore. The tool is currently in a ‘pre-launch’ phase and will be fully released in the coming weeks.

As per previous project updates, an important requirement is that queries that are made to the ‘old’ IATI Datastore API are redirected to the new one, with the equivalent query parameters used. This will ensure that any regular queries that utilise the existing tool can continue to return corresponding data from the new tool.

Please test Datastore API redirects

We have now implemented these redirects on a test version of the old Datastore and as a user of the existing tool, we would welcome your input in this testing phase, as we are aware that your organisation makes (or has previously made) regular queries to the old Datastore.

Instead of immediately returning the results, you will be presented with the redirected query for the new Datastore. You should then run this query to check that the results correspond with your original regular query. Once the tool is fully launched, the redirected query will be run automatically, rather than just the URL being displayed.

It is important to note that we do not expect the number of activities that are returned to be the same when an equivalent query is made using the two different tools. The new Datastore does not import data that is published at version 1 of the IATI Standard or datasets that do not conform to the IATI Schema.

Provide feedback by 15 June

Rather, we would appreciate your feedback on whether the parameters translate correctly, and that the data that is returned corresponds with these parameters as expected. Please provide your feedback by Friday 15th June.

If you have any questions, please do not hesitate to ask.

Many thanks,
IATI Tech Team

1 Like

This looks great! Thanks, @IATI-techteam.

Minor thing, but I think it might help to make the test version behave the same way the live version is intended to work, i.e. perform the automatic redirect. That way, developers can fully test this in a staging environment, in order to spot any problems.

You could still add a query parameter (?dryrun=true or equivalent) that puts the redirect URL in the body of the response (as it does now), rather than using headers. But I think it would be helpful to make the default behaviour match production.

1 Like