<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="TZA_2009_MCC-TPE_v01_M" xml-lang="en" xmlns="http://www.icpsr.umich.edu/DDI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.icpsr.umich.edu/DDI http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>DDI_TZA_2009_MCC-TPE_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Metadata Producer">Millennium Challenge Corporation</producer>
      <prodDate date="2014-03-28">2014-03-28</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.1 (March 2014).  This version uses an updated metadata template.
Version 2.0 (May 2015). Edited version based on Version 01 (DDI-MCC-TZA-thrshld-2011-1.1) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Threshold Performance Evaluation 2009-2010</titl>
      <subTitl/>
      <altTitl>MCC-TPE 2009-10</altTitl>
      <parTitl/>
      <IDNo>TZA_2009_MCC-TPE_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="New York University">James Hollyer</AuthEnty>
      <AuthEnty affiliation="New York University">Leonard Wantchekon</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-09">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="The World Bank" URI="http://microdata.worldbank.org" email="microdata@worldbank.org">The World Bank Microdata Library</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">Raw data for internal use only</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Anti-corruption</keyword>
    </subject>
    <abstract>The methodologies employed by the evaluation are both quantitative and qualitative. Wherever possible, we obtain data and employ an identification strategy with which to estimate the causal effect of a given intervention. Data are collected from program participants, and data collection was handled by EcomResearch – a Dar es Salaam based research firm. Because data is often unavailable, and because randomization was never employed in treatment assignment, such causal estimations are sometimes impossible. Where quantitative methods cannot be used to assess the effect of an intervention, we employ qualitative methods. We conduct interviews with program participants, engage in document review, and – in some cases – conduct semi-structured field interviews to assess the implementation and sustainability of a given intervention. We also examine the logical link between the intervention and the reduction of corruption, in light of related academic literatures. The quantitative methods employed in this evaluation give precise estimates of the effect of training on a narrowly defined quantity of interest. Qualitative methods, on the other hand, cannot give as precise an estimate, but may incorporate a broader variety of factors than quantitative estimation allows.</abstract>
    <sumDscr>
      <collDate date="2009-12-01" event="start" cycle=""/>
      <collDate date="2010-06-30" event="end" cycle=""/>
      <nation abbr="TZA">Tanzania</nation>
      <geogCover>National coverage</geogCover>
      <geogUnit/>
      <anlyUnit>Individuals and institutions/organizations</anlyUnit>
      <universe>Key government of Tanzania representatives involved in the threshold program activities.</universe>
      <dataKind>Sample survey data [ssd]</dataKind>
    </sumDscr>
    <!-- qualityStatement - ddi2.5 - complex type
     
     This structure consists of two parts, standardsCompliance and otherQualityStatements. 
     In standardsCompliance list all specific standards complied with during the execution of this 
     study. Note the standard name and producer and how the study complied with the standard. 
     Enter any additional quality statements in otherQualityStatements.
     
     -->
    <qualityStatement>
      <standardsCompliance>
        <standard>
          <standardName/>
          <producer/>
        </standard>
        <complianceDescription/>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes/>
    <!-- exPostEvaluation ddi2.5
      Use this section to describe evaluation procedures not address in data evaluation processes. 
      These may include issues such as timing of the study, sequencing issues, cost/budget issues, 
      relevance, instituional or legal arrangments etc. of the study. 
      
      The completionDate attribute holds the date the evaluation was completed. 
      The type attribute is an optional type to identify the type of evaluation with or without 
      the use of a controlled vocabulary.
    -->
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth/>
      <dataCollector abbr="" affiliation="">Ecom-Research</dataCollector>
      <!-- collectorTraining - DDI2.5
        
        Collector Training

        Describes the training provided to data collectors including internviewer training, process testing, 
        compliance with standards etc. This is repeatable for language and to capture different aspects of the 
        training process. The type attribute allows specification of the type of training being described.
        
        -->
      <collectorTraining type=""/>
      <frequenc/>
      <sampProc>PETS districts were selected by random sampling to be interviewed.</sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <resInstru/>
      <!-- instrumentDevelopment - DDI2.5             
        Describe any development work on the data collection instrument. Type attribute allows for the optional use of a defined development type with or without use of a controlled vocabulary.
        -->
      <instrumentDevelopment type=""/>
      <collSitu/>
      <actMin/>
      <ConOps/>
      <weight/>
      <cleanOps/>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate>Our measure of article quality weights factors such as the quality of the writing and the ability to place a given story in a broader context; whereas, much of PACT’s training emphasized investigative methods.</respRate>
      <EstSmpErr/>
      <dataAppr/>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://data.mcc.gov/evaluations/index.php/catalog/75">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/75
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="no" formNo="" URI=""/>
      <restrctn/>
      <citReq>Hollyer, James, and Leonard Wantchekon. Tanzania Threshold Country Program: End Term Evaluation. 2011.</citReq>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
