You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm filing this as a request in the context of the guidelines by the Dutch Ministry of Foreign Affairs.
Dutch NGOs are requested to use IATI 2.02, because of one extra transaction type introduced: "incoming commitment" (code 11). The easiest way to help those organisations is to just add this option to the pick list in AidStream.
Technically, the resulting data should be marked as version 2.02. It doesn't mean that AidStream supports all other new features of 2.02, but a valid 2.01 file should be a valid 2.02 file as well if backward compatibility is done right.
I can imagine some discussion, although I think confusion will be minimal. The full support for 2.02 can then be added to AidStream after the interface upgrade has been completed.
The text was updated successfully, but these errors were encountered:
Hi @rolfkleef just to let you know that @anjesh and I spoke before Christmas about the possibility of being to able to release the 'new' version of Aidstream at the end of March and for it to include V2.02 support as well. Obviously this is a very ambitious ask given the timescales but @anjesh was going to look into the possibility of being able to do this so I'll let @anjesh comment on the feasibility of this one.
Hi @KasperBrandt really sorry for not getting back to you sooner but yes things are still on track for the release of a new version of Aidstream (with a new interface & other enhancements) and including this transaction type at the beginning of April. Comms will be going out to Aidstream users soon
I'm filing this as a request in the context of the guidelines by the Dutch Ministry of Foreign Affairs.
Dutch NGOs are requested to use IATI 2.02, because of one extra transaction type introduced: "incoming commitment" (code 11). The easiest way to help those organisations is to just add this option to the pick list in AidStream.
Technically, the resulting data should be marked as version 2.02. It doesn't mean that AidStream supports all other new features of 2.02, but a valid 2.01 file should be a valid 2.02 file as well if backward compatibility is done right.
I can imagine some discussion, although I think confusion will be minimal. The full support for 2.02 can then be added to AidStream after the interface upgrade has been completed.
The text was updated successfully, but these errors were encountered: