A month ago, on April 8th, I helped a group of Dutch NGOs get to grips with AidStream, as part of the Partos IATI programme. As always, itโs very informative to see unsuspecting users try to make sense of a new tool. It resulted in a list of observations, often easy fixes, that can make life a little easier or more pleasant.
That same week, the AidStream code base was published on Github, and I had a chance to participate in the team check-in, and report a bunch of these observations as issues.
just added some observations from the @PartosNL #IATI workshop last week as @aidstream issues on github: http://t.co/rLyvzRHakl
โ Rolf Kleef (@rolfkleef) April 9, 2014
Weโre hardly a month later, and Iโm glad to see a steady flow of notifications of issues being closed:
- The workflow status โEditโ is now called โDraftโ, to avoid confusion with the action โeditโ.
- When you add a new activity, you now see descriptive values (โReporting Organisation Type: National NGOโ) instead of code list values (โ22โณ).
- The template file to upload transactions works properly now (you actually can choose a simpler template now as well).
- Your own internal reference numbers for transactions are now shown in the transactions list.
- The exotic โLinked Data Defaultโ field is hidden (at the moment, only Unicef seems to publish this, with valueโฆ โโ).
So if you participate in the Partos programme, and use AidStream: tell us what you like and what confuses you. Thereโs a good chance youโll see your feedback incorporated in the next version soon!