Presentation on theme: "Expected Outputs & Lessons Learned"— Presentation transcript:
1Expected Outputs & Lessons Learned Léa Hakim & Neda JafarStatistics Coordination Unit, ESCWAWorkshop on Building Country Capacity to Maintain a Central Repository of Data Amman March 2007
22. Action plan for clean-up Expected OutputsBy the end of today’s session:1. Preliminary Report2. Action plan for clean-up
32. Action plan for clean-up Expected Outputs1. Preliminary Report2. Action plan for clean-up
4Preliminary ReportConsolidation of working session outputs as per templates shared:Status:Database ManagementDevInfo as a Central Repository of Data (CRD)Data coverageLinking producers and users of dataDissemination
71. DevInfo summary report: Review of subgroups Source: Report on DevInfo 2004 Technical Support for UNDG Project “Building Capactiy and Statistical Literacy for MDG Monitoring”, Community Systems Foundation p.12
81. DevInfo summary report: Review of sources Source: Report on DevInfo 2004 Technical Support for UNDG Project “Building Capactiy and Statistical Literacy for MDG Monitoring”, Community Systems Foundation p.9
92. MDG Monitoring Indicator I-U-S Analysis Source: Report on DevInfo 2004 Technical Support for UNDG Project “Building Capactiy and Statistical Literacy for MDG Monitoring”, Community Systems Foundation p.19
102. MDG Monitoring Indicator I-U-S Analysis Complete template in reviewing data contentCustomize area categoriesInclude review of whether changes implemented for final report [ Column “Action Taken (Y, N)” in template shared]Note: Electronic I-U-S Analysis template distributed.
11Preliminary Report Conclusions for next steps Outline decisions taken for next steps during this trainingEx. Focus on MDG indicators only for first launchEx. Establishing area codes at sub-national levelEx. Adding proxies/national development indicators
12Final Report Outline Introduction Objectives Status of CRD Structure and Content ReviewConclusionsChallenges in clean-upLessons learnedEvaluation report (M&E UNICEF)AnnexesInclude Action Plan TimetablePreliminary ReportNote: Electronic report template distributed.
132. Action plan for clean-up Expected Outputs1. Preliminary Report2. Action plan for clean-up
14Beyond CRD Training Complete database (DB) Review Complete DevInfo DB cleanupUNICEF M&E officer evaluationSubmission of final reportUse and dissemination of DBCountry Roll-out
152. Action plan Main Task Task Components Person(s) responsible March AprilI. Full conversion to DevInfo v5.0II. Completion of DB reviewIII. Implementation of cleanupIV. EvaluationV. Submission of reportVI. Launch of national DevInfo DBNote: Detailed electronic action plan template distributed.
17Strategy and Planning Exchange of experiences Should invest in preparation prior to release:Setup (complete DevInfo team w/ clear functions & responsibilities)Necessity of Technical/Steering CommitteeEstablish (feedback between DevInfo team, statistics producers, UN agencies).Clear strategy and plan of actionEmphasis on qualityPrioritize MDG DBRaise awareness of decision-makers to make use of available statistics
18Database Management Start with planning process Start small, think BIG!Importance of establishing:DevInfo teamCommittees: Steering and TechnicalFormal agreements with line ministriesInvolve users from beginningDB management requires experts for assessing data and metadata
19DevInfo as CRD DevInfo is user-friendly as a program and interface Web-enabling optionInstitutional link between DBs and DevInfoCustomized national DevInfoUse of GISMapping facilityData organized by themes for targeted policy-makingStore other activities’ data such as surveys & censusesReady-tailored metadata and indicators of MDG frameworkAvailability of international sources of data
20Data coverage Sex disaggregated data Small area disaggregated data Time seriesDifferent sourcesStrengths and weaknesses of DBEstablish processes for data collectionReview of list of indicators in national database relative to global MDG listAddition of country-specific development indicatorsReview of meta-data on indicators, sourcesReview of geographical areas/maps
21Producer – User dialogue Establish linkages with line ministriesRegular forumsUnification of standards and methodsUnification of classifications and definitionsData-entry by line ministries through webTrain users to understand statistics, indicators, and analysis of data
22Dissemination Press releases Web-enabling Dissemination through workshopsAddition of DevInfo links to NSO sites (including training material)Provision of DevInfo CD with national MDGRKnowledge transferRoll-out advocacy campaign
23Structure & Content Spell Check Thematic databases Always refer to global DB structures - Import MDG indicators and goals from global DB – do not type.Planning of DB content is essentialContinuous check of data qualityMetadataFollow standard naming of sourceDocument all changes madeAssessment of data availability has to be done BEFORE creating a templateSource of data should specify the original producer ex. MOH for health indicatorsNaming of source should follow “PAL_MOH_DHS_2003”Set up different DBs for big amounts of info ex.census & surveysRemove indicators with no data values to avoid over reporting
24Mapping Continent and country level: apply ISO coding Ensure each area ID is connected to area name and vice versaStart working towards a target for infrastructure mapsArea ID is the key to the mapping
25Data Quality During data entry preferable to insert value not formula Review data and consistency – do not rely on automated waysDo not include indicators with missing valuesAvoid duplicationEnsure completeness of data values and time series