Building a Good Practice Database: Lessons Learned on Categorization, Promotion and Purpose
•
1 j'aime•592 vues
Win experience on online database teun bastemeijer, win
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Building a Good Practice Database: Lessons Learned on Categorization, Promotion and Purpose
Similaire à Building a Good Practice Database: Lessons Learned on Categorization, Promotion and Purpose (20)
Plus de OECD Governance
Plus de OECD Governance (20)
Dernier
Dernier (20)
Building a Good Practice Database: Lessons Learned on Categorization, Promotion and Purpose
- 1. January 2017 C. Grandadam – Water Integrity Network cgrandadam@win-s.org BUILDING A GOOD PRACTICE DATABASE Notes and lessons learned
- 2. A case database, 2 years in the making January 2017 2 Our database shows that action is possible. We have diverse cases from across the globe that demonstrate that there are many ways to promote integrity at any level. We keep the main editorial burden internal and collect cases in any format. It can be a resource challenge but makes it easier for partners to share info. For us as a network, this is key. As an evidence base, the cases are strong input for research and in-depth analysis.
- 3. The bumpy road to web databases January 2017 3 Categorization, research, editing and translating take the most time (and it’s a lot). Each individual case requires promotion to be viewed and traffic is only starting to grow. The main database is still relatively unknown. We spent a lot of time cleaning historical data thinking cases are evergreen but most older cases are not regularly consulted. We spent a lot of time on categorizations but in practice, most users filter only on location.
- 5. It’s easy to get bogged down in the processes of building a public database instead of focusing on the processes that ensure a database is visited (promotion!) and the processes that one brings most unique value to. January 2017 5 A lesson learned
- 6. Ideas and suggestions January 2017 6 - Clearly identify purpose of database. Make choices: show evolving practice or proven impact? Show diversity and provide a source of inspiration or build a reference showing specific and replicable information. - Don’t forget “after-sales service”: the database will not gather traffic on its own. Historical data generates less traffic than information that responds to current priorities. A high visibility host, regular updates, and promotion for each case, will help make a database google-friendly and therefore more visible. - Focus on your strengths and piggy-back on the strengths of your members. OECD WGI’s strength may not be in the database build and publication but in the assessment of the cases (peer- reviewing, providing access to a network, measuring impact using indicators, relating and contextualizing different cases -for example in publications for World Water Forum). - Think of incentives for users to share “practice”, especially more sensitive information on challenges and failures