Description:
Every element in the DDI DTD/Schema has the following attributes:
ID - This uniquely identifies each element.
xml-lang - Use of this attribute is deprecated, and it will no longer be supported in the next major version of the DDI specification. For newly created XML documents, please use xml:lang.
xml:lang - This attribute specifies the language used in the contents and attribute values of any element in the XML document. Use of ISO (www.iso.org) language codes is recommended.
source - This attribute identifies the source that provided information in the element. If the documentation contains two differing sets of information on Sampling Procedure -- one provided by the data producer and one by the archive where the data is deposited -- this information can be distinguished through the use of the source attribute.
Note also that the DDI contains a linking mechanism permitting arbitrary links between internal elements and from internal elements to external sources.
The top-level element, codeBook (0.0) also includes a version attribute to specify the version number of the DDI specification.
Mention of formatting elements: p, emph, list, itm, etc.???
Description: The Document Description consists of bibliographic information describing the DDI-compliant document itself as a whole. This Document Description can be considered the wrapper or header whose elements uniquely describe the full contents of the compliant DDI file. Since the Document Description section is used to identify the DDI-compliant file within an electronic resource discovery environment, this section should be as complete as possible. The author in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived. The producer in the Document Description should be the agency or person that prepared the marked-up document. Note that the Document Description section contains a Documentation Source subsection consisting of information about the source of the DDI-compliant file-- that is, the hardcopy or electronic codebook that served as the source for the marked-up codebook. These sections allow the creator of the DDI file to produce version, responsibility, and other descriptions relating to both the creation of that DDI file as a separate and reformatted version of source materials (either print or electronic) and the original source materials themselves.
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: List of terms and definitions used in the documentation. Provided to assist users in using the document correctly. This element was intended to reflect the section in OSIRIS codebooks that assisted users in reading and interpreting a codebook. Each OSIRIS codebook contained a sample codebook page that defined the codebook conventions.
Description: Use this field to indicate if the documentation is being presented/distributed before it has been finalized. Some data producers and social science data archives employ data processing strategies that provide for release of data and documentation at various stages of processing.
Example(s):
<docStatus>This marked-up document includes a provisional data dictionary and brief citation only for the purpose of providing basic access to the data file. A complete codebook will be published at a later date.</docStatus>
Description: Citation for the source document. This element encodes the bibliographic information describing the source codebook, including title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any). Information for this section should be taken directly from the source document whenever possible. If additional information is obtained and entered in the elements within this section, the source of this information should be noted in the source attribute of the particular element tag. A MARCURI attribute is provided to link to the MARC record for this citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: The Study Description consists of information about the data collection, study, or compilation that the DDI-compliant documentation file describes. This section includes information about how the study should be cited, who collected or compiled the data, who distributes the data, keywords about the content of the data, summary (abstract) of the content of the data, data collection methods and processing, etc. Note that some content of the Study Description's Citation -- e.g., Responsibility Statement -- may be identical to that of the Documentation Citation. This is usually the case when the producer of a data collection also produced the print or electronic codebook for that data collection.
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: This section contains information about the data collection's scope across several dimensions, including substantive content, geography, and time.
Description: Subject information describing the data collection's intellectual content.
Description: Words or phrases that describe salient aspects of a data collection's content. Can be used for building keyword indexes and for classification and retrieval purposes. A controlled vocabulary can be employed. Maps to Dublin Core Subject element. The "vocab" attribute is provided for specification of the controlled vocabulary in use, e.g., LCSH, MeSH, etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<keyword vocab="ICPSR Subject Thesaurus" vocabURI="http://www.icpsr.umich.edu/thesaurus/subject.html"> quality of life</keyword> <keyword vocab="ICPSR Subject Thesaurus" vocabURI="http://www.icpsr.umich.edu/thesaurus/subject.html"> family</keyword> <keyword vocab="ICPSR Subject Thesaurus" vocabURI="http://www.icpsr.umich.edu/thesaurus/subject.html"> career goals</keyword>
Description: The classification field indicates the broad substantive topic(s) that the data cover. Library of Congress subject terms may be used here. The "vocab" attribute is provided for specification of the controlled vocabulary in use, e.g., LCSH, MeSH, etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary. Maps to Dublin Core Subject element. Inclusion of this element in the codebook is recommended.
Example(s):
<topcClas vocab="LOC Subject Headings" vocabURI="http://www.loc.gov/catdir/cpso/lcco/lcco.html"> Public opinion -- California -- Statistics</topcClas> <topcClas vocab="LOC Subject Headings" vocabURI="http://www.loc.gov/catdir/cpso/lcco/lcco.html">Elections -- California</topcClas>
Description: An unformatted summary describing the purpose, nature, and scope of the data collection, special characteristics of its contents, major subject areas covered, and what questions the PIs attempted to answer when they conducted the study. A listing of major variables in the study is important here. In cases where a codebook contains more than one abstract (for example, one might be supplied by the data producer and another prepared by the data archive where the data are deposited), the "source" and "date" attributes may be used to distinguish the abstract versions. Maps to Dublin Core Description element. Inclusion of this element in the codebook is recommended. The "date" attribute should follow ISO convention of YYYY-MM-DD.
Example(s):
<abstract date="1999-01-28" source="ICPSR"> Data on labor force activity for the week prior to the survey are supplied in this collection. Information is available on the employment status, occupation, and industry of persons 15 years old and over. Demographic variables such as age, sex, race, marital status, veteran status, household relationship, educational background, and Hispanic origin are included. In addition to providing these core data, the May survey also contains a supplement on work schedules for all applicable persons aged 15 years and older who were employed at the time of the survey. This supplement focuses on shift work, flexible hours, and work at home for both main and second jobs.</abstract>
Description: Information about a study's chronological and geographic coverage and unit of analysis.
Description: The time period to which the data refer. This item reflects the time period covered by the data, not the dates of coding or making documents machine-readable or the dates the data were collected. Also known as span. Use the event attribute to specify "start", "end", or "single" for each date entered. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. The "cycle" attribute permits specification of the relevant cycle, wave, or round of data. Maps to Dublin Core Coverage element. Inclusion of this element is recommended.
Example(s):
<timePrd event="start" date="1998-05-01">May 1, 1998</timePrd>
<timePrd event="end" "date=1998-05-31">May 31, 1998</timePrd>
Description: Contains the date(s) when the data were collected. Use the event attribute to specify "start", "end", or "single" for each date entered. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. The "cycle" attribute permits specification of the relevant cycle, wave, or round of data. Maps to Dublin Core Coverage element. Inclusion of this element in the codebook is recommended.
Example(s):
<collDate event="single" date="1998-11-10">10 November 1998</collDate>
Description: Indicates the country or countries covered in the file. Attribute "abbr" may be used to list common abbreviations; use of ISO country codes is recommended. Maps to Dublin Core Coverage element. Inclusion of this element is recommended.
Example(s):
<nation abbr="GB">United Kingdom</nation>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Information on the geographic coverage of the data. Includes the total geographic scope of the data, and any additional levels of geographic coding provided in the variables. Maps to Dublin Core Coverage element. Inclusion of this element in the codebook is recommended.
Example(s):
<geogCover>State of California</geogCover>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Lowest level of geographic aggregation covered by the data.
Example(s):
<geogUnit>state</geogUnit>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The fundamental geometric description for any dataset that models geography. GeoBndBox is the minimum box, defined by west and east longitudes and north and south latitudes, that includes the largest geographic extent of the dataset's geographic coverage. This element is used in the first pass of a coordinate-based search. If the boundPoly element is included, then the geoBndBox element MUST be included.
Example(s):
<geogCover>Nevada State</geogCover>
<geoBndBox>
<westBL>-120.005729004</westBL>
<eastBL>-114.039663</eastBL>
<southBL>35.00208499998</southBL>
<northBL>42.002207</northBL>
</geoBndBox>
<geogCover>Norway</geogCover>
<geoBndBox>
<westBL>4.789583</westBL>
<eastBL>33.637497</eastBL>
<southBL>57.987915</southBL>
<northBL>80.76416</northBL>
</geoBndBox>
Description: The westernmost coordinate delimiting the geographic extent of the dataset. A valid range of values, expressed in decimal degrees (positive east and positive north), is: -180,0 <= West Bounding Longitude Value <= 180,0
Description: The easternmost coordinate delimiting the geographic extent of the dataset. A valid range of values, expressed in decimal degrees (positive east and positive north), is: -180,0 <= East Bounding Longitude Value <= 180,0
Description: The southernmost coordinate delimiting the geographic extent of the dataset. A valid range of values, expressed in decimal degrees (positive east and positive north), is: -90,0 <= South Bounding Latitude Value <= 90,0 ; South Bounding Latitude Value <= North Bounding Latitude Value
Description: The northernmost coordinate delimiting the geographic extent of the dataset. A valid range of values, expressed in decimal degrees (positive east and positive north), is: -90,0 <= North Bounding Latitude Value <= 90,0 ; North Bounding Latitude Value = South Bounding Latitude Value
Description:
This field allows the creation of multiple polygons to describe in a more detailed manner the geographic area covered by the dataset. It should only be used to define the outer boundaries of a covered area. For example, in the United States, such polygons can be created to define boundaries for Hawaii, Alaska, and the continental United States, but not interior boundaries for the contiguous states. This field is used to refine a coordinate-based search, not to actually map an area.
If the boundPoly element is used, then geoBndBox MUST be present, and all points enclosed by the boundPoly MUST be contained within the geoBndBox. Elements westBL, eastBL, southBL, and northBL of the geoBndBox should each be represented in at least one point of the boundPoly description.
Example(s):
<geogCover>Nevada State</geogCover>
<boundPoly>
<polygon>
<point><gringLat>42.002207</gringLat><gringLon>-120.005729004</gringLon></point>
<point><gringLat>42.002207</gringLat><gringLon>-114.039663</gringLon></point>
<point><gringLat>35.9</gringLat><gringLon>-114.039663</gringLon></point>
<point><gringLat>36.080</gringLat><gringLon>-114.544</gringLon></point>
<point><gringLat>35.133</gringLat><gringLon>-114.542</gringLon></point>
<point><gringLat>35.00208499998</gringLat><gringLon>-114.63288</gringLon></point>
<point><gringLat>35.00208499998</gringLat><gringLon>-114.63323</gringLon></point>
<point><gringLat>38.999</gringLat><gringLon>-120.005729004</gringLon></point>
<point><gringLat>42.002207</gringLat><gringLon>-120.005729004</gringLon></point>
</polygon>
</boundPoly>
<geogCover>Norway</geogCover>
<boundPoly>
<polygon>
<point><gringLat>80.76416</gringLat><gringLon>33.637497</gringLon></point>
<point><gringLat>80.76416</gringLat><gringLon>10.2</gringLon></point>
<point><gringLat>62.48395</gringLat><gringLon>4.789583</gringLon></point>
<point><gringLat>57.987915</gringLat><gringLon>4.789583</gringLon></point>
<point><gringLat>57.987915</gringLat><gringLon>11.8</gringLon></point>
<point><gringLat>61.27794</gringLat><gringLon>13.2336</gringLon></point>
<point><gringLat>63.19012</gringLat><gringLon>13.2336</gringLon></point>
<point><gringLat>67.28615</gringLat><gringLon>17.24580</gringLon></point>
<point><gringLat>68.14297</gringLat><gringLon>21.38362</gringLon></point>
<point><gringLat>68.14297</gringLat><gringLon>25.50054</gringLon></point>
<point><gringLat>69.39685</gringLat><gringLon>27.38137</gringLon></point>
<point><gringLat>68.76991</gringLat><gringLon>28.84424</gringLon></point>
<point><gringLat>68.76991</gringLat><gringLon>31.31021</gringLon></point>
<point><gringLat>71.42</gringLat><gringLon>31.31021</gringLon></point>
<point><gringLat>71.42</gringLat><gringLon>33.637497</gringLon></point>
<point><gringLat>80.76416</gringLat><gringLon>33.637497</gringLon></point>
</polygon>
</boundPoly>
Description: The minimum polygon that covers a geographical area, and is delimited by at least 4 points (3 sides), in which the last point coincides with the first point.
Description: 0-dimensional geometric primitive, representing a position, but not having extent. In this declaration, point is limited to a longitude/latitude coordinate system.
Description: Latitude (y coordinate) of a point. Valid range expressed in decimal degrees is as follows: -90,0 to 90,0 degrees (latitude)
Description: Longitude (x coordinate) of a point. Valid range expressed in decimal degrees is as follows: -180,0 to 180,0 degrees (longitude)
Description: Basic unit of analysis or observation that the file describes: individuals, families/households, groups, institutions/organizations, administrative units, etc. The "unit" attribute is included to permit the development of a controlled vocabulary for this element.
Example(s):
<anlyUnit>individuals</anlyUnit>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.
Example(s):
<universe clusion="I">Individuals 15-19 years of age. </universe> <universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The type of data included in the file: survey data, census/enumeration data, aggregate data, clinical data, event/transaction data, program source code, machine-readable text, administrative records data, experimental data, psychological test, textual data, coded textual, coded documents, time budget diaries, observation data/ratings, process-produced data, etc. This element maps to Dublin Core Type element.
Example(s):
<dataKind>survey data</dataKind>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: This section describes the methodology and processing involved in a data collection.
Description: Information about the methodology employed in a data collection.
Description: The time method or time dimension of the data collection. The "method" attribute is included to permit the development of a controlled vocabulary for this element.
Example(s):
<timeMeth>panel survey</timeMeth> <timeMeth>cross-section</timeMeth> <timeMeth>trend study</timeMeth> <timeMeth>time-series</timeMeth>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The entity (individual, agency, or institution) responsible for administering the questionnaire or interview or compiling the data. This refers to the entity collecting the data, not to the entity producing the documentation. Attribute "abbr" may be used to list common abbreviations given to agencies, etc. Attribute "affiliation" may be used to record affiliation of the data collector.
Example(s):
<dataCollector abbr="SRC" affiliation="University of Michigan">Survey Research Center</dataCollector>
Description: For data collected at more than one point in time, the frequency with which the data were collected. The "freq" attribute is included to permit the development of a controlled vocabulary for this element.
Example(s):
<freq>monthly</freq> <freq>quarterly</freq>
Description: The type of sample and sample design used to select the survey respondents to represent the population. May include reference to the target sample size and the sampling fraction.
Example(s):
<sampProc>National multistage area probability sample</sampProc>
<sampProc>Simple random sample</sampProc>
<sampProc>Stratified random sample</sampProc>
<sampProc>Quota sample</sampProc>
<sampProc>The 8,450 women interviewed for the NSFG, Cycle IV, were drawn from households in which
someone had been interviewed for the National Health Interview Survey (NHIS), between October 1985
and March 1987.</sampProc>
<sampProc>Samples sufficient to produce approximately 2,000 families with completed interviews were
drawn in each state. Families containing one or more Medicaid or uninsured persons were oversampled.</sampProc>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Information indicating correspondence as well as discrepancies between the sampled units (obtained) and available statistics for the population (age, sex-ratio, marital status, etc.) as a whole.
Example(s):
<deviat>The suitability of Ohio as a research site reflected its similarity to the United States as a whole. The evidence extended by Tuchfarber (1988) shows that Ohio is representative of the United States in several ways: percent urban and rural, percent of the population that is African American, median age, per capita income, percent living below the poverty level, and unemployment rate. Although results generated from an Ohio sample are not empirically generalizable to the United States, they may be suggestive of what might be expected nationally.</deviat>
Description: The method used to collect the data; instrumentation characteristics.
Example(s):
<collMode>telephone interviews</collMode> <collMode>face-to-face interviews</collMode> <collMode>mail questionnaires</collMode> <collMode>computer-aided telephone interviews (CATI)</collMode>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The type of data collection instrument used. "Structured" indicates an instrument in which all respondents are asked the same questions/tests, possibly with precoded answers. If a small portion of such a questionnaire includes open-ended questions, provide appropriate comments. "Semi-structured" indicates that the research instrument contains mainly open-ended questions. "Unstructured" indicates that in-depth interviews were conducted. The "type" attribute is included to permit the development of a controlled vocabulary for this element.
Example(s):
<resInstru>structured</resInstru>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Description of sources used for the data collection. The element is nestable so that the sources statement might encompass a series of discrete source statements, each of which could contain the facts about an individual source. This element maps to Dublin Core Source element.
Description: Used to list the book(s), article(s), serial(s), and/or machine-readable data file(s)--if any--that served as the source(s) of the data collection.
Example(s):
<dataSrc> "Voting Scores." CONGRESSIONAL QUARTERLY ALMANAC 33 (1977), 487-498.</dataSrc>
<dataSrc>United States Internal Revenue Service Quarterly Payroll File</dataSrc>
Description: For historical materials, information about the origin(s) of the sources and the rules followed in establishing the sources should be specified. May not be relevant to survey data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Assessment of characteristics and quality of source material. May not be relevant to survey data.
Description: Level of documentation of the original sources. May not be relevant to survey data.
Description: Description of noteworthy aspects of the data collection situation. Includes information on factors such as cooperativeness of respondents, duration of interviews, number of call-backs, etc.
Example(s):
<collSitu>There were 1,194 respondents who answered questions in face-to-face interviews
lasting approximately 75 minutes each.</collSitu>
Description: Summary of actions taken to minimize data loss. Includes information on actions such as follow-up visits, supervisory checks, historical matching, estimation, etc.
Example(s):
<actMin>To minimize the number of unresolved cases and reduce the potential nonresponse bias, four follow-up contacts were made with agencies that had not responded by various stages of the data collection process.</actMin>
Description: Methods to facilitate data control performed by the primary investigator or by the data archive. Specify any special programs used for such operations. The "agency" attribute maybe used to refer to the agency that performed the control operation.
Example(s):
<ConOps source="ICPSR">Ten percent of data entry forms were reentered to check for accuracy.</ConOps>
Description: The use of sampling procedures may make it necessary to apply weights to produce accurate statistical results. Describe here the criteria for using weights in analysis of a collection. If a weighting formula or coefficient was developed, provide this formula, define its elements, and indicate how the formula is applied to data.
Example(s):
<weight>The 1996 NES dataset includes two final person-level analysis weights which incorporate sampling, nonresponse, and post-stratification factors. One weight (variable #4) is for longitudinal micro-level analysis using the 1996 NES Panel. The other weight (variable #3) is for analysis of the 1996 NES combined sample (Panel component cases plus Cross-section supplement cases). In addition, a Time Series Weight (variable #5) which corrects for Panel attrition was constructed. This weight should be used in analyses which compare the 1996 NES to earlier unweighted National Election Study data collections.</weight>
Description: Methods used to "clean" the data collection, e.g., consistency checking, wildcode checking, etc. The "agency" attribute permits specification of the agency doing the data cleaning.
Example(s):
<cleanOps>Checks for undocumented codes were performed, and data were subsequently revised in consultation with the principal investigator.</cleanOps>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Information on data appraisal.
Description: The percentage of sample members who provided information.
Example(s):
<respRate>For 1993, the estimated inclusion rate for TEDS-eligible providers was 91 percent,
with the inclusion rate for all treatment providers estimated at 76 percent (including privately and
publicly funded providers).</respRate>
<respRate>The overall response rate was 82%, although retail firms with an annual sales volume of more
than $5,000,000 were somewhat less likely to respond.</respRate>
Description: Measure of how precisely one can estimate a population value from a given sample.
Example(s):
<EstSmpErr> To assist NES analysts, the PC SUDAAN program was used to compute sampling errors for a wide-ranging example set of proportions estimated from the 1996 NES Pre-election Survey dataset. For each estimate, sampling errors were computed for the total sample and for twenty demographic and political affiliation subclasses of the 1996 NES Pre-election Survey sample. The results of these sampling error computations were then summarized and translated into the general usage sampling error table provided in Table 11. The mean value of deft, the square root of the design effect, was found to be 1.346. The design effect was primarily due to weighting effects (Kish, 1965) and did not vary significantly by subclass size. Therefore the generalized variance table is produced by multiplying the simple random sampling standard error for each proportion and sample size by the average deft for the set of sampling error computations.</EstSmpErr>
Description: Other issues pertaining to data appraisal. Describe here issues such as response variance, nonresponse rate and testing for bias, interviewer and response bias, confidence levels, question bias, etc.
Example(s):
<dataAppr>These data files were obtained from the United States House of Representatives, who received them from the Census Bureau accompanied by the following caveats: "The numbers contained herein are not official 1990 decennial Census counts. The numbers represent estimates of the population based on a statistical adjustment method applied to the official 1990 Census figures using a sample survey intended to measure overcount or undercount in the Census results. On July 15, 1991, the Secretary of Commerce decided not to adjust the official 1990 decennial Census counts (see 56 Fed. Reg. 33582, July 22, 1991). In reaching his decision, the Secretary determined that there was not sufficient evidence that the adjustment method accurately distributed the population across and within states. The numbers contained in these tapes, which had to be produced prior to the Secretary's decision, are now known to be biased. Moreover, the tapes do not satisfy standards for the publication of Federal statistics, as established in Statistical Policy Directive No. 2, 1978, Office of Federal Statistical Policy and Standards. Accordingly, the Department of Commerce deems that these numbers cannot be used for any purpose that legally requires use of data from the decennial Census and assumes no responsibility for the accuracy of the data for any purpose whatsoever. The Department will provide no assistance in interpretation or use of these numbers."</dataApp>
Description: Generally used to give the data archive's class or study status number, which indicates the processing status of the study. May also be used as a text field to describe processing status.
Example(s):
<stdyClas>ICPSR Class II</stdyClas>
<stdyClas>DDA Class C</stdyClas>
<stdyClas>Available from the DDA. Being processed. </stdyClas>
Description: This section describes access conditions and terms of use for the data collection. In cases where access conditions differ across individual files or variables, multiple access conditions can be specified. The access conditions applying to a study, file, variable group, or variable can be indicated by an IDREF attribute on the study, file, variable group, or variable elements called "access".
Description: Information on availability and storage of the collection. The "media" attribute may be used in combination with any of the subelements. See Location of Data Collection.
Description: Location where the data collection is currently stored. Use the URI attribute to provide a URN or URL for the storage site or the actual address from which the data may be downloaded.
Description: Archive from which the data collection was obtained; the originating archive.
Example(s):
<origArch>Zentralarchiv fuer empirische Sozialforschung</origArch>
Description: Statement of collection availability. An archive may need to indicate that a collection is unavailable because it is embargoed for a period of time, because it has been superseded, because a new edition is imminent, etc. It is anticipated that a controlled vocabulary will be developed for this element.
Example(s):
<avlStatus>This collection is superseded by CENSUS OF POPULATION, 1880 [UNITED STATES]: PUBLIC USE SAMPLE (ICPSR 6460).</avlStatus>
Description: Summarizes the number of physical files that exist in a collection, recording the number of files that contain data and noting whether the collection contains machine-readable documentation and/or other supplementary files and information such as data dictionaries, data definition statements, or data collection instruments.
Example(s):
<collSize>1 data file + machine-readable documentation (PDF) + SAS data definition statements </collSize>
Description: This item indicates the relationship of the data collected to the amount of data coded and stored in the data collection. Information as to why certain items of collected information were not included in the data file stored by the archive should be provided.
Example(s):
<complete>Because of embargo provisions, data values for some variables have been masked. Users should consult the data definition statements to see which variables are under embargo. A new version of the collection will be released by ICPSR after embargoes are lifted.</complete>
Description: Total number of physical files associated with a collection.
Example(s):
<fileQnty> 5 files</fileQnty>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Information on terms of use for the data collection.
Description: This element is used to determine if signing of a confidentiality declaration is needed to access a resource. The "required" attribute is used to aid machine processing of this element, and the default specification is "yes". The "formNo" attribute indicates the number or ID of the form that the user must fill out. The "URI" attribute may be used to provide a URN or URL for online access to a confidentiality declaration form.
Example(s):
<confDec formNo="1">To download this dataset, the user must sign a declaration of confidentiality. </confDec> <confDec URI="http://www.icpsr.umich.edu/HMCA/CTSform/contents.html"> To obtain this dataset, the user must complete a Restricted Data Use Agreement.</confDec>
Description: This element is used to determine if any special permissions are required to access a resource. The "required" attribute is used to aid machine processing of this element, and the default specification is "yes". The "formNo" attribute indicates the number or ID of the form that the user must fill out. The "URI" attribute may be used to provide a URN or URL for online access to a special permissions form.
Example(s):
<specPerm formNo="4">The user must apply for special permission to use this dataset locally
and must complete a confidentiality form.</specPerm>
Description: Any restrictions on access to or use of the collection such as privacy certification or distribution restrictions should be indicated here. These can be restrictions applied by the author, producer, or disseminator of the data collection. If the data are restricted to only a certain class of user, specify which type.
Example(s):
<restrctn> In preparing the data file(s) for this collection, the National Center for Health Statistics (NCHS) has removed direct identifiers and characteristics that might lead to identification of data subjects. As an additional precaution NCHS requires, under Section 308(d) of the Public Health Service Act (42 U.S.C. 242m), that data collected by NCHS not be used for any purpose other than statistical analysis and reporting. NCHS further requires that analysts not use the data to learn the identity of any persons or establishments and that the director of NCHS be notified if any identities are inadvertently discovered. ICPSR member institutions and other users ordering data from ICPSR are expected to adhere to these restrictions.</restrctn> <restrctn> ICPSR obtained these data from the World Bank under the terms of a contract which states that the data are for the sole use of ICPSR and may not be sold or provided to third parties outside of ICPSR membership. Individuals at institutions that are not members of the ICPSR may obtain these data directly from the World Bank.</restrctn>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: Text of requirement that a data collection should be cited properly in articles or other publications that are based on analysis of the data.
Example(s):
<citReq>Publications based on ICPSR data collections should acknowledge those sources by means of bibliographic citations. To ensure that such source attributions are captured for social science bibliographic utilities, citations must appear in footnotes or in the reference section of publications.</citReq>
Description: Information regarding user responsibility for informing archives of their use of data through providing citations to the published work or providing copies of the manuscripts.
Example(s):
<deposReq> To provide funding agencies with essential information about use of archival resources and to facilitate the exchange of information about ICPSR participants' research activities, users of ICPSR data are requested to send to ICPSR bibliographic citations for, or copies of, each completed manuscript or thesis abstract. Please indicate in a cover letter which data were used.</deposReq>
Description: Indicates any additional information that will assist the user in understanding the access and use conditions of the data collection.
Example(s):
<conditions>The data are available without restriction. Potential users of these datasets are advised, however, to contact the original principal investigator Dr. J. Smith (Institute for Social Research, The University of Michigan, Box 1248, Ann Arbor, MI 48106), about their intended uses of the data. Dr. Smith would also appreciate receiving copies of reports based on the datasets. </conditions>
Description: Information regarding responsibility for uses of the data collection.
Example(s):
<disclaimer>The original collector of the data, ICPSR, and the relevant funding agency bear no responsibility for uses of this collection or for interpretations or inferences based upon such uses.</disclaimer>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Other materials relating to the study description. This section describes other materials that are related to the study description that are primarily descriptions of the content and use of the study, such as appendices, sampling information, weighting details, methodological and technical details, publications based upon the study content, related studies or collections of studies, etc. This section may point to other materials related to the description of the study through use of the generic citation element (A.6), which is available for each element in this section. <othrStdyMat> maps to Dubli Core Relation element. Note that Section 5.0, Other Study-Related Materials, should be sued for materials used in the production of the study or useful in the analysis of the study. The materials in Section 5.0 may be entered as PCDATA (ASCII text) directly into the document (through use of the txt element). That section may also serve as a "container" for other electronic materials by providing a brief description of the study-related materials accompanied by the "type" and "level" attributes further defining the materials. Other Study-Related Materials in Section 5.0 may include: questionnaires, coding notes, SPSS/SAS/Stata setup files (and others), user manuals, continuity guides, sample computer software programs, glossaries of terms, interviewer/project instructions, maps, database schema, data dictionaries, show cards, coding information, interview schedules, missing values information, frequency files, variable maps, etc.
Description: Describes materials related to the study description, such as appendices, additional information on sampling found in other documents, etc. Can take the form of bibliographic citations. This element can contain either PCDATA or a citation or both, and there can be multiple occurrences of both the citation and PCDATA within a single element. May consist of a single URI or a series of URIs comprising a series of citations/references to external materials which can be objects as a whole (journal articles) or parts of objects (chapters or appendices in articles or documents).
Example(s):
<relMat> Full details on the research design and procedures, sampling methodology, content areas, and questionnaire design, as well as percentage distributions by respondent's sex, race, region, college plans, and drug use, appear in the annual ISR volumes MONITORING THE FUTURE: QUESTIONNAIRE RESPONSES FROM THE NATION'S HIGH SCHOOL SENIORS.</relMat> <relMat>Current Population Survey, March 1999: Technical Documentation includes an abstract, pertinent information about the file, a glossary, code lists, and a data dictionary. One copy accompanies each file order. When ordered separately, it is available from Marketing Services Office, Customer Service Center, Bureau of the Census, Washington, D.C. 20233. </relMat> <relMat>A more precise explanation regarding the CPS sample design is provided in Technical Paper 40, The Current Population Survey: Design and Methodology. Chapter 5 of this paper provides documentation on the weighting procedures for the CPS both with and without supplement questions.</relMat>
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Information on the relationship of the current data collection to others (e.g., predecessors, successors, other waves or rounds) or to other editions of the same file. This would include the names of additional data collections generated from the same data collection vehicle plus other collections directed at the same general topic. Can take the form of bibliographic citations.
Example(s):
<relStdy>ICPSR distributes a companion study to this collection titled FEMALE LABOR FORCE PARTICIPATION AND MARITAL INSTABILITY, 1980: [UNITED STATES] (ICPSR 9199).</relStdy>
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Bibliographic and access information about articles and reports based on the data in this collection. Can take the form of bibliographic citations.
Example(s):
<relPubl>Economic Behavior Program Staff. SURVEYS OF CONSUMER FINANCES. Annual volumes 1960 through 1970. Ann Arbor, MI: Institute for Social Research.</relPubl> <relPubl>Data from the March Current Population Survey are published most frequently in the Current Population Reports P- 20 and P- 60 series. These reports are available from the Superintendent of Documents, U. S. Government Printing Office, Washington, DC 20402. They also are available on the INTERNET at http:// www. census. gov. Forthcoming reports will be cited in Census and You, the Monthly Product Announcement (MPA), and the Bureau of the Census Catalog and Guide. </relPubl>
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Indicates other pertinent references. Can take the form of bibliographic citations.
Example(s):
<othRefs>Part II of the documentation, the Field Representative's Manual, is provided in hardcopy
form only.</othRefs>
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
Information about the data file(s) that comprises a collection. This section can be repeated for collections with multiple files.
The "URI" attribute may be a URN or a URL that can be used to retrieve the file. The "sdatrefs" are summary data description references that record the ID values of all elements within the summary data description section of the Study Description that might apply to the file. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data. The "methrefs" are methodology and processing references that record the ID values of all elements within the study methodology and processing section of the Study Description that might apply to the file. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates). The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Other Study Description Materials or Other Study-Related Materials that pertain to this file. "Access" records the ID values of all elements in the Data Access section that describe access conditions for this file.
Remarks: When a codebook documents two different physical instantiations of a data file, e.g., logical record length (or OSIRIS) and card-image version, the Data File Description should be repeated to describe the two separate files. An ID should be assigned to each file so that in the Variable section the location of each variable on the two files can be distinguished using the unique file IDs.
Example(s):
<fileDscr ID="CARD-IMAGE" URI="www.icpsr.umich.edu/cgi-bin/archive.prl?path=ICPSR&num=7728"/>
<fileDscr ID="LRECL" URI="www.icpsr.umich.edu/cgi-bin/archive.prl?path=ICPSR&num=7728"/>
Description: Information about the data file.
Description: Contains a short title that will be used to distinguish a particular file/part from other files/parts in the data collection.
Example(s):
<fileName ID="File1">Second-Generation Children Data </fileName>
Description: Abstract or description of the file. A summary describing the purpose, nature, and scope of the data file, special characteristics of its contents, major subject areas covered, and what questions the PIs attempted to answer when they created the file. A listing of major variables in the file is important here. In the case of multi-file collections, this uniquely describes the contents of each file.
Example(s):
<fileCont>Part 1 contains both edited and constructed variables describing demographic and
family relationships, income, disability, employment, health insurance status, and utilization data
for all of 1987. </fileCont>
Description: Type of file structure. The attribute "type" is used to indicate hierarchical, rectangular, relational, or nested (the default is rectangular). If the file is rectangular, the next relevant element is File Dimensions.
Description: Used to describe record groupings if the file is hierarchical or relational. The attribute "recGrp" allows a record group to indicate subsidiary record groups which nest underneath; this allows for the encoding of a hierarchical structure of record groups. The attribute "rectype" indicates the type of record, e.g., "A records" or "Household records." The attribute "keyvar" is an IDREF that provides the link to other record types. In a hierarchical study consisting of individual and household records, the "keyvar" on the person record will indicate the household to which it belongs. The attribute "rtypeloc" indicates the starting column location of the record type indicator variable on each record of the data file. The attribute "rtypewidth" specifies the width, for files with many different record types. The attribute "rtypevtype" specifies the type of the indicator variable. The "recidvar" indicates the variable that identifies the record group.
Example(s):
<fileStrc type="hierarchical">
<recGrp rectype="Person" keyvar="HHDID">
<labl>CPS 1999 Person-Level Record</labl>
<recDimnsn>
<varQnty>133</varQnty>
<caseQnty>1500</caseQnty>
<logRecL>852</logRecL>
</recDimnsn>
</recGrp>
</fileStrc>Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Information about the physical characteristics of the record. The "level" attribute on this element should be set to "record".
Description: Number of variables.
Example(s):
<varQnty>27</varQnty>
Description: Number of variables.
Example(s):
<varQnty>27</varQnty>
Description: Number of cases or observations.
Example(s):
<caseQnty>1011</caseQnty>
Description: Logical record length, i.e., number of characters of data in the record.
Example(s):
<logRecL>27</logRecL>
Description: Logical record length, i.e., number of characters of data in the record.
Example(s):
Example:
<logRecL>27</logRecL>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Dimensions of the overall file.
Description: Number of cases or observations.
Example(s):
<caseQnty>1011</caseQnty>
Description: Number of variables.
Example(s):
<varQnty>27</varQnty>
Description: Number of variables.
Example(s):
<varQnty>27</varQnty>
Description: Logical record length, i.e., number of characters of data in the record.
Example(s):
<logRecL>27</logRecL>
Description: Logical record length, i.e., number of characters of data in the record.
Example(s):
Example:
<logRecL>27</logRecL>
Description: Records per case in the file. This element should be used for card-image data or other files in which there are multiple records per case.
Example(s):
<dimensns><recPrCas>5</recPrCas></dimensns>
Description: Records per case in the file. This element should be used for card-image data or other files in which there are multiple records per case.
Example(s):
<dimensns><recPrCas>5</recPrCas></dimensns>
Description: Overall record count in file. Particularly helpful in instances such as files with multiple cards/decks or records per case.
Example(s):
<dimensns><recNumTot>2400</recNumTot></dimensns>
Description: Types of data files include raw data (ASCII, EBCDIC, etc.) and software-dependent files such as SAS datasets, SPSS export files, etc. If the data are of mixed types (e.g., ASCII and packed decimal), state that here. Note that the element varFormat permits specification of the data format at the variable level. The "charset" attribute allows one to specify the character set used in the file, e.g., US-ASCII, EBCDIC, UNICODE UTF-8, etc.
Example(s):
<fileType charset="US-ASCII">ASCII data file</fileType>
Description: Physical format of the data file: Logical record length format, card-image format (i.e., data with multiple records per case), delimited format, free format, etc.
Example(s):
<format>comma-delimited</format>
Description: Indicates whether the file was produced at an archive or produced elsewhere.
Example(s):
<filePlac>Washington, DC: United States Department of Commerce, Bureau of the Census</filePlac>
Description: Indicate here, at the file level, the types of checks and operations performed on the data file. A controlled vocabulary may be developed for this element in the future. The following examples are based on ICPSR's Extent of Processing scheme:
Example(s):
<dataChck>The archive produced a codebook for this collection.</dataChck>
<dataChck>Consistency checks were performed by Data Producer/ Principal Investigator.</dataChck>
<dataChck>Consistency checks performed by the archive.</dataChck>
<dataChck>The archive generated SAS and/or SPSS data definition statements for this collection.</dataChck>
<dataChck>Frequencies were provided by Data Producer/Principal Investigator.</dataChck>
<dataChck>Frequencies provided by the archive.</dataChck>
<dataChck>Missing data codes were standardized by Data Producer/ Principal Investigator.</dataChck>
<dataChck>Missing data codes were standardized by the archive.</dataChck>
<dataChck>The archive performed recodes and/or calculated derived variables. </dataChck>
<dataChck>Data were reformatted by the archive.</dataChck>
<dataChck>Checks for undocumented codes were performed by Data Producer/Principal Investigator.</dataChck>
<dataChck>Checks for undocumented codes were performed by the archive.</dataChck>
Description: Processing status of the file. Some data producers and social science data archives employ data processing strategies that provide for release of data and documentation at various stages of processing.
Example(s):
<ProcStat>Available from the DDA. Being processed.</ProcStat>
<ProcStat>The principal investigator notes that the data in Public Use Tape 5 are released prior to final
cleaning and editing, in order to provide prompt access to the NMES data by the research and policy
community.</ProcStat>
Description: This element can be used to give general information about missing data, e.g., that missing data have been standardized across the collection, missing data are present because of merging, etc.
Example(s):
<dataMsng>Missing data are represented by blanks.</dataMsng>
<dataMsng>The codes "-1" and "-2" are used to represent missing data.</dataMsng>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: This element maps individual data entries to one or more physical storage locations. It is used to describe the physical location of aggregate/tabular data in cases where the nCube model is employed.
Description: Identifies a physical storage location for an individual data entry, serving as a link between the physical location and the logical content description of each data item. The attribute "varRef" is an IDREF that points to a discrete variable description. If the data item is located within an nCube (aggregate data), use the attribute "nCubeRef" (IDREF) to point to the appropriate nCube and the element CubeCoord to identify the coordinates of the data item within the nCube.
Description: This is an empty element containing only the attributes listed below. It is used to identify the coordinates of the data item within a logical nCube describing aggregate data. CubeCoord is repeated for each dimension of the nCube giving the coordinate number ("coordNo") and coordinate value ("coordVal"). Coordinate value reference ("cordValRef") is an ID reference to the variable that carries the coordinate value. The attributes provide a complete coordinate location of a cell within the nCube.
Example(s):
<CubeCoord coordNo="1" coordVal="3"/>
<CubeCoord coordNo="2" coordVal="7"/>
<CubeCoord coordNo="3" coordVal="2"/>
Description:
This is an empty element containing only the attributes listed below. Attributes include "type" (type of file structure: rectangular, hierarchical, two-dimensional, relational), "recRef" (IDREF link to the appropriate file or recGrp element within a file), "startPos" (starting position of variable or data item), "endPos" (ending position of variable or data item), "width" (number of columns the variable/data item occupies), "RecSegNo" (the record segment number, deck or card number the variable or data item is located on), and "fileid" (an IDREF link to the fileDscr element for the file that includes this physical location).
Remarks: Where the same variable is coded in two different files, e.g., a fixed format file and a relational database file, simply repeat the physLoc element with the alternative location information. Note that if there is no width or ending position, then the starting position should be the ordinal position in the file, and the file would be described as free-format. New attributes will be added as other storage formats are described within the DDI.
Example(s):
<physLoc type="rectangular" recRef="R1" startPos="55" endPos="57" width="3"/>
<physLoc type="hierarchical" recRef="R6" startPos="25" endPos="25" width="1"/>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Description of variables.
Description:
A group of variables that may share a common subject, arise from the interpretation of a single question, or are linked by some other factor.
Variable groups are created this way in order to permit variables to belong to multiple groups, including multiple subject groups such as a group of variables on sex and income, or to a subject and a multiple response group, without causing overlapping groups. Variables that are linked by use of the same question need not be identified by a Variable Group element because they are linked by a common unique question identifier in the Variable element. Note that as a result of the strict sequencing required by XML, all Variable Groups must be marked up before the Variable element is opened. That is, the mark-up author cannot mark up a Variable Group, then mark up its constituent variables, then mark up another Variable Group.
The "type" attribute refers to the general type of grouping of the variables, e.g., subject, multiple response.
Specific variable groups, included within the "type" attribute, are:
Section: Questions which derive from the same section of the questionnaire, e.g., all variables located in Section C.
Multiple response: Questions where the respondent has the opportunity to select more than one answer from a variety of choices, e.g., what newspapers have you read in the past month (with the respondent able to select up to five choices).
Grid: Sub-questions of an introductory or main question but which do not constitute a multiple response group, e.g., I am going to read you some events in the news lately and you tell me for each one whether you are very interested in the event, fairly interested in the fact, or not interested in the event.
Display: Questions which appear on the same interview screen (CAI) together or are presented to the interviewer or respondent as a group.
Repetition: The same variable (or group of variables) which are repeated for different groups of respondents or for the same respondent at a different time.
Subject: Questions which address a common topic or subject, e.g., income, poverty, children.
Version: Variables, often appearing in pairs, which represent different aspects of the same question, e.g., pairs of variables (or groups) which are adjusted/unadjusted for inflation or season or whatever, pairs of variables with/without missing data imputed, and versions of the same basic question.
Iteration: Questions that appear in different sections of the data file measuring a common subject in different ways, e.g., a set of variables which report the progression of respondent income over the life course.
Analysis: Variables combined into the same index, e.g., the components of a calculation, such as the numerator and the denominator of an economic statistic.
Pragmatic: A variable group without shared properties.
Record: Variable from a single record in a hierarchical file.
File: Variable from a single file in a multifile study.
Randomized: Variables generated by CAI surveys produced by one or more random number variables together with a response variable, e.g, random variable X which could equal 1 or 2 (at random) which in turn would control whether Q.23 is worded "men" or "women", e.g., would you favor helping [men/women] laid off from a factory obtain training for a new job?
Other: Variables which do not fit easily into any of the categories listed above, e.g., a group of variables whose documentation is in another language.
The "var" attribute is used to reference all the constituent variable IDs in the group.
The "varGrp" attribute is used to reference all the subsidiary variable groups which nest underneath the current varGrp. This allows for encoding of a hierarchical structure of variable groups.
The attribute "name" provides a name, or short label, for the group.
The "sdatrefs" are summary data description references that record the ID values of all elements within the summary data description section of the Study Description that might apply to the group. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the group. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).
The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Section 2.5 or Section 5.0 that pertain to this variable group.
The "access" attribute records the ID values of all elements in Section 2.4 of the document that describe access conditions for this variable group.
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Rationale for why the group was constituted in this way.
Example(s):
<varGrp><defntn>The following eight variables were only asked in Ghana.</defntn></varGrp> <nCubeGrp><defntn>The following four nCubes form a single presentation table.</defntn></nCubeGrp>
Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.
Example(s):
<universe clusion="I">Individuals 15-19 years of age. </universe> <universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
A group of nCubes that may share a common subject, arise from the interpretation of a single question, or are linked by some other factor. This element makes it possible to identify all nCubes derived from a simple presentation table, and to provide the original table title and universe, as well as reference the source. Specific nesting patterns can be described using the attribute nCubeGrp.
nCube groups are also created this way in order to permit nCubes to belong to multiple groups, including multiple subject groups, without causing overlapping groups. nCubes that are linked by the same use of the same variable need not be identified by an nCubeGrp element because they are already linked by a common variable element. Note that as a result of the strict sequencing required by XML, all nCube Groups must be marked up before the Variable element is opened. That is, the mark-up author cannot mark up a nCube Group, then mark up its constituent nCubes, then mark up another nCube Group.
The "type" attribute refers to the general type of grouping of the nCubes. Specific nCube Groups, included within the 'type' attribute, are:
Display: nCubes that are part of the same presentation table.
Subject: nCubes that address a common topic or subject, e.g., income, poverty, children.
Iteration: nCubes that appear in different sections of the data file measuring a common subject in different ways, e.g., using different universes, units of measurement, etc.
Pragmatic: An nCube group without shared properties.
Record: nCubes from a single record in a hierarchical file.
File: nCube from a single file in a multifile study.
Other: nCubes that do not fit easily into any of the categories listed above, e.g., a group of nCubes whose documentation is in another language.
The "nCube" attribute is used to reference all the IDs of the nCubes belonging to the group.
The "nCubeGrp" attribute is used to reference all the subsidiary nCube groups which nest underneath the current nCubeGrp. This allows for encoding of a hierarchical structure of nCube groups.
The attribute "name" provides a name, or short label, for the group.
The "sdatrefs" are summary data description references that record the ID values of all elements within the summary data description section of the Study Description that might apply to the group. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the group. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).
The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Section 2.5 or Section 5.0 that pertain to this nCube group.
The "access" attribute records the ID values of all elements in Section 2.4 of the document that describe access conditions for this nCube group.
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Rationale for why the group was constituted in this way.
Example(s):
<varGrp><defntn>The following eight variables were only asked in Ghana.</defntn></varGrp> <nCubeGrp><defntn>The following four nCubes form a single presentation table.</defntn></nCubeGrp>
Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.
Example(s):
<universe clusion="I">Individuals 15-19 years of age. </universe> <universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
This element describes all of the features of a single variable in a social science data file. It includes the following attributes:
The attribute "name" usually contains the so-called "short label" for the variable, limited to eight characters in many statistical analysis systems such as SAS or SPSS.
The attribute "wgt" indicates whether the variable is a weight.
The attribute "wgt-var" references the weight variable(s) for this variable.
The attribute "qstn" is a reference to the question ID for the variable.
The attribute "files" is the IDREF identifying the file(s) to which the variable belongs.
The attribute "vendor" is the origin of the proprietary format and includes SAS, SPSS, ANSI, and ISO.
The attribute "dcml" refers to the number of decimal points in the variable.
The attribute "intrvl" indicates the interval type; options are discrete or continuous.
The "rectype" attribute refers to the record type to which the variable belongs.
The "sdatrefs" are summary data description references which record the ID values of all elements within the summary data description section of the Study Description which might apply to the variable. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the variable. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).
The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Other Study Description Materials or Other Study-Related Materials that pertain to this variable.
The attribute "access" records the ID values of all elements in the Data Access section that describe access conditions for this variable.
The "aggrMeth" attribute indicates the type of aggregation method used, for example 'sum', 'average', 'count'.
The attribute "measUnit" records the measurement unit, for example 'km', 'miles', etc.
The "scale" attribute records unit of scale, for example 'x1', 'x1000', etc.
The attribute "origin" records the point of origin for anchored scales.
The "nature" attribute records the nature of the variable, whether it is 'nominal', 'ordinal', 'interval', or 'ratio'.
The attribute "additivity" records type of additivity, such as 'stock', 'flow', 'non-additive'.
The attribute "temporal" indicates whether the variable relays time-related information.
The "geog" attribute indicates whether the variable relays geographic information.
The attribute "geoVocab" records the coding scheme used in the variable.
The attribute "catQnty" records the number of categories found in the variable, and is used primarily for aggregate data files for verifying cell counts in nCubes.
Description: This is an empty element containing only the attributes listed below. Attributes include "StartPos" (starting position of variable), "EndPos" (ending position of variable), "width" (number of columns the variable occupies), "RecSegNo" (the record segment number, deck or card number the variable is located on), and "fileid", an IDREF link to the fileDscr element for the file that this location is within (this is necessary in cases where the same variable may be coded in two different files, e.g., a logical record length type file and a card image type file). Note that if there is no width or ending position, then the starting position should be the ordinal position in the file, and the file would be described as free-format. The attribute "locMap" is an IDREF to the element locMap and serves as a pointer to indicate that the location information for the nCube's cells (aggregate data) is located in that section.
Example(s):
<var><location StartPos="55" EndPos="57" width="3" RecSegNo="2" fileid="CARD-IMAGE" ></location>
<location StartPos="167" EndPos="169" fileid="LRECL"></location></var>
<nCube><location locMap="LM"/></nCube>
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: According to the Statistical Terminology glossary maintained by the National Science Foundation, this is "the process by which one estimates missing values for items that a survey respondent failed to provide," and if applicable in this context, it refers to the type of procedure used. When applied to an nCube, imputation takes into consideration all of the dimensions that are part of that nCube.
Example(s):
<var><imputation>This variable contains values that were derived by substitution.</imputation></var>
Description: Provides information regarding levels of access, e.g., public, subscriber, need to know. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<var><security date="1998-05-10"> This variable has been recoded for reasons of confidentiality.
Users should contact the archive for information on obtaining access.</security></var>
<var><security date="1998-05-10">Variable(s) within this nCube have been recoded for reasons of
confidentiality. Users should contact the archive for information on obtaining access.</security></var>
Description:
Provides information on variables/nCubes which are not currently available because of policies established by the principal investigators and/or data producers. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. An "event" attribute is provided to specify "notBefore" or "notAfter" ("notBefore" is the default). A "format" attribute is provided to ensure that this information will be machine-processable, and specifies a format for the embargo element.
The "format" attribute could be used to specify other conventions for the way that information within the embargo element is set out, if conventions for encoding embargo information were established in the future.
Example(s):
<var><embargo event="notBefore" date="2001-09-30"> The data associated with this variable/nCube
will not become available until September 30, 2001, because of embargo provisions established by the
data producers.</embargo></var>
Description: Provides information regarding who provided the information contained within the variable/nCube, e.g., respondent, proxy, interviewer.
Example(s):
<var><respUnit>Head of household</respUnit></var>
<nCube><respUnit>Head of household</respUnit></nCube>
Description: Provides information regarding whom or what the variable/nCube describes.
Example(s):
<var><anlysUnit> This variable reports election returns at the constituency level. </anlysUnit></var>
<nCube><anlysUnit>Household</anlysUnit></nCube>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The question element may have mixed content. The element itself may contain text for the question, with the subelements being used to provide further information about the question. Alternatively, the question element may be empty and only the subelements used. The element has a unique question ID attribute which can be used to link a variable with other variables where the same question has been asked. This would allow searching for all variables that share the same question ID, perhaps because the questions was asked several times in a panel design. The "ID" attribute contains a unique identifier for the question. "Var" references the ID(s) of the variable(s) relating to the question. The attribute "seqNo" refers to the sequence number of the question. The attribute "sdatrefs" may be used to reference elements in the summary data description section of the Study Description which might apply to this question. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Example(s):
<var><qstn ID="Q125">When you get together with your friends, would you say you discuss political
matters frequently, occasionally, or never?</qstn></var>
Description: Text describing a set of conditions under which a question might be asked.
Example(s):
<var><qstn><preQTxt>For those who did not go away on a holiday of four days or more in 1985...
</preQTxt></qstn></var>
Description: Text of the actual, literal question asked.
Example(s):
<var><qstn><qstnLit>Why didn't you go away in 1985?</qstnLit></qstn></var>
Description: Text describing what occurs after the literal question has been asked.
Example(s):
<var><qstn><postQTxt>The next set of questions will ask about your financial situation.</postQTxt>
</qstn></var>
Description: Contains a reference to IDs of possible following questions. The "qstn" IDREFS may be used to specify the question IDs.
Example(s):
<var><qstn><forward qstn="Q120 Q121 Q122 Q123 Q124"> If yes, please ask questions 120-124.
</forward></qstn></var>
Description: Contains a reference to IDs of possible preceding questions. The "qstn" IDREFS may be used to specify the question IDs.
Example(s):
<var><qstn><backward qstn="Q12 Q13 Q14 Q15">For responses on a similar topic, see questions
12-15.</backward></qstn> </var>
<var><qstn><backward qstn="Q143"> </backward></qstn> </var>
Description: Specific instructions to the individual conducting an interview.
Example(s):
<var><qstn><ivuInstr> Please prompt the respondent if they are reticent to answer this question.
</ivuInstr></qstn></var>
Description: Values for a particular variable that represent legitimate responses.
Example(s):
<valrng><range min="1" max="3" /></valrng>
<valrng><item VALUE="1" /><item VALUE="2" /><item VALUE="3" /></valrng>
Description: This element permits a listing of the category values and labels. While this information is coded separately in the Category element, there may be some value in having this information in proximity to the range of valid and invalid values. A table is permissible in this element.
Example(s):
<valrng> <range UNITS="INT" maxExclusive="95" min="05" max="80"> </range> <key> 05 (PSU) Parti Socialiste Unifie et extreme gauche (Lutte Ouvriere) [United Socialists and extreme left (Workers Struggle)] 50 Les Verts [Green Party] 80 (FN) Front National et extreme droite [National Front and extreme right] </key> </valrng>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Values for a particular variable that represent missing data, not applicable responses, etc.
Example(s):
<invalrng> <range UNITS="INT" min="98" max="99"> </range> <key> 98 DK 99 Inappropriate </key> </invalrng>
Description: This element permits a listing of the category values and labels. While this information is coded separately in the Category element, there may be some value in having this information in proximity to the range of valid and invalid values. A table is permissible in this element.
Example(s):
<valrng> <range UNITS="INT" maxExclusive="95" min="05" max="80"> </range> <key> 05 (PSU) Parti Socialiste Unifie et extreme gauche (Lutte Ouvriere) [United Socialists and extreme left (Workers Struggle)] 50 Les Verts [Green Party] 80 (FN) Front National et extreme droite [National Front and extreme right] </key> </valrng>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Values whose meaning is unknown.
Example(s):
<var><undocCod>Responses for categories 9 and 10 are unavailable.</undocCod></var>
Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.
Example(s):
<universe clusion="I">Individuals 15-19 years of age. </universe> <universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: The number of responses to this variable. This element might be used if the number of responses does not match added case counts. It may also be used to sum the frequencies for variable categories.
Example(s):
<var><TotlResp>1,056</TotlResp></var>
OR
<var><TotlResp>There are only 725 responses to this question since it was not asked in Tanzania.</TotlResp></var>
Description:
One or more statistical measures that describe the responses to a particular variable and may include one or more standard summaries, e.g., minimum and maximum values, median, mode, etc. The attribute "wgtd" indicates whether the statistics are weighted or not. The "weight" attribute is an IDREF(S) to the weight element(s) in the study description.
The attribute "type" denotes the type of statistics being shown: mean, median, mode, valid cases, invalid cases, minimum, maximum, or standard deviation.
Example(s):
<var><sumStat type="min">0</sumStat></var>
<var><sumStat type="max">9</sumStat></var>
<var><sumStat type="median">4</sumStat></var>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: Standard category codes used in the variable, like industry codes, employment codes, or social class codes. The attribute "date" is provided to indicate the version of the code in place at the time of the study. The attribute "URI" is provided to indicate a URN or URL that can be used to obtain an electronic list of the category codes.
Example(s):
<var><stdCatgry date="1981" source="producer">U. S. Census of Population and Housing, Classified
Index of Industries and Occupations </stdCatgry></var>
Description: A description of response categories that might be grouped together. The attribute "missing" indicates whether this category group contains missing data or not. The attribute "missType" is used to specify the type of missing data, e.g., inap., don't know, no answer, etc. The attribute catGrp is used to indicate all the subsidiary category groups which nest underneath the current category group. This allows for the encoding of a hierarchical structure of category groups. The "levelno" attribute allows the addition of a level number, and "levelnm" allows the addition of a level name to the category group. The completeness attribute ("compl") should be set to "false" if the category group is incomplete (not a complete aggregate of all sub-nodes or children). The exclusiveness attribute ("excls") should be set to "false" if the category group can appear in more than one place in the classification hierarchy.
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: May include frequencies, percentages, or crosstabulation results. This field can contain one of the following: 1. textual information (e.g., PCDATA), or 2. non-parseable character data (e.g., the statistics), or 3. some other form of external information (table, image, etc.) In case 1, the tag can be used to mark up character data; tables can also be included in the actual markup. In cases 2 or 3, the element can be left empty and the "URI" attribute used to refer to the external object containing the information. The attribute "type" indicates the type of statistics presented - frequency, percent, or crosstabulation.
Example(s):
<var><catgryGrp ><catStat type='freq'>256 </catStat></catgryGrp></var>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description:
A description of a particular response.
The attribute "missing" indicates whether this category group contains missing data or not.
The attribute "missType" is used to specify the type of missing data, e.g., inap., don't know, no answer, etc.
The attribute "country" allows for the denotation of country-specific category values.
The "sdatrefs" attribute records the ID values of all elements within the summary data decription that apply to this category.
The exclusiveness attribute ("excls") should be set to "false" if the category can appear in more than one place in the classification hierarchy.
The attribute "catgry" is an IDREF referencing any child categories of this category element. Used to capture nested hierarchies of categories.
The attribute "level" is an IDREF referencing the catLevel ID in which this category exists.
Example(s):
<catlevel ID="Level1" levelnm="Broader sectors" />
<catlevel ID="Level2" levelnm="Narrower sectors" />
<catlevel ID="Level3" levelnm="Occupations" />
<!-- ... -->
<catgry ID="C1" catgry="C2" Level="Level1">
<catValu>0</catValu>
<labl> Management, professional and related occupations </labl>
</catgry>
<catgry ID="C2" catgry="C3, C4" Level="Level2">
<catValu>01</catValu>
<labl> Management occupations</labl>
</catgry>
<catgry ID="C3" Level="Level3">
<catValu>011</catValu>
<labl> Top executives </labl>
</catgry>
<catgry ID="C4" Level="Level3">
<catValu>012</catValu>
<labl> Financial managers</labl>
</catgry>
Description: The explicit response.
Example(s):
<var><catgry missing="Y" missType="inap"><catValu>9 </catValu> </catgry></var>
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: May include frequencies, percentages, or crosstabulation results. This field can contain one of the following: 1. textual information (e.g., PCDATA), or 2. non-parseable character data (e.g., the statistics), or 3. some other form of external information (table, image, etc.) In case 1, the tag can be used to mark up character data; tables can also be included in the actual markup. In cases 2 or 3, the element can be left empty and the "URI" attribute used to refer to the external object containing the information. The attribute "type" indicates the type of statistics presented - frequency, percent, or crosstabulation.
Example(s):
<var><catgryGrp ><catStat type='freq'>256 </catStat></catgryGrp></var>
Description: This element is a wrapper containing the presentation expression mi. It creates a single string without spaces consisting of the individual elements described within it. It can be used to create a single variable by concatenating other variables into a single string. It is used to create linking variables composed of multiple non-contiguous parts, or to define unique strings for various category values of a single variable.
Description: Token element containing the smallest unit in the mrow that carries meaning.
Description: Any special instructions to those who converted information from one form to another for a particular variable. This might include the reordering of numeric information into another form or the conversion of textual information into numeric information.
Example(s):
<var><codInstr>Use the standard classification tables to present responses to the question:
What is your occupation? into numeric codes.</codInstr></var>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Used only in the case of a derived variable, this element provides both a description of how the derivation was performed and the command used to generate the derived variable, as well as a specification of the other variables in the study used to generate the derivation. The "var" attribute provides the ID values of the other variables in the study used to generate this derived variable.
Description: A textual description of the way in which this variable was derived.
Example(s):
<var><derivation><drvdesc> VAR215.01 "Outcome of first pregnancy" (1988 NSFG=VAR611 PREGOUT1)
If R has never been pregnant (VAR203 PREGNUM EQ 0) then OUTCOM01 is blank/inapplicable. Else, OUTCOM01
is transferred from VAR225 OUTCOME for R's 1st pregnancy. </drvdesc></derivation></var>
Description: The actual command used to generate the derived variable. The "syntax" attribute is used to indicate the command language employed (e.g., SPSS, SAS, Fortran, etc.)
Example(s):
<var><derivation><drvcmd syntax="SPSS" >RECODE V1 TO V3 (0=1) (1=0) (2=-1) INTO DEFENSE WELFARE
HEALTH. </drvcmd></derivation></var>
Description: The technical format of the variable in question. Attributes for this element include: "type," which indicates if the variable is character or numeric; "formatname," which in some cases may provide the name of the particular, proprietary format actually used; "schema," which identifies the vendor or standards body that defined the format (acceptable choices are SAS, SPSS, IBM, ANSI, ISO, XML-data or other); "category," which describes what kind of data the format represents, and includes date, time, currency, or "other" conceptual possibilities; and "URI," which supplies a network identifier for the format definition.
Example(s):
<var><varFormat type="numeric" schema="SAS" formatname="DATE" category="date" >The number in this
variable is stored in the form 'ddmmmyy' in SAS format. </varFormat></var>
<var><varFormat type="numeric" formatname="date.iso8601" schema="XML-Data" category="date"
URI="http://www.w3.org/TR/1998/NOTE-XML-data/">19541022 </varFormat></var>
Description: This element is used to point, using a "URI" attribute, to an external map that displays the geography in question. The "levelno" attribute indicates the level of the geographic hierarchy relayed in the map. The "mapformat" attribute indicates the format of the map.
Description: Used to describe the levels of the category hierarchy. Note that we do not indicate nesting levels or roll-up structures here. This is done to be able to support ragged hierarchies.
Example(s):
<catlevel ID="Level1" levelnm="Broader sectors" /> <catlevel ID="Level2" levelnm="Narrower sectors" /> <catlevel ID="Level3" levelnm="Occupations" />
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
Describes the logical structure of an n-dimensional array, in which each coordinate intersects with every other dimension at a single point. The nCube has been designed for use in the markup of aggregate data. This element includes the following attributes:
The attribute "name" includes a short label for the nCube. Following the rules of many statistical analysis systems such as SAS and SPSS, names are usually up to eight characters long.
The "sdatrefs" are summary data description references which record the ID values of all elements within the summary data description section of the Study Description which might apply to the nCube. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the nCube. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).
The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements in Other Study Description Materials or Other Study-Related Materials that pertain to this nCube.
The "access" attribute records the ID values of all elements in the Data Access section that describe access conditions for this nCube. The "dmnsQnty" attribute notes the number of dimensions in the nCube. The "cellQnty" attribute indicates the total number of cells in the nCube.
Description: This is an empty element containing only the attributes listed below. Attributes include "StartPos" (starting position of variable), "EndPos" (ending position of variable), "width" (number of columns the variable occupies), "RecSegNo" (the record segment number, deck or card number the variable is located on), and "fileid", an IDREF link to the fileDscr element for the file that this location is within (this is necessary in cases where the same variable may be coded in two different files, e.g., a logical record length type file and a card image type file). Note that if there is no width or ending position, then the starting position should be the ordinal position in the file, and the file would be described as free-format. The attribute "locMap" is an IDREF to the element locMap and serves as a pointer to indicate that the location information for the nCube's cells (aggregate data) is located in that section.
Example(s):
<var><location StartPos="55" EndPos="57" width="3" RecSegNo="2" fileid="CARD-IMAGE" ></location>
<location StartPos="167" EndPos="169" fileid="LRECL"></location></var>
<nCube><location locMap="LM"/></nCube>
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.
Example(s):
<universe clusion="I">Individuals 15-19 years of age. </universe> <universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: According to the Statistical Terminology glossary maintained by the National Science Foundation, this is "the process by which one estimates missing values for items that a survey respondent failed to provide," and if applicable in this context, it refers to the type of procedure used. When applied to an nCube, imputation takes into consideration all of the dimensions that are part of that nCube.
Example(s):
<var><imputation>This variable contains values that were derived by substitution.</imputation></var>
Description: Provides information regarding levels of access, e.g., public, subscriber, need to know. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<var><security date="1998-05-10"> This variable has been recoded for reasons of confidentiality.
Users should contact the archive for information on obtaining access.</security></var>
<var><security date="1998-05-10">Variable(s) within this nCube have been recoded for reasons of
confidentiality. Users should contact the archive for information on obtaining access.</security></var>
Description:
Provides information on variables/nCubes which are not currently available because of policies established by the principal investigators and/or data producers. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. An "event" attribute is provided to specify "notBefore" or "notAfter" ("notBefore" is the default). A "format" attribute is provided to ensure that this information will be machine-processable, and specifies a format for the embargo element.
The "format" attribute could be used to specify other conventions for the way that information within the embargo element is set out, if conventions for encoding embargo information were established in the future.
Example(s):
<var><embargo event="notBefore" date="2001-09-30"> The data associated with this variable/nCube
will not become available until September 30, 2001, because of embargo provisions established by the
data producers.</embargo></var>
Description: Provides information regarding who provided the information contained within the variable/nCube, e.g., respondent, proxy, interviewer.
Example(s):
<var><respUnit>Head of household</respUnit></var>
<nCube><respUnit>Head of household</respUnit></nCube>
Description: Provides information regarding whom or what the variable/nCube describes.
Example(s):
<var><anlysUnit> This variable reports election returns at the constituency level. </anlysUnit></var>
<nCube><anlysUnit>Household</anlysUnit></nCube>
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.
Example(s):
<nCubeGrp><concept>Income</concept></nCubeGrp>
<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>
<var><concept>Income</concept></var>
<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Explains the purpose for which a particular nCube was created.
Example(s):
<nCube><purpose>Meets reporting requirements for the Federal Reserve Board</purpose></nCube>
Description: This element defines a variable as a dimension of the nCube, and should be repeated to describe each of the cube's dimensions. The attribute "rank" is used to define the coordinate order (rank="1", rank="2", etc.) The attribute "varRef" is an IDREF that points to the variable that makes up this dimension of the nCube.
Description: The element cohort is used when the nCube contains a limited number of categories from a particular variable, as opposed to the full range of categories. The attribute "catRef" is an IDREF to the actual category being used. The attribute "value" indicates the actual value attached to the category that is being used.
Example(s):
<dmns><cohort catRef="CV24_1" value="1"></cohort></dmns>
Description: This is the actual range of values. The "UNITS" attribute permits the specification of integer/real numbers. The "min" and "max" attributes specify the lowest and highest values that are part of the range. The "minExclusive" and "maxExclusive" attributes specify values that are immediately outside the range. This is an empty element consisting only of its attributes.
Example(s):
For example, x < 1 or 10 <= x < 20 would be expressed as <range maxExclusive="1"/><range min="10" maxExclusive="20" />.
Description: The element measure indicates the measurement features of the cell content: type of aggregation used, measurement unit, and measurement scale. An origin point is recorded for anchored scales, to be used in determining relative movement along the scale. Additivity indicates whether an aggregate is a stock (like the population at a given point in time) or a flow (like the number of births or deaths over a certain period of time). The non-additive flag is to be used for measures that for logical reasons cannot be aggregated to a higher level - for instance, data that only make sense at a certain level of aggregation, like a classification. Two nCubes may be identical except for their measure - for example, a count of persons by age and percent of persons by age. Measure is an empty element that includes the following attributes: "varRef" is an IDREF; "aggrMeth" indicates the type of aggregation method used, for example 'sum', 'average', 'count'; "measUnit" records the measurement unit, for example 'km', 'miles', etc.; "scale" records unit of scale, for example 'x1', 'x1000'; "origin" records the point of origin for anchored scales;"additivity" records type of additivity such as 'stock', 'flow', 'non-additive'.
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description:
This section allows for the inclusion of other materials that are related to the study as identified and labeled by the DTD/Schema users (encoders). The' materials may be entered as PCDATA (ASCII text) directly into the document (through use of the "txt" element). This ection may also serve as a "container" for other electronic materials such as setup files by providing a brief description of the study-related materials accompanied by the attributes "type" and "level" defining the material further. The "URI" attribute may be used to indicate the location of the other study-related materials.
Other Study-Related Materials may include: questionnaires, coding notes, SPSS/SAS/Stata setup files (and others), user manuals, continuity guides, sample computer software programs, glossaries of terms, interviewer/project instructions, maps, database schema, data dictionaries, show cards, coding information, interview schedules, missing values information, frequency files, variable maps, etc.
Note that Section 2.5, Other Study Description Materials, should be used for materials that are primarily descriptions of the content and use of the study, such as appendices, sampling information, weighting details, methodological and technical details, publications based upon the study content, related studies or collection of studies, etc. This section, 5.0 Other Study-Related Materials, is intended to include or to link to materials used in the production of the study or useful in the analysis of the study.
The "level" attribute is used to clarify the relationship of the other materials to components of the study. Suggested values for level include specifications of the item level to which the element applies: e.g., level=datafile; level=studydsc; level=study. The URI attribute need not be used in every case; it is intended for capturing references to other materials separate from the codebook itself. In Section 5, Other Material is recursively defined.
Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.
Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.
Example(s):
<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, and nuclear waste.</txt></varGrp> <nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> <var><txt>Total population for the agency for the year reported.</txt></var> <catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties with a right-wing orientation coded on the high end of the scale. Categories 90-99 were reserved miscellaneous responses.</txt></catgryGrp> <catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> <nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining program eligibility</txt></nCube> <otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire provided by the principal investigator.</txt></otherMat> <otherMat><txt>Glossary of Terms. Below are terms that may prove useful in working with the technical documentation for this study.. </txt></otherMat> <otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator. </txt></otherMat>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description:
This element encodes the bibliographic information for the work at the level specified: (1) Document Description, Citation (of Marked-up Document), (2) Document Description, Citation (of Marked-up Document Source), (3) Study Description, Citation (of Study), (4) Study Description, Other Material, and (5) Other Material for the study itself. Bibliographic information includes title information, statement of responsibility, production and distribution information, series and version information, text of a preferred bibliographic citation, and notes (if any).
A MARCURI attribute is provided to link to the MARC record for the citation.
Description: Title statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other materials; other materials for study.
Description: Full authoritative title for the work at the appropriate level: marked-up document; marked-up document source; study; other material(s) related to study description; other material(s) related to study. The study title will in most cases be identical to the title for the marked-up document. A full title should indicate the geographic scope of the data collection as well as the time period covered. Title of data collection (2.1.1.1) maps to Dublin Core Title element. This element is required in the Study Description citation.
Example(s):
<titl>Domestic Violence Experience in Omaha, Nebraska, 1986-1987</titl> <titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl> <titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
Description: A secondary title used to amplify or state certain limitations on the main title. It may repeat information already in the main title.
Example(s):
<titl>Monitoring the Future: A Continuing Study of American Youth, 1995</titl>
<subTitl>A Continuing Study of American Youth, 1995</subTitl>
<titl>Census of Population, 1950 [United States]: Public Use Microdata Sample</titl>
<subTitl>Public Use Microdata Sample</subTitl>
Description: A title by which the work is commonly referred, or an abbreviation of the title.
Description: Title translated into another language.
Example(s):
<titl>Politbarometer West [Germany], Partial Accumulation, 1977-1995</titl> <parTitl>Politbarometer, 1977-1995: Partielle Kumulation</parTitl>
Description: Unique string or number (producer's or archive's number). An "agency" attribute is supplied. Identification Number of data collection maps to Dublin Core Identifier element.
Example(s):
<IDNo agency="ICPSR">6678</IDNo> <IDNo agency="ZA">2010</IDNo>
Description: Responsibility for the creation of the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description:
The person, corporate body, or agency responsible for the work's substantive and intellectual content. Repeat the element for each author, and use "affiliation" attribute if available. Invert first and last name and use commas. Author of data collection (2.1.2.1) maps to Dublin Core Creator element. Inclusion of this element in codebook is recommended.
The "author" in the Document Description should be the individual(s) or organization(s) directly responsible for the intellectual content of the DDI version, as distinct from the person(s) or organization(s) responsible for the intellectual content of the earlier paper or electronic edition from which the DDI edition may have been derived.
Example(s):
<AuthEnty>United States Department of Commerce. Bureau of the Census</AuthEnty>
<AuthEnty affiliation="European Commission">Rabier, Jacques-Rene</AuthEnty>
Description: Statements of responsibility not recorded in the title and statement of responsibility areas. Indicate here the persons or bodies connected with the work, or significant persons or bodies connected with previous editions and not already named in the description. For example, the name of the person who edited the marked-up documentation might be cited in 1.1.2.2, using the "role" and "affiliation" attributes. Other identifications/acknowledgements for data collection (2.1.2.2) maps to Dublin Core Contributor element.
Example(s):
<othId role="editor" affiliation="INRA">Jane Smith</othId>
Description: Production statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The producer is the person or organization with the financial or administrative responsibility for the physical processes whereby the document was brought into existence. Use the "role" attribute to distinguish different stages of involvement in the production process, such as original producer. Producer of data collection (2.1.3.1) maps to Dublin Core Publisher element. The "producer" in the Document Description should be the agency or person that prepared the marked-up document.
Example(s):
<producer abbr="ICPSR" affiliation="Institute for Social Research">Inter-university Consortium for Political and Social Research</producer> <producer abbr="MNPoll" affiliation="Minneapolis Star Tibune Newspaper" role="original producer"> Star Tribune Minnesota Poll</producer> <producer abbr="MRDC" affiliation="University of Minnesota" role="final production">Machine Readable Data Center</producer>
Description: Copyright statement for the work at the appropriate level. Copyright for data collection (2.1.3.2) maps to Dublin Core Rights. Inclusion of this element is recommended element.
Example(s):
<copyright>Copyright(c) ICPSR, 2000</copyright>
Description: Date when the marked-up document/marked-up document source/data collection/other material(s) were produced (not distributed or archived). The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute. Production date for data collection (2.1.3.3) maps to Dublin Core Date element.
Example(s):
<prodDate date="1999-01-25">January 25, 1999</prodDate>
Description: Address of the archive or organization that produced the work.
Example(s):
<prodPlac>Ann Arbor, MI: Inter-university Consortium for Political and Social Research</prodPlac>
Description: Software used to produce the work. A "version" attribute permits specification of the software version number. The "date" attribute is provided to enable specification of the date (if any) for the software release. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.
Example(s):
<docDscr><citation><prodStmt><software version="1.0">MRDC Codebook Authoring Tool</software> </prodStmt></citation></docDscr> <docDscr><citation><prodStmt><software version="8.0">Arbortext Adept Editor</software> </prodStmt></citation></docDscr> <docDscr><docSrc><prodStmt><software version="4.0">PageMaker</software></prodStmt></docSrc></docDscr> <stdyDscr><citation><prodStmt><software version="6.12">SAS</software></prodStmt></citation></stdyDscr> <fileTxt><software version="6.12">The SAS transport file was generated by the SAS CPORT procedure. </software></fileTxt>
Description: The source(s) of funds for production of the work. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish them.
Example(s):
<fundAg abbr="NSF" role="infrastructure">National Science Foundation</fundAg> <fundAg abbr="SUN" role="equipment">Sun Microsystems</fundAg>
Description: The grant/contract number of the project that sponsored the effort. If more than one, indicate the appropriate agency using the "agency" attribute. If different funding agencies sponsored different stages of the production process, use the "role" attribute to distinguish the grant numbers.
Example(s):
<grantNo agency="Bureau of Justice Statistics">J-LEAA-018-77</grantNo>
Description: Distribution statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study.
Description: The organization designated by the author or producer to generate copies of the particular work including any necessary editions or revisions. Names and addresses may be specified and other archives may be co-distributors. A URI attribute is included to provide an URN or URL to the ordering service or download facility on a Web site.
Example(s):
<distrbtr abbr="ICPSR" affiliation="Institute for Social Research" URI="http://www.icpsr.umich.edu">Ann Arbor, MI: Inter-university Consortium for Political and Social Research</distrbtr>
Description: Names and addresses of individuals responsible for the work. Individuals listed as contact persons will be used as resource persons regarding problems or questions raised by the user community. The URI attribute should be used to indicate a URN or URL for the homepage of the contact individual. The email attribute is used to indicate an email address for the contact individual.
Example(s):
<contact affiliation="University of Wisconsin" email="jsmith@...">Jane Smith</contact>
Description: The name of the person (or institution) who provided this work to the archive storing it.
Example(s):
<depositr abbr="BJS" affiliation="U.S. Department of Justice">Bureau of Justice Statistics </depositr>
Description: The date that the work was deposited with the archive that originally received it. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<depDate date="1999-01-25">January 25, 1999</depDate>
Description: Date that the work was made available for distribution/presentation. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<distDate date="1999-01-25">January 25, 1999</distDate>
Description: Series statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. The URI attribute is provided to point to a central Internet repository of series information.
Description: The name of the series to which the work belongs.
Example(s):
<serName abbr="CPS">Current Population Survey Series</serName>
Description: Contains a history of the series and a summary of those features that apply to the series as a whole.
Example(s):
<serInfo>The Current Population Survey (CPS) is a household sample survey conducted monthly by the Census Bureau to provide estimates of employment, unemployment, and other characteristics of the general labor force, estimates of the population as a whole, and estimates of various subgroups in the population. The entire non-institutionalized population of the United States is sampled to obtain the respondents for this survey series.</serInfo>
Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.
Example(s):
<verStmt><version type="version" date="1999-01-25">Second version</version>
Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.
Example(s):
<version type="edition" date="1999-01-25">Second ICPSR Edition</version> <var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> <nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube>
Description: The organization or person responsible for the version of the work.
Example(s):
<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> <verResp>Inter-university Consortium for Political and Social Research</verResp> <var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> <nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>
Description: Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.
Example(s):
<biblCit format="MRDF">Rabier, Jacques-Rene, and Ronald Inglehart. EURO-BAROMETER 11: YEAR OF THE CHILD IN EUROPE, APRIL 1979 [Codebook file]. Conducted by Institut Francais D'Opinion Publique (IFOP), Paris, et al. ICPSR ed. Ann Arbor, MI: Inter-university Consortium for Political and Social Resarch [producer and distributor], 1981. </biblCit>
Description: Information concerning either the physical or electronic holdings of the cited work. Attributes include: location--The physical location where a copy is held; callno--The call number for a work at the location specified; and URI--A URN or URL for accessing the electronic copy of the cited work.
Example(s):
<holdings location="ICPSR DDI Repository" callno="inap." URI="http://www.icpsr.umich.edu/DDIrepository/"> Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File</holdings> <holdings location="University of Michigan Graduate Library" callno="inap." URI="http://www.umich.edu/library/"> Codebook for Current Population Survey, 1999: Annual Demographic File </holdings>
Description:
For clarifying information/annotation regarding the parent element.
The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").
Example(s):
<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables has been added to this marked-up version of the documentation.</notes></verStmt></docDscr> <docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive based on information received from the markup authors.</notes></citation></docDscr> <docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from original hardcopy materials using Optical Character Recognition (OCR).</notes><verStmt> </docSrc> <docSrc><notes>A machine-readable version of the source codebook was supplied by the Zentralarchiv</notes></docSrc> <docDscr><notes>This Document Description, or header information, can be used within an electronic resource discovery environment.</notes></docDscr> <stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this version of the data collection.</notes></verStmt></stdyDscr> <stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the agency depositing the data.</notes></citation></stdyDscr> <stdyInfo><notes>Data on employment and income refer to the preceding year, although demographic data refer to the time of the survey.</notes></stdyInfo> <method><notes>Undocumented codes were found in this data collection. Missing data are represented by blanks.</notes></method> <method><notes>For this collection, which focuses on employment, unemployment, and gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> <setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the final report are not provided as part of this collection.</notes></setAvail> <dataAccs><notes>Users should note that this is a beta version of the data. The investigators therefore request that users who encounter any problems with the dataset contact them at the above address.</notes></dataAccs> <fileStrc><notes>The number of arrest records for an individual is dependent on the number of arrests an offender had.</notes></fileStrc> <fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available in this version of the file.</notes></verStmt></fileTxt> <fileDscr><notes>There is a restricted version of this file containing confidential information, access to which is controlled by the principal investigator.</notes> </fileDscr> <varGrp><notes>This variable group was created for the purpose of combining all derived variables.</notes></varGrp> <varGrp><notes source="archive" resp="John Data">This variable group and all other variable groups in this data file were organized according to a schema developed by the adhoc advisory committee. </notes></varGrp> <nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross- tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> <valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of this variable has been standardized following an approximate ordering of each country's political parties along a "left" to "right" continuum in the first digit of the codes. Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the "center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 50-59 cannot be readily located in the traditional meaning of "left" and "right". The second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 contain the response "other party" and various missing data responses. Users may modify these codings or part of these codings in order to suit their specific needs. </notes> </valrng> <invalrng><notes>Codes 90-99 contain the response "other party" and various missing data responses. </notes></invalrng> <var><verStmt><notes>The labels for categories 01 and 02 for this variable, were inadvertently switched in the first version of this variable and have now been corrected.</notes></verStmt></var> <var><notes>This variable was created by recoding location of residence to Census regions.</notes></var> <nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were inadvertently switched in the first version of the cube, and have now been corrected. </notes></verStmt></nCube> <nCube><notes>This nCube was created to meet the needs of local low income programs in determining eligibility for federal funds.</notes></nCube> <dataDscr><notes>The variables in this study are identical to earlier waves. </notes> </dataDscr> <otherMat><notes>Users should be aware that this questionnaire was modified during the CAI process.</notes></otherMat>