New version of IATI Bug Tracker


(Vincent van 't Westende) #1

Last year around this time I put http://www.iatibugtracker.org/ online, which was an incomplete, example-ish tool that displayed validation logs on ~250 checks being applied in OIPA.

Since then, nothing really changed in being able to validate your data, nor in the (technical) data quality itself. So in an effort to give more feedback to data publishers I’ve been working on finishing this tool. An updated version of it is now online. The update includes:

  • A list of all validation checks I could think of http://www.iatibugtracker.org/implemented-checks
  • Better search functionalities in publisher / dataset lists
  • Better functionalities to filter validation errors (select element/attribute)
  • More in depth info; the line number where the error occurs (for most of them at least), the used value in the XML in case its an ‘not on codelist’ or ‘incorrect format’ error.
  • An updated, easier to maintain design (with a favicon of a bug)

Further more, a couple notes on dubious errors;

  • When an element is used, its expected to have valid data (hence something like an empty narrative will show as an error).
  • When an attribute is used, its expected to have valid data (hence an empty transaction/provider-org/provider-activity-id will show as an error).
  • The “Must be in the format {Registration Agency} - (Registration Number}” check for org refs is a bit awkward; with that rule you can’t correctly mention an organisation that uses a 1.0x ref (for example, unhabitat with ref 41120) from 2.0x data. This should solve itself when all orgs publish in 2.01+ though.
  • Some errors might throw for 1.0x data while they only apply to 2.0x. I was a bit lazy on this, but at the same time it gives publishers valuable info for their to do’s when moving to 2.0x.

I hope this helps some publishers with improving their data, the tool is obviously not meant to blame anyone or rank something like technical data correctness, its just an extra aid.

Feedback is very welcome of course!

p.s. excuse me for the name of the tool, software has bugs, data has errors.

p.s.2 I’ve got very limited ambition to further improve this tool anytime soon, its an evening hours side-project that took me too much time already.