We have had a busy start to the year. Here’s an update on a few key projects…
As announced in January, we’ve secured a new hosting arrangement for the IATI Registry to improve the experience for users. The team has been busy preparing for the migration and the switchover to our new CKAN provider, Derilinx will be completed by 30th March.
Please note: users will not be able to access the Registry during a brief period of downtime (timings to be confirmed) to allow for the migration to be complete. After the switch, users should not notice any difference in the way they interact with the Registry.
The team have been working on implementing IATI’s website project and by the beginning of May will release a beta version of a new website with:
- Redesigned/rewritten content to replace aidtransparency.net
- Redesigned/rewritten content replacing the guidance section on the iatistandard.org site. NB. This phase of the project does not include a redesign of the reference section which is derived from the standard’s schema and codelists.
- A home page with descriptions and links to all IATI legacy assets (all existing IATI maintained websites)
We would like to encourage the IATI community to take part in a number of user testing exercises for the new website. To begin with, we are seeking help that will inform the structure of the new guidance section of the website. Can you give us 10-15 minutes of your time to complete this exercise. We will also shortly be inviting you to review the site’s new information architecture using an interactive online tool.
The Governing Board will take a decision in the near future on the redevelopment of the Datastore. In anticipation of some or all of the project being outsourced the Technical Team has begun preparation of a detailed specification which will be shared with the community in April.
We are decommissioning the publishing tool CSV2IATI in the first week of April. Over the past 12 months we have been supporting organisations to transition off this tool and to start publishing at the latest versions of the IATI Standard, this is either with a tool provided by the IATI community or through an internal reporting system. If you still need support to transition off CSV2IATI please contact the IATI Technical Team at: email@example.com.