<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="HND_2010_MCC-APGGF_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_HND_2010_MCC-APGGF_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Review of Metadata">Millennium Challenge Corporation</producer>
      <prodDate date="2014-04">2014-04</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (April 2014)
Version 2.0 (April 2015). Edited version based on Version 01 (DDI-MCC-HND-IE-AG-2010-v1) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Agricultural Public Goods Grant Facility 2010</titl>
      <subTitl/>
      <altTitl>MCC-APGGF 2010</altTitl>
      <parTitl/>
      <IDNo>HND_2010_MCC-APGGF_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">NORC</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-01">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="Millennium Challenge Corporation" URI="" email="impact-eval@mcc.gov">Monitoring &amp; Evaluation Division</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date=""/>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Honduras</keyword>
      <keyword vocab="" vocabURI="">Agriculture</keyword>
      <keyword vocab="" vocabURI="">Grants Facility</keyword>
      <keyword vocab="" vocabURI="">IRR</keyword>
      <keyword vocab="" vocabURI="">ERR</keyword>
      <keyword vocab="" vocabURI="">Performance evaluation</keyword>
    </subject>
    <abstract>In this report, the economic rates of return have been reviewed and recalculated for the projects that were concluded or that registered a considerable level of progress as of July 2010.
 
For purposes of facilitating the methodological development and obtaining valid conclusions, the following was taken into consideration: 

- For purposes of the analysis, the 15 projects have been classified in three types: i) Irrigation (10 projects); ii) Value Added-Microbusinesses (1); and iii) Research and technology (4), which includes the OIRSA-MOSCAMED project. 

- Due to the different level of advancement of the projects being implemented, the re-calculation of the ERR for the irrigation projects is based on the three projects that had ended their first implementation phase or were very close to completing it by July 2010. This first phase represents the ending of the works to be executed with the project and the beneficiaries' incorporation. In the projects in which the total number of predicted beneficiaries had not yet been reached, the number of beneficiaries that had been actually reached as of the time of this analysis was taken into account, and future incorporations were assumed until attaining the expected goal by year 3 of the project's implementation, approximately. 

- The value-added project type is represented by a single project, which is carried out by EAP-Zamorano and that was concluded in July 2010. Consequently, the evaluation is based on this single project. 

- Regarding the research projects, since the progress for projects of this type as of July 2010 covered mainly the laboratories' set-up activities and the creation of the biological items and basic genetic material required in the project the ERRs were calculated maintaining the assumption and goals originally proposed by the project designers, adjusting only the start-up times for the beneficiaries' incorporation. These projects should be evaluated once they have registered further progress on meeting surface-area and number of incorporated producers or beneficiaries goals.</abstract>
    <sumDscr>
      <collDate date="2010" event="start" cycle=""/>
      <collDate date="2010" event="end" cycle=""/>
      <nation abbr="HND">Honduras</nation>
      <geogCover/>
      <geogUnit/>
      <anlyUnit/>
      <universe/>
      <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/>
      <!-- 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/>
      <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/>
      <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/99">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/99
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="no" formNo="" URI=""/>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
