<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="JOR_2004_PHC_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_WB_JOR_2004_PHC_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="DECDG" affiliation="World Bank" role="Documentation of the DDI">Development Economics Data Group</producer>
      <prodDate date="">
        <_value></_value>
      </prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 01 (August 2011)</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Population and Housing Census 2004</titl>
      <subTitl/>
      <altTitl/>
      <parTitl/>
      <IDNo>JOR_2004_PHC_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">Department of Statistics (DOS)</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-08">NADA</software>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <distrbtr abbr="" affiliation="" URI="">The Hashemite Kingdom of Jordan-Department of Statistics Public Relations PO BOX 2015 Amman Jordan Tel 00962 - 6 - 5300700 Fax 00962 - 6 - 5300710 Email stat@dos.gov.jo Web www.dos.gov.jo</distrbtr>
      <contact affiliation="" URI="http://www.dos.gov.jo" email="stat@dos.gov.jo">Department of Statistics</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Population and Housing Census [hh/popcen]</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date=""/>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
                  
                  
    </subject>
    <abstract>Main Objectives of the Census:
The comprehensive census is characterized with the following unique features compared to other statistical operations:
1. It providers comprehensive and detailed data on all population of the Kingdom, their demographic and socio-economic characteristics at the lowest administrative of geographic level.
2. It provides the necessary data for evaluating the population status in the Kingdom during period separating the two census, in addition to monitoring the demographic and socio-economic variations occurred on the population during that period for all administrative regions from the locality level till the governorate level.
3. It provides the possibility of limiting the size, distribution and characteristics of non-Jordanians in the Kingdom including the expatriate labour force at a high level of accuracy instead of depending upon estimations and expectations, in addition to identifying the size of Jordanians abroad where certain specifications apply to them.
4. It provides data on available housing units, their utilities, characteristics and living conditions related situation. It also provides the essential basic data for formulating a clear housing policy.
5. It provides a comprehensive and updated frame for the buildings, housing units households and enterprises according to various localities and administrative divisions. This frame is fundamental in the process of designing and drawing of samples for carrying out various future surveys.
6. It provides a data base for each household that can be linked to available maps through the geographic information system (GIS) these data could be linked to other available services information such as schools, health centers, roads, universities, civil defense centers, police stations … etc. It is also possible to identify the household and individuals, addresses quickly through use of the computer and this system.

The data collected in the census directly serve data users in the public and private sectors at various levels. This helps in sound planning and decision taking based on accurate information.</abstract>
    <sumDscr>
      <collDate date="2004-10-01" event="start" cycle=""/>
      <collDate date="2004-10-01" event="end" cycle=""/>
      <nation abbr="JOR">Jordan</nation>
      <geogCover>National</geogCover>
      <geogUnit/>
      <anlyUnit/>
      <universe/>
      <dataKind>Census/enumeration data [cen]</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>The scope of Jordan 2004 PHC includes:
- Demography
- Economic activities
- Education status
- Housing conditions</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>Face-to-face [f2f]</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=""/>
      <origArch/>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
