02 September 2011

The new Data Quarantine feature provides a level of data quality validation before data enters the database. Unmapped data (that is, data that the system does not recognise such as a newly installed ANPR link etc) is quarantined within the database where the user can review it and either add it to the database or permanently exclude it. In addition, data that falls outside acceptable user defined values can also be quarantined which helps to identify source data issues but, following review by an Argonaut user, can still be allowed in to the database if it is deemed to be valid. This feature ensures the highest level of data quality within the database. There is also the ability to ignore future invalid data from a specified source.

Lee Williams, a Project Manager within Idox Transport, went on to describe how one features which will help his customers: "Any data received from a third party system such as a counter that is sending clearly wrong data (such as a negative count or a count that exceeds some user defined value etc) is stored in the quarantine area where the user can either delete it or allow it to be added in to the common data base. This ensures that data in the database is not polluted by poor quality data."

Mike Wells, responsible for all operations chimed in and added; "Any data received from a third party system that the UTMC database does not recognise can also be quarantined. For example imagine that a new ANPR link has been installed; if that ANPR link has not been manually added to the common database then any data for that link will then enter the quarantine area. This lets the user know that he/she is receiving data for an object that has not yet been added to the Common Database. The user can then simply select that item and add it to the database, thereafter any such data will automatically pass in to the database."