In the Techniques section:
Techniques
Avoiding eTransparency Failure: Ideas About Data Infrastructure
This page offers ideas about how to address one factor identified as important to the success or failure of e-transparency projects. Follow this link for more information about such factors (and some related case examples).
Idea 1: Ensure Someone Internal Is Responsible For Data Quality
Good quality data is the bedrock of e-transparency systems. If the data that is being opened up to public scrutiny is of poor quality, then no-one will trust or then use the e-transparency system. Data in such systems must be pushed as far as reasonably possible on five quality measures:
- Completeness : the degree to which all the data required is present.
- Accuracy : the level of errors/incorrect data within the overall data.
- Relevance : the degree to which data is necessary in order to complete the required transparency decisions and actions.
- Timeliness : the degree to which data arrives within a required timeframe.
- Appropriateness of presentation : the degree to which data is accessible and intelligible to recipients.
To ensure this 'push', someone within the public agency must be made sustainably responsible for these 'CARTA' qualities of all data loaded onto the e-transparency system.
(From: Richard Heeks, Alan Levin & Ryan Dingley)
Idea 2: Introduce Hard And Soft Controls To Boost Data Quality
Since data quality matters so much for e-transparency, a combination of hard and soft controls needs to be put in place to try to improve and sustain good data quality. Hard controls include things like passwords, encryption, firewalls, anti-virus software, and automated checks on data input. Soft controls include things like adequate reward systems for those handling data, appropriate training, and separation of duties.
(From: Richard Heeks)
Online Resources
Follow this link to access online resources on e-transparency data architecture.