Annex_9_MCC_Evaluation_Metadata_Template.pdf

<?xml version="1.0" encoding="UTF-8" ?>

- <Templates Version="1.08">

- <Template Name="MCC Evaluation Metadata Template 1.3" Version="1.3" Author="Nicole Styler Harker, Olivier Dupriez, Mehmood Ashgar, Tefera Bekele, Akiko Sagesaka, Matthew Welch, Johan Mistiaen" Organization="Millennium Challenge Corporation / World Bank / International Household Survey Network" OtherMaterialsVisible="FALSE" CellNotesVisible="FALSE" CubeSetupsVisible="FALSE"> <Languages Default="EN" />

- <Description>

- <![CDATA[

Adaptation of template IHSN_1.6_en from the International Household Survey Network

The only differences are:

- the study title was removed from the Document Description section (it was redundant with "Title" in the Study description"

- the CESSDA topics classification was replaced by the WB topics classification as controlled vocabulary.

- added "Holdings URI" and "Collection" in the document description section

- integrated the Impact Evaluation fields into the main template for World Bank use

- added "Impact Evaluation Methods" using "2.1.6.2 Version Responsibility Affiliation" field

</Description> <Created y="2005" m="3" d="3" /> <Modified y="2013" m="10" d="28" />

- <DocDesc>

- <TabGroup>

- <Tab Name="Metadata Preparation">

- <Item ID="DocumentDescription_Citation_ProductionStatement_Producers" Label="Metadata Producer" Mandatory="TRUE">

- <Description>

- <![CDATA[

Name of the person(s) or organization(s) who documented the dataset. Use the "role" attribute to distinguish different stages of involvement in the production process.

MCC Clarification:

Although Survey Firms will be expected to provide information related to data collection in a Data Collection Report, the In

Content and Format:

Name: Evaluation Individual or Firm Name Abbreviation: Only include if applicable (e.g., NORC) Affiliation: For individuals, list the university or institution that they are affiliated with. Leave blank if a firm is the Role: Independent Evaluator or MCC in the case that MCC created the Nesstar metadata file.

Examples:

Name: National Statistics Office Abbreviation: NSO Affiliation:

Role: Documentation of the study

Name: International Household Survey Network Abbreviation: IHSN Affiliation:

Role: Review of the metadata

</Description>

- <ProducersItem> <Producer Name="Millennium Challenge Corporation" Abbreviation="MCC" Role="Review of Metadata" />

</ProducersItem> </Item>

- <Item ID="DocumentDescription_Citation_ProductionStatement_ProductionDate" Label="Date Produced">

- <Description>

- <![CDATA[

MCC Clarification:

This is the date (in ISO format YYYY-MM-DD) the DDI metadata was produced (not distributed or archived). This date will be a

</Description> <DateItem />

</Item>

- <Item ID="DocumentDescription_Citation_Version_Text" Label="Metadata Version">

- <Description>

- <![CDATA[

Documenting a dataset is not a trivial exercise. Producing "perfect" metadata is probably impossible. It may therefore happen that, having identified errors in a DDI document or having received suggestions for improvement, you decide

MCC Clarification:

Metadata maybe updated continuously and we therefore need to track versions. The Version number will be a sequential number

Content and Format:

Version X (Original YYYY-MM-DD): Explanation

Example:

Version 1.1 (July 2006). This version is identical to version 1.0, except for the section on Data Appraisal which was update

</Description> <LinkedTextItem />

</Item>

- <Item ID="DocumentDescription_Citation_TitleStatement_IDNumber" Label="Metadata ID Number" Mandatory="TRUE">

- <Description>

- <![CDATA[

The ID number of a DDI document is a unique number that is used to identify this DDI file. Define and use a consistent scheme to use.

Content and Format:

DDI-country-producer-survey-year(s)

- country is the 3-letter ISO country abbreviation

- producer is the abbreviation of the producing agency

- survey is the survey abbreviation

12/28/2016http://intranet.mcc.gov/department/AF-CGM/CGMOnlyAccess/CGM%20T2%20Shared/...

- year is the reference year (or the year the survey report was received)

- DDI document version number

Example:

A metadata file for a rural water supply activity survey in Mozambique created by Stanford and Virginia Tech in 2011 could ha If the same survey is documented by a staff from the IHSN, this would be DDI-MCC-MOZ-IHSN-RWSA-2011-v01.

</Description> <UnicodeAttributeItem />

</Item> </Tab>

- <Tab Name="MCC Compact and Program">

- <Item ID="DocumentDescription_DocSource_TitleStatement_Title" Label="Compact or Threshold" Mandatory="TRUE">

- <Description>

- <![CDATA[

MCC Clarification:

Include the word 'Compact' or 'Threshold' as applicable, as well as the compact or threshold number.

Examples:

Moldova Compact Cape Verde Compact II Tanzania Threshold Niger Threshold II

</Description> <AttributeItem />

</Item>

- <Item ID="DocumentDescription_DocSource_Notes" Label="Program" Mandatory="TRUE">

- <Description>

- <![CDATA[

MCC Clarification:

Brief description of the Compact components being evaluated (Project/Activity/Sub-Activity). This is essentially the first pa

</Description> <LinkedTextItem />

</Item>

- <Item ID="DocumentDescription_DocSource_ProductionStatement_ProductionPlace" Label="MCC Sector" Mandatory="TRUE">

- <Description>

- <![CDATA[

MCC Clarification:

Most threshold evaluations fall under Cap Bldg & Inst Dev.

</Description>

- <LinkedTextItem>

- <CtrlVocab>

<VocabItem Value="Agriculture and Irrigation (Ag & Irr)" /> <VocabItem Value="Capacity Building and Institutional Development (Cap Bldg & Inst Dev)" /> <VocabItem Value="Education (Edu)" /> <VocabItem Value="Energy (Energy)" /> <VocabItem Value="Finance, Investment, and Trade (FIT)" /> <VocabItem Value="Health (Health)" /> <VocabItem Value="Land (Land)" /> <VocabItem Value="Transport (Trans)" /> <VocabItem Value="Water, Sanitation and Hygiene (WASH)" /> <VocabItem Value="Other (Other)" />

</CtrlVocab> </LinkedTextItem>

</Item>

- <Item ID="DocumentDescription_Notes" Label="Program Logic">

- <Description>

- <![CDATA[

MCC Clarification:

Overview of Projects/Activities/Sub-Activities objectives and a description of the causal chain from inputs, outputs, to outc

</Description> <LinkedTextItem />

</Item>

- <Item ID="DocumentDescription_Citation_Version_Notes" Label="Program Participants">

- <Description>

- <![CDATA[

MCC Clarification:

Please define the program participant in terms of specific selection criteria for participation in the program.

Example:

The survey covered all de jure household members (usual residents), all women aged 15-49 years resident in the household, and

</Description> <LinkedTextItem />

</Item> </Tab>

</TabGroup> </DocDesc>

- <StudyDesc>

- <TabGroup>

- <Tab Name="Identification">

- <Item ID="StudyDescription_Scope_SummaryDataDescription_Countries" Label="Country" Mandatory="TRUE">

- <Description>

- <![CDATA[

Enter the country name, even in cases where the survey did not cover the entire country. In the field

"Abbreviation", we recommend that you enter the 3-letter ISO code of the country. If the dataset you document covers more tha

Content and Format:

Name: Full country name Abbreviation: Three-letter country code

MCC Clarification: Country or Countries where evaluation was conducted.

Example:

Name: Burkina Faso Abbreviation: BFA

</Description> <CountriesItem />

</Item>

- <Item ID="StudyDescription_Citation_TitleStatement_Title" Label="Evaluation Title" Mandatory="TRUE">

- <Description>

- <![CDATA[

Content and Format:

If Compact: Name of Compact Project/Activity/Sub-Activity If Threshold: Country Name Threshold Number

MCC Clarification:

Using the Compact hierarchy as a reference, write the Project/Activity/Sub-Activity/Threshold that is being evaluated. If the

Examples:

For the evaluation of the Water to Market Project's Farmer Training Activity, the name can be "Water to Market Farmer Trainin For the first Malawi Threshold, the name can be "Malawi Threshold I"

</Description> <AttributeItem />

</Item>

- <Item ID="StudyDescription_Citation_TitleStatement_ParallelTitle" Label="Translated Evaluation Title">

- <Description>

- <![CDATA[

MCC Clarification:

Although providing a translated title is optional, a translated title may be ideal for evaluations done in countries that hav

</Description> <AttributeItem />

</Item>

- <Item ID="StudyDescription_Citation_SeriesName" Label="Evaluation Type" Mandatory="TRUE">

- <Description>

- <![CDATA[

MCC Clarification: If the evaluation evolved from a performance to an impact or impact to a performance, indicate Independent Evaluation instead of specify type.

Content and Format:

Select from controlled vocabulary options:

Independent Performance Evaluation, Independent Impact Evaluation, or Independent Evaluation

</Description>

- <AttributeItem>

- <CtrlVocab>

<VocabItem Value="Independent Performance Evaluation" /> <VocabItem Value="Independent Impact Evaluation" /> <VocabItem Value="Independent Evaluation" />

</CtrlVocab> </AttributeItem>

</Item> </Tab>

- <Tab Name="Version">

- <Item ID="StudyDescription_Citation_Version_Text" Label="Data Description">

- <Description>

- <![CDATA[

Content and Format:

Select from controlled vocabulary options:

Raw data for internal use only, Edited clean data for internal use only, Licensed datasets, accessible under conditions, Anonymized dataset for public distribution, Not applicable to this evaluation; no quantitative data to be shared

</Description>

- <LinkedTextItem>

- <Text>

<![CDATA[ - v01: Edited, anonymous dataset for public distribution. ]]> </Text>

- <CtrlVocab> <VocabItem Value="Raw data for internal use only" /> <VocabItem Value="Edited clean data for internal use only" /> <VocabItem Value="Licensed datasets, accessible under conditions," /> <VocabItem Value="Anonymized dataset for public distribution" /> <VocabItem Value="Not applicable to this evaluation; no quantitative data to be shared" />

</CtrlVocab> </LinkedTextItem>

</Item> </Tab>

- <Tab Name="Overview">

- <Item ID="StudyDescription_Scope_Abstract" Label="Evaluation Summary">

- <Description>

- <![CDATA[

MCC Clarification:

Overview of Evaluation Design, includes evaluation type (performance/impact), evaluation questions, exposure to treatment. U

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Citation_Version_Affiliation" Label="Evaluation Methodology">

- <Description>

- <![CDATA[

Keywords summarize the content or subject matter of the survey. As topic classifications, these are used to facilitate referencing and searches in electronic survey catalogs.

Keywords should be selected from a standard thesaurus, preferably an international, multilingual thesaurus. Entering a list

Content and Format:

Select from controlled vocabulary options:

Randomization, Propensity Score Matching, Difference-in-Difference, Regression Discontinuity Design, Interrupted Time Series, Continuous Treatment, Pre-Post with Comparison Population, Pre-Post, Ex-Post, Independent Ex-Post ERR, Independent Ex-Post ERR and HDM-4, Other (Performance Evaluation)

MCC Clarification:

These are the Performance options listed above; all other options are only to be selected for Impact Evaluations:

Pre-Post with Comparison Population, Pre-Post, Ex-Post, Independent Ex-Post ERR, Independent Ex-Post ERR and HDM-4, Other (Performance Evaluation)

</Description>

- <AttributeItem>

- <CtrlVocab>

<VocabItem Value="Randomization" /> <VocabItem Value="Propensity Score Matching" /> <VocabItem Value="Difference-in-Difference" /> <VocabItem Value="Regression Discontinuity Design" /> <VocabItem Value="Interrupted Time Series" /> <VocabItem Value="Continous Treatment" /> <VocabItem Value="Pre-Post with Comparison Population" /> <VocabItem Value="Pre-Post" /> <VocabItem Value="Ex-Post" /> <VocabItem Value="Independent Ex-Post ERR" /> <VocabItem Value="Independent Ex-Post ERR and HDM-4" /> <VocabItem Value="Other (Performance Evaluation)" />

</CtrlVocab> </AttributeItem>

</Item>

- <Item ID="StudyDescription_Scope_SummaryDataDescription_AnalysisUnit" Label="Unit of Analysis">

- <Description>

- <![CDATA[

MCC Clarification:

Choose from any of the following: individuals, households, community, administrative units, enterprise, school, health cent

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Scope_SummaryDataDescription_DataKind" Label="Kind of Data">

- <Description>

- <![CDATA[

This field is a broad classification of the data and it is associated with a drop down box providing controlled vocabulary. That controlled vocabulary includes 9 items but is not limited to them.

MCC Clarification: Only fill in this field if it is applicable.

</Description>

- <LinkedTextItem>

- <CtrlVocab>

<VocabItem Value="Sample survey data [ssd]" /> <VocabItem Value="Census/enumeration data [cen]" /> <VocabItem Value="Administrative records data [adm]" /> <VocabItem Value="Aggregate data [agg]" /> <VocabItem Value="Clinical data [cli]" /> <VocabItem Value="Event/transaction data [evn]" /> <VocabItem Value="Observation data/ratings [obs]" /> <VocabItem Value="Process-produced data [pro]" /> <VocabItem Value="Time budget diaries [tbd]" /> <VocabItem Value="Other" />

</CtrlVocab> </LinkedTextItem>

</Item>

- <Item ID="StudyDescription_Methodology_ResearchInstrument" Label="Questionnaires">

- <Description>

- <![CDATA[

List of questionnaires and short description of each (languages, modules)

Example:

The questionnaires for the Generic MICS were structured questionnaires based on the MICS3 Model Questionnaire with some modi

In addition to a household questionnaire, questionnaires were administered in each household for women age 15-49 and childre

The women's questionnaire include women's characteristics, child mortality, tetanus toxoid, maternal and newborn health, mar

The children's questionnaire includes children's characteristics, birth registration and early learning, vitamin A, breastfe

The questionnaires were developed in English from the MICS3 Model Questionnaires, and were translated into Mumbo-jumbo. Afte The English and Mumbo-jumbo questionnaires were both piloted as part of the survey pretest.

All questionnaires and modules are provided as external resources.

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Scope_SummaryDataDescription_GeographicCoverage" Label="Geographic Coverage of

Program" Mandatory="TRUE">

- <Description>

- <![CDATA[

This field aims at describing at what geographic level the data are representative. Typical entries will be "National coverage", "Urban (or rural) areas only", "State of ...", "Capital city", etc.

Note that we do not describe here where the data was collected. For example, as sample survey could be declared as "national

MCC Clarification:

This description should indicate where the program is being implemented (nationally, regionally, etc) with specifically defi

</Description> <LinkedTextListItem />

</Item> </Tab>

- <Tab Name="Scope">

- <Item ID="StudyDescription_Scope_TopicClassifications" Label="Topics Classifications">

- <Description>

- <![CDATA[

A topic classification facilitates referencing and searches in electronic survey catalogs. Topics should be selected from a standard thesaurus, preferably an international, multilingual thesaurus.

The IHSN recommends the use of the thesaurus used by the Council of European Social Science Data Archives (CESSDA). The CESS

Content and Format:

Select from controlled vocabulary options:

See CESSDA Vocabulary menu options (or "Topics") in the MCC Evaluation Catalog: http://data.mcc.gov/evaluations/index.php/ca

</Description>

- <KeywordsItem>

- <KWCtrlVocab Name="World Bank">

- <KWVocabItem Value="Agriculture & Rural Development">

<KWVocabItem Value="Agriculture & Rural Development" /> <KWVocabItem Value="Forests & Forestry" /> <KWVocabItem Value="Food (production, crisis)" /> <KWVocabItem Value="Land (policy, resource management)" />

</KWVocabItem>

- <KWVocabItem Value="Aid Effectiveness">

<KWVocabItem Value="Aid Effectiveness" /> <KWVocabItem Value="Impact Evaluation" /> <KWVocabItem Value="Millennium Development Goals" />

</KWVocabItem>

- <KWVocabItem Value="Economic Policy & Debt">

<KWVocabItem Value="Economic Policy" /> <KWVocabItem Value="Debt Management" /> <KWVocabItem Value="Debt Relief/ HIPC" /> <KWVocabItem Value="Decentralization/ Subnational Regional Economics" /> <KWVocabItem Value="Fiscal Policy" /> <KWVocabItem Value="Macroeconomics & Growth" />

</KWVocabItem>

- <KWVocabItem Value="Education">

<KWVocabItem Value="Education" /> <KWVocabItem Value="Primary Education" /> <KWVocabItem Value="Secondary Education" /> <KWVocabItem Value="Tertiary Education" /> <KWVocabItem Value="Vocational Education" /> <KWVocabItem Value="Girls’ Education" /> <KWVocabItem Value="Educational Technology" />

</KWVocabItem>

- <KWVocabItem Value="Energy & Mining">

<KWVocabItem Value="Energy" /> <KWVocabItem Value="Clean Energy / Renewables" /> <KWVocabItem Value="Coal" /> <KWVocabItem Value="Electricity" /> <KWVocabItem Value="Hydropower" /> <KWVocabItem Value="Mining" /> <KWVocabItem Value="Oil & Gas" />

</KWVocabItem>

- <KWVocabItem Value="Environment">

<KWVocabItem Value="Environment" /> <KWVocabItem Value="Biodiversity" /> <KWVocabItem Value="Carbon Finance" /> <KWVocabItem Value="Climate Change" /> <KWVocabItem Value="Coastal & Marine Management" /> <KWVocabItem Value="Environmental Health/ Pollution Management" /> <KWVocabItem Value="Safeguards" />

</KWVocabItem>

- <KWVocabItem Value="Financial Sector">

<KWVocabItem Value="Financial Sector" /> <KWVocabItem Value="Access to Finance" /> <KWVocabItem Value="Financial Market Integrity (Anti-Money Laundering)" /> <KWVocabItem Value="Migration & Remittances" /> <KWVocabItem Value="Payment Systems" />

</KWVocabItem>

- <KWVocabItem Value="Health">

<KWVocabItem Value="Health" /> <KWVocabItem Value="Health Systems & Financing" /> <KWVocabItem Value="HIV/AIDS" /> <KWVocabItem Value="Malaria" /> <KWVocabItem Value="Mental Health" /> <KWVocabItem Value="Nutrition" /> <KWVocabItem Value="Pandemic Flu (including H1N1, Avian Flu)" /> <KWVocabItem Value="Population & Reproductive Health" /> <KWVocabItem Value="Tuberculosis" />

</KWVocabItem>

- <KWVocabItem Value="Infrastructure">

<KWVocabItem Value="Infrastructure" /> <KWVocabItem Value="Information & Communication Technologies" /> <KWVocabItem Value="Transport" /> <KWVocabItem Value="Water" />

</KWVocabItem>

- <KWVocabItem Value="Labor & Social Protection">

<KWVocabItem Value="Social Protection (includes Pensions, Safety Nets, Social Funds)" /> <KWVocabItem Value="Disability" /> <KWVocabItem Value="Labor Markets" />

</KWVocabItem>

- <KWVocabItem Value="Poverty">

<KWVocabItem Value="Poverty" /> <KWVocabItem Value="Fragile & Conflict-affected States" /> <KWVocabItem Value="Small States" />

</KWVocabItem>

- <KWVocabItem Value="Private Sector and Trade">

<KWVocabItem Value="Private Sector Development" /> <KWVocabItem Value="Doing Business / Business Regulation" /> <KWVocabItem Value="Trade" /> <KWVocabItem Value="Export Competitiveness" /> <KWVocabItem Value="Logistics/Trade Facilitation" />

</KWVocabItem>

- <KWVocabItem Value="Public Sector">

<KWVocabItem Value="Public Sector" /> <KWVocabItem Value="Administrative & Civil Service Reform" /> <KWVocabItem Value="Anti-Corruption" /> <KWVocabItem Value="Financial Management" /> <KWVocabItem Value="Governance" /> <KWVocabItem Value="Law & Justice" /> <KWVocabItem Value="Public Finance" /> <KWVocabItem Value="Tax Policy & Administration" />

</KWVocabItem>

- <KWVocabItem Value="Social Development">

<KWVocabItem Value="Social Development" /> <KWVocabItem Value="Children & Youth" /> <KWVocabItem Value="Community Driven Development" /> <KWVocabItem Value="Faiths & Development" /> <KWVocabItem Value="Gender" /> <KWVocabItem Value="Indigenous Peoples" /> <KWVocabItem Value="Participation / Empowerment" /> <KWVocabItem Value="Resettlement" />

</KWVocabItem>

- <KWVocabItem Value="Urban Development">

<KWVocabItem Value="Urban Development" /> <KWVocabItem Value="Disaster Risk Management" /> <KWVocabItem Value="Municipal Finance" /> <KWVocabItem Value="Slum Prevention" /> <KWVocabItem Value="Solid Waste Management" />

</KWVocabItem> </KWCtrlVocab>

</KeywordsItem> </Item>

- <Item ID="StudyDescription_Scope_Keywords" Label="Searchable Keywords">

- <Description>

- <![CDATA[

Content and Format:

Text: Keywords to identify evaluation with in the public Evalaution Catalog Vocabulary: Leave blank until we have a controlled vocabulary selection to choose from.

Vocabulary URI: Leave blank

Words or phrases that describe salient aspects of a data collection's content. Can be used for building keyword indexes and f

</Description> <KeywordsItem />

</Item> </Tab>

- <Tab Name="Producers and Sponsors">

- <Item ID="StudyDescription_Citation_Authors" Label="Independent Evaluator" Mandatory="TRUE">

- <Description>

- <![CDATA[

Content and Format:

Name: Independent Evaluator Firm (or individual) Name Affiliation: For individuals, list the university or institution that they are affiliated with. Leave blank for evaluation f

MCC Clarification:

Provide the full unabbreviated name

</Description> <AuthorsItem />

</Item>

- <Item ID="StudyDescription_Citation_ProductionStatement_Fundings" Label="Fund Source">

- <Description>

- <![CDATA[

List the organizations (national or international) that have contributed, in cash or in kind, to the financing of the survey.

Content and Format:

Agency: Millennium Challenge Corporation Abbreviation: MCC

MCC Clarification:

MCC should already be listed here. This optional field can also be used to acknowledge any other people and institutions that

</Description>

- <FundingsItem> <Funding Agency="Millennium Challenge Corporation" Abbreviation="MCC" />

</FundingsItem> </Item>

</Tab>

- <Tab Name="Sampling">

- <Item ID="StudyDescription_Scope_SummaryDataDescription_Universe" Label="Study Population">

- <Description>

- <![CDATA[

Define study population.

Example:

Parents of and children 0-5 years old living in rural Tanzania.

</Description> <LinkedTextListItem />

</Item>

- <Item ID="StudyDescription_Methodology_Sampling" Label="Sampling Procedure">

- <Description>

- <![CDATA[

This field only applies to sample surveys. Information on sampling procedure is crucial (although not applicable for censuses and administrative datasets).

Content and Format:

Description of power calculations, sample sizes, selection process, level of representation, etc.

MCC Clarification:

Information on sampling procedure is crucial (although not applicable for censuses and administrative datasets). This section Required sample size and actual sample size, Selection process (e.g., probability proportional to size or over sampling), Stratification (implicit and explicit), Stages of sample selection, Level of representation, Strategy for absent respondents/not found/refusals (replacement or not), Sample frame used, and listing exercise conducted to update it

Example:

5000 households were selected for the sample. Of these, 4996 were occupied households and 4811 were successfully interviewed

</Description> <LinkedTextListItem />

</Item>

- <Item ID="StudyDescription_Methodology_Deviations" Label="Deviations from Sample Design">

- <Description>

- <![CDATA[

This field only applies to sample surveys.

MCC Clarification:

Sometimes the reality of the field requires a deviation from the sampling design (for example due to difficulty to access to

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Methodology_ResponseRate" Label="Response Rates">

- <Description>

- <![CDATA[

MCC Clarification:

Response rate provides that percentage of households (or other sample unit) that participated in the survey based on the ori

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Methodology_Weighting" Label="Weighting">

- <Description>

- <![CDATA[

This field only applies to sample surveys.

MCC Clarification:

Provide here the list of variables used as weighting coefficient. If more than one variable is a weighting variable, describ

Example:

Sample weights for the household data were computed as the inverse of the probability of selection of the household, compute

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Methodology_SamplingErrorEstimates" Label="Estimates of Sampling Error">

- <Description>

- <![CDATA[

MCC Clarification:

For sampling surveys, it is good practice to calculate and publish sampling error. This field is used to provide information

- A list of ratios/indicators for which sampling errors were computed.

- Details regarding the software used for computing the sampling error, and reference to the programs used (to be provided a

- Reference to the reports or other document where the results can be found (to be provided as external resources).

Example:

Estimates from a sample survey are affected by two types of errors: 1) non-sampling errors and 2) sampling errors. Non-sampl

If the sample of respondents had been a simple random sample, it would have been possible to use straightforward formulae f

Sampling errors have been calculated for a select set of statistics (all of which are proportions due to the limitations of

</Description> <LinkedTextItem />

</Item> </Tab>

- <Tab Name="Data Collection">

- <Item ID="StudyDescription_Scope_SummaryDataDescription_CollectionDates" Label="Data Collection Dates"

Mandatory="TRUE">

- <Description>

- <![CDATA[

DATE MUST BE ENTERED IN THE ISO FORMAT YYYY-MM-DD

Content and Format:

YYYY-MM-DD (Baseline); YYYY-MM-DD (Interim); YYYY-MM-DD (End-line)

MCC Clarification:

In some cases, data collection for a same survey can be conducted in waves. In such case, you should enter the start and end

</Description> <TimeSpansItem />

</Item>

- <Item ID="StudyDescription_Methodology_CollectionSituation" Label="Data Collection Notes">

- <Description>

- <![CDATA[

MCC Clarification:

Include any additional information and direct users to Data Collection Reports if available.

Example:

The pre-test for the survey took place from August 15, 2006 - August 25, 2006 and included 14 interviewers who would later b

Each interviewing team comprised of 3-4 female interviewers (no male interviewers were used due to the sensitivity of the su

Interviews averaged 35 minutes for the household questionnaire (excluding salt testing), 23 minutes for the women's question

Six staff members of GenCenStat provided overall fieldwork coordination and supervision. The overall field coordinator was

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Methodology_DataCollectors" Label="Data Collection Firm">

- <Description>

- <![CDATA[

This element is provided in order to record information regarding the persons and/or agencies that took charge of the data collection. This element includes 3 fields: Name, Abbreviation and the Affiliation. In most cases, we wil

Content and Format:

Name: Name of data collection firm(s) or survey firms.

Abbreviation: Abbreviation of Data collection firm name(s) or survey firm name(s).

MCC Clarification:

This is the data collection firm responsible for administering the questionnaire or interview or compiling the data. This re

Example:

Name: Central Statistics Office Abbreviation: CSO

</Description> <DataCollectorsItem />

</Item>

- <Item ID="StudyDescription_Methodology_MinimizeLossActions" Label="Data Collection Team Composition">

- <Description>

- <![CDATA[

MCC Clarification:

Please describe how data collection teams were organized (how many team members per team, how many teams per supervisor, how

Example:

Interviewing was conducted by teams of interviewers. Each interviewing team comprised of 3-4 female interviewers, a field edi

The role of the supervisor was to coordinator field data collection activities, including management of the field teams, supp

The field editor was responsible for reviewing each questionnaire at the end of the day, checking for missed questions, skip

Responsibilities of the supervisors and field editors are described in the Instructions for Supervisors and Field Editors, to

Field visits were also made by a team of central staff on a periodic basis during fieldwork. The senior staff of GenCenStat a

</Description> <LinkedTextItem />

</Item> </Tab>

- <Tab Name="Data Processing">

- <Item ID="StudyDescription_Methodology_CleaningOperations" Label="Data Cleaning">

- <Description>

- <![CDATA[

MCC Clarification:

Evaluator please describe the data cleaning process. E.g., consistency checking, wildcode checking, etc. Include the role of

The data editing should contain information on how the data was treated or controlled for in terms of consistency and coheren

- Was a hot deck or a cold deck technique used to edit the data?

- Were corrections made automatically (by program), or by visual control of the questionnaire?

- What software was used?

Example:

Data editing took place at a number of stages throughout the processing, including:

a) Office editing and coding

b) During data entry

c) Structure checking and completeness

d) Secondary editing

e) Structural checking of SPSS data files Detailed documentation of the editing of data can be found in the "Data processing guidelines" document provided as an extern

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_Methodology_Notes" Label="Data Entry Process">

- <Description>

- <![CDATA[

MCC Clarification:

Use this field to provide as much information as possible on the data entry design. This includes such details as:

- Mode of data entry (manual or by scanning, in the field/in regions/at headquarters)

- Computer architecture (laptop computers in the field, desktop computers, scanners, PDA, other; indicate the number of compu

- Software used

- Use (and rate) of double data entry

- Average productivity of data entry operators; number of data entry operators involved and their work schedule

Example:

Data entry was conducted by 12 data entry operators in tow shifts, supervised by 2 data entry supervisors, using a total of 7

100% verification of all variables was performed using independent verification, i.e. double entry of data, with separate com

</Description> <LinkedTextItem />

</Item> </Tab>

- <Tab Name="Data Access">

- <Item ID="StudyDescription_AccessConditions_UseStatement_ConfidentialityDeclaration_Required" Label="Data

Anonymization"> <Description>All microdata from MCC-financed evaluations must be anonymized at the individual level to protect the confidentiality of survey respondents. Any requests for non-anonymized data must go through the MCC Disclosure Review Board.</Description>

<BooleanItem /> </Item>

- <Item ID="StudyDescription_AccessConditions_UseStatement_Conditions" Label="Access Conditions">

- <Description>

- <![CDATA[

Each dataset should have an "Access policy" attached to it. The IHSN recommends three levels of accessibility:

- Public use files, accessible to all

- Licensed datasets, accessible under conditions

- Datasets only accessible in a data enclave, for the most sensitive and confidential data.

The IHSN has formulated standard, generic policies and access forms for each one of these three levels (which each country ca If the access policy is subject to regular changes, you should enter here a URL where the user will find detailed information

If the access policy is not subject to regular changes, you may enter more detailed information here. For a public use file f The dataset has been anonymized and is available as a Public Use Dataset. It is accessible to all for statistical and resear

1. The data and other materials will not be redistributed or sold to other individuals, institutions, or organizations withou

2. The data will be used for statistical and scientific research purposes only. They will be used solely for reporting of agg

3. No attempt will be made to re-identify respondents, and no use will be made of the identity of any person or establishment

4. No attempt will be made to produce links among datasets provided by the [National Data Archive], or among data from the [N

5. Any books, articles, conference papers, theses, dissertations, reports, or other publications that employ data obtained fr

6. An electronic copy of all reports and publications based on the requested data will be sent to the [National Data Archive]

The original collector of the data, the [National Data Archive], and the relevant funding agencies bear no responsibility for

</Description> <LinkedTextItem />

</Item>

- <Item ID="StudyDescription_AccessConditions_UseStatement_CitationRequirement" Label="Citation Requirement"

Mandatory="TRUE">

- <Description>

- <![CDATA[

Citation requirement is the way that the dataset should be referenced when cited in any publication. Every dataset should have a citation requirement. This will guarantee that the data producer gets proper credit, and that analytica

Content and Format:

Use of the dataset must be acknowledged using a citation which would include:

- the Identification of the Primary Investigator

- the title of the survey (including country, acronym and year of implementation)

- the survey reference number

- the source and date of download

Example:

Chicago (16th edition) (author-date)

Smith, Tom W., Peter V. Marsden, and Michael Hout. 2011. General Social Survey, 1972-2010 Cumulative File. ICPSR31521-v1. Chi

</Description>

- <LinkedTextItem>

- <Text>

- <![CDATA[

Use of the dataset must be acknowledged using a citation which would include:

- the Identification of the Primary Investigator

- the title of the survey (including country, acronym and year of implementation)

- the survey reference number

- the source and date of download

</Text>

</LinkedTextItem> </Item>

- <Item ID="StudyDescription_Citation_DistributorStatement_Contacts" Label="Contact Persons">

- <Description>

- <![CDATA[

Users of the data may need further clarification and information. This section may include the name-affiliation-email-URI of one or multiple contact persons. Avoid putting the name of individuals. The information provided her

MCC Clarification:

All inquiries should be directed to this generic address, rather than to specific MCC contacts.

Content and Format:

Name: Monitoring & Evaluation Division of the Millennium Challenge Corporation Affiliation: Leave blank Email: impact-eval@mcc.gov

</Description>

- <ContactsItem> <Contact Name="The World Bank Microdata Library" Affiliation="The World Bank" EMail="microdata@worldbank.org"

URI="http://microdata.worldbank.org" /> </ContactsItem>

</Item> </Tab>

</TabGroup> </StudyDesc>

- <FileDesc>

- <TabGroup>

- <Tab Name="Data Files">

- <Item ID="FileDescription_FileContents" Label="Contents">

- <Description>

- <![CDATA[

A data filename usually provides little information on its content. Provide here a description of this content. This description should clearly distinguish collected variables and derived variables. It is also useful to indicate

Examples:

- The file contains data related to section 3A of the household survey questionnaire (Education of household members aged 6 t

- The file contains derived data on household consumption, annualized and aggregated by category of products and services. Th

</Description> <LinkedTextItem />

</Item>

- <Item ID="FileDescription_ProductionPlace" Label="Producer">

<Description>Put the name of the agency that produced the data file. Most data files will have been produced by the survey primary investigator. In some cases however, auxiliary or derived files from other producers may be released with a data set. This may for example include CPI data generated by a different agency, or files containing derived variables generated by a researcher.</Description>

<LinkedTextItem /> </Item>

- <Item ID="FileDescription_Version_Text" Label="Version"> <Description>A data file may undergo various changes and modifications. These file specific versions can be tracked in this element. This field will in most cases be left empty. It is more important to fill the field identifying the version of the dataset (see above).</Description>

<LinkedTextItem /> </Item>

- <Item ID="FileDescription_ProcessingChecks" Label="Processing Checks">

- <Description>

- <![CDATA[

Use this element if needed to provide information about the types of checks and operations that have been performed on the data file to make sure that the data are as correct as possible, e.g. consistency checking, wildcode checki

You may also provide here a reference to an external resource that contains the specifications for the data processing check

</Description> <LinkedTextItem />

</Item>

- <Item ID="FileDescription_MissingData" Label="Missing Data">

<Description>Missing data can be given certain coding. A common convention is to iterate the number "9"to fill a field.

This value needs to be defined as missing in the data set and can be explained in detail in this element.</Description>

<LinkedTextItem /> </Item>

- <Item ID="FileDescription_Notes" Label="Notes"> <Description>This field, aiming to provide information to the user on items not covered elsewhere, will in most cases be left empty.</Description> <LinkedTextItem />

</Item> </Tab>

</TabGroup> </FileDesc>

- <VarDesc>

- <TabGroup>

- <Tab Name="Description">

- <Item ID="VarDoc_Text" Label="Definition">

- <Description>

- <![CDATA[

This element provides a space to describe the variable in detail. Not all variables require definition. The following variables should always be defined when available in a questionnaire:

- Household (attach this definition to the "household ID" variable

- Head of household (attach this definition to the variable "relationship to the head"

- Urban/rural

</Description> <TextItem />

</Item>

- <Item ID="VarDoc_Concepts" Label="Concepts">

- <Description>

- <![CDATA[

Greater description on the nature of the variable can be placed in this element. For example this element can provide a clearer definition for certain variables (i.e. a variable that provides information on whether a person is a h

Example:

A household member is defined as any person who has been resident in the household for six months or more in a given year an

</Description> <KeywordsItem />

</Item> </Tab>

</TabGroup> </VarDesc>

</Template> </Templates>