If you’ve ever had to write software that imports or exports IATI data, you may have noticed that the order of the XML elements is considered a critical part of the schema validation. Why was this change made historically, and why does it persist today?
How can one combine the advantages of modern single-page applications with traditional search-engine optimization (SEO)? Here’s the lessons we learned while implementing SEO on the IATI Datastore Search.
Today we released the International Aid Transparency Initiative’s Datastore Search. One of the main features of the product is to allow the user to download their search results in JSON, CSV, or original IATI XML format. This enables data users to export and use the IATI data in their own systems or analysis. Previous iterations of the IATI Datastore either required pagination over results to get a full view of the data or struggled to consistently handle requests for large amounts of data. This post covers how we tackled this issue on the IATI Unified Platform.
Today we released Datastore Search.
When I started to play this game, back in the early years of this century, we had system administrators on staff.
For the last decade or so, IATI software as cared for by the core IATI technical team has been a smorgasbord of tools contributed by all sorts, each operating independently on innumerable servers, each repeating a number of things in different and exotic ways - most presciently, downloading the 8000+ plus IATI documents to occupy many duplicated gigabytes of storage space.
Increase deployment speed of Azure Premium SKU Functions from GitHub Actions through use of Docker containers and an Azure maintained action.
Hello and welcome to the first post on our brand new IATI Developer Blog. We’re intending this blog to be a place for us to document the challenges we’ve faced as we build your favourite IATI tools, as well as the solutions we’ve designed to overcome them.