This is a w3c Schema "Technical Implementation" of the DDI Conceptual
Specification. This schema is intended for use in producing electronic versions of
codebooks for quantitative social science data. Please note that the attribute xml-lang in
the a.globals group is an error that was persisted to retain backward compatibility. DO NOT
USE THIS ATTRIBUTE. If this attribute has been used, transfer the content to xml:lang.
DO NOT USE THIS ATTRIBUTE. Its inclusion is an error that was
persisted to retain backward compatibility. If this attribute has been used, transfer
the content to xml:lang.
Captures version of the element
Indicates version date for the element. Use YYYY-MM-DD, YYYY-MM, or
YYYY formats.
Used to capture the DDI-Lifecycle type URN for the element. This may
be captured during translation from DDI-Lifecycle to DDI-Codebook structure or in
preparation for transferring to a DDI-Lifecycle structure.
Used to capture the DDI-Codebook type URN for the element. This is
used to assign a DDI-Codebook specific URN to the element, according the format
prescribed by the DDI-Codebook standard.
Base Element Type
This type forms the basis for all elements. Every
element may contain the attributes defined the GLOBALS attribute
group.
Abstract Text Type
This type forms the basis for all textual elements.
Textual elements may contain text or a mix of select elements. This type is
abstract and is refined by more specific types which will limit the allowable
elements and attributes. Any textual element will be a subset of this type and
can be processed as such.
Simple Text Type
This type forms the basis of most textual elements.
Elements using this type may have mixed content (text and child elements). The
child elements are from the PHRASE, FORM, and xhtml:BlkNoForm.mix (a specific
subset of XHTML) content groups. Note that if elements from the PHRASE and FORM
groups must not be used with elements from the xhtml:BlkNoForm.mix group; one
can use either elements from xhtml:BlkNoForm.mix or elements from the PHRASE
and FORM groups. This type is extended in some cases to include additional
attributes.
Conceptual Text Type
This type forms this basis for a textual element
which may also provide for a conceptual (see concept) description of the
element a longer description (see txt). If the concept and/or txt elements are
used, then the element should contain no other child elements or text. Note
that if elements from the PHRASE and FORM groups must not be used with elements
from the xhtml:BlkNoForm.mix group; one can use either elements from
xhtml:BlkNoForm.mix or elements from the PHRASE and FORM groups.
Phrase Type
This type restricts the simpleTextType to allow for
only child elements from the PHRASE content group. It still allows for mixed
content (text and child elements).
String Type
This type restricts the base abstractTextType to
only allow for text (i.e. no child elements).
Integer Type
This type restricts the base abstractTextType to
only allow for an integer as text content. No child elements are
allowed.
Date Simple Type
This simple type is a union of the various XML
Schema date formats. Using this type, a date can be expressed as a year (YYYY),
a year and month (YYYY-MM), a date (YYYY-MM-DD) or a complete date and time
(YYYY-MM-DDThh:mm:ss). All of these formats allow for an optional timezone
offset to be specified.
Date Type
This type restricts the base abstractTextType to
allow for only the union of types defined in dateSimpleType as text content. No
child elements are allowed.
External Link
This element permits encoders to provide links from
any arbitrary element containing ExtLink as a subelement to electronic
resources outside the codebook.
Link
This element permits encoders to provide links from
any arbitrary element containing Link as a subelement to other elements in the
codebook.
Form Type
This type defines the basis for all elements in the
FORM content group. This is derived from the abstractTextType. The content may
still be mixed (text and child elements), but the child elements are restricted
to be those from the PHRASE and FORM content groups, or the itm and label
elements. Further, the possible attributes are restricted. This type is
abstract, so specific form elements will further refine this type, but all
elements in the FORM content group will conform to this structure and may be
processed as such.
Division
Formatting element: marks a subdivision in a
text.
Emphasis
Formatting element: marks words or phrases that are
emphasized for rhetorical effect.
Head
Formatting element: marks off a heading to a
division, list, etc.
Highlight
Formatting element: marks a word or phrase as
graphically distinct from the surrounding text, while making no claim for the
reasons.
List
Formatting element: contains any sequence of items
(entries) organized as a list.
Item
Formatting element: marks entries (items) in a
list.
Label
Formatting element: contains the label associated
with an item in a list; in glossaries, marks the term being defined.
Label
A short description of the parent element.
Attribute "level" indicates the level to which the element applies (variable
group, nCube group, variable, etc.). The "vendor" attribute allows for
specification of different labels for use with different vendors' software.
Attribute "country" allows specification of a different label by country for
the same element to which it applies. Attribute "sdatrefs" allows pointing to
specific dates, universes, or other information encoded in the study
description. The attributes "country" and "sdatrefs" are intended to cover
instances of comparative data, by retaining consistency in some elements over
time and geography, but altering, as appropriate, information pertaining to
date, language, and/or location.
Person (A) Record
]]>
Study Procedure Information
]]>
Political Involvement and National Goals
]]>
Household Variable Section
]]>
Sex by Work Experience in 1999 by Income in 1999
]]>
Tenure by Age of Householder
]]>
Why No Holiday-No Money
]]>
Other Agricultural and Related Occupations
]]>
Better
]]>
About the same
]]>
Inap.
]]>
Age by Sex by Poverty Status
]]>
SAS Data Definition Statements for ICPSR 6837
]]>
Paragraph
Marks a paragraph.
Abstract
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.
The contentType attribute provides forward-compatibility with DDI 3 by
describing where the content fits in that structure, or if is mixed in terms of
what is contained.
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.
]]>
Location of Data Collection
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.
Actions to Minimize Losses
Summary of actions taken to minimize data loss.
Includes information on actions such as follow-up visits, supervisory checks,
historical matching, estimation, etc.
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.
]]>
Alternative Title
A title by which the work is commonly referred, or
an abbreviation of the title.
Data Appraisal
Information on data appraisal.
Unit of Analysis
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.
individuals
]]>
Analysis Unit
Provides information regarding whom or what the
variable/nCube describes. The element may be repeated only to support multiple
language expressions of the content.
This variable reports election returns at the constituency level.
]]>
Household
]]>
Authoring Entity/Primary Investigator
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
(codeBook/stdyDscr/citation/rspStmt/AuthEnty) 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.
United States Department of Commerce. Bureau of the Census
]]>
Rabier, Jacques-Rene
]]>
Availability Status
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.
This collection is superseded by CENSUS OF POPULATION, 1880 [UNITED STATES]: PUBLIC USE SAMPLE (ICPSR 6460).
]]>
Backflow
Contains a reference to IDs of possible preceding
questions. The "qstn" IDREFS may be used to specify the question
IDs.
For responses on a similar topic, see questions 12-15.
]]>
]]>
Bibliographic Citation
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.
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.
]]>
Geographic Bounding Polygon
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.
Nevada State
]]>
42.002207
-120.005729004
42.002207
-114.039663
35.9
-114.039663
36.080
-114.544
35.133
-114.542
35.00208499998
-114.63288
35.00208499998
-114.63323
38.999
-120.005729004
42.002207
-120.005729004
]]>
Norway
]]>
80.76416
33.637497
80.76416
10.2
62.48395
4.789583
57.987915
4.789583
57.987915
11.8
61.27794
13.2336
63.19012
13.2336
67.28615
17.24580
68.14297
21.38362
68.14297
25.50054
69.39685
27.38137
68.76991
28.84424
68.76991
31.31021
71.42
31.31021
71.42
33.637497
80.76416
33.637497
]]>
Number of cases / Record Quantity
Number of cases or observations.
1011
]]>
Category Level Statistic
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. If a value of "other" is
used for this attribute, the "otherType" attribute should take a value from a
controlled vocabulary. This option should only be used when applying a
controlled vocabulary to this attribute. Use the complex element
controlledVocabUsed to identify the controlled vocabulary to which the selected
term belongs.
256
]]>
Category Value
The explicit response.
9
]]>
Category Level
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. A category level
may be linked to one or more maps of the variable content. This id done by
referencing the IDs of the appropriate geoMap elements in the attribute
geoMap.
]]>
]]>
]]>
Category
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 description 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.
]]>
]]>
]]>
0
Management, professional and related occupations
]]>
01
Management occupations
]]>
011
Top executives
]]>
012
Financial managers
]]>
Category Group
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.
Citation Requirement
Text of requirement that a data collection should
be cited properly in articles or other publications that are based on analysis
of the data.
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.
]]>
Bibliographic Citation
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.
Cleaning Operations
Methods used to "clean" the data collection, e.g.,
consistency checking, wild code checking, etc. The "agency" attribute permits
specification of the agency doing the data cleaning.
Checks for undocumented codes were performed, and data were subsequently revised in consultation with the principal investigator.
]]>
Coder Instructions
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.
Use the standard classification tables to present responses to the question: What is your occupation? into numeric codes.
]]>
This 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 is intended to include or to link
to materials used in the production of the study or useful in the analysis
of the study.
Codebook
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 (See Link) and from internal
elements to external sources (See ExtLink).
The top-level element, codeBook, also includes a version attribute to
specify the version number of the DDI specification.
codeBookAgency - This attribute holds the agency name of the creator
or maintainer of the codeBook instance as a whole, and is designed to
support forward compatibility with DDI-Lifecycle. Recommend the agency name
as filed with the DDI Agency ID Registry with optional additional sub-agency
extensions.
Cohort
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.
]]>
Date of Collection
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.
10 November 1998
]]>
Mode of Data Collection
The method used to collect the data;
instrumentation characteristics. XHTML formatting may be used in the txt
element for forward-compatibility with DDI 3.
telephone interviews
]]>
face-to-face interviews
]]>
mail questionnaires
]]>
computer-aided telephone interviews (CATI)
]]>
Characteristics of Data Collection
Situation
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.
There were 1,194 respondents who answered questions in face-to-face interviews lasting approximately 75 minutes each.
]]>
Extent of Collection
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.
1 data file + machine-readable documentation (PDF) + SAS data definition statements
]]>
Column Specification
Completeness of Study Stored
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.
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.
]]>
Concept
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.
Income
]]>
more experience
]]>
Income
]]>
SF: 311-312 draft horses
]]>
Conditions
Indicates any additional information that will
assist the user in understanding the access and use conditions of the data
collection.
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.
]]>
Confidentiality Declaration
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.
To download this dataset, the user must sign a declaration of confidentiality.
]]>
To obtain this dataset, the user must complete a Restricted Data Use Agreement.
]]>
Contact Persons
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.
Jane Smith
]]>
Control Operations
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.
Ten percent of data entry forms were reentered to check for accuracy.
]]>
Controlled Vocabulary Used
Provides a code value, as well as a reference to
the code list from which the value is taken. Note that the CodeValue can be
restricted to reference an enumeration.
Code List ID
Identifies the code list that the value is taken
from.
TimeMethod
]]>
Code List Name
Identifies the code list that the value is taken
from with a human-readable name.
Time Method]]>
Code List Agency Name
Agency maintaining the code list.
DDI Alliance]]>
Code List Version ID
Version of the code list. (Default value is
1.0)
1.1]]>
Code List URN
Identifies the code list that the value is taken
from with a URN.
urn:ddi-cv:TimeMethod:1.1]]>
Code List Scheme URN
Identifies the code list scheme using a
URN.
http://www.ddialliance.org/Specification/DDI-CV/TimeMethod_1.1_Genericode1.0_DDI-CVProfile1.0.xml]]>
Usage
Defines where in the instance the controlled
vocabulary which is identified is utilized. A controlled vocabulary may occur
either in the content of an element or in an attribute on an element. The usage
can either point to a collection of elements using an XPath via the selector
element or point to a more specific collection of elements via their identifier
using the specificElements element. If the controlled vocabulary occurs in an
attribute within the element, the attribute element identifies the specific
attribute. When specific elements are specified, an authorized code value may
also be provided. If the current value of the element or attribute identified
is not in the controlled vocabulary or is not identical to a code value, the
authorized code value identifies a valid code value corresponding to the
meaning of the content in the element or attribute.
Selector
Identifies a collection of elements in which a
controlled vocabulary is used. This is a simplified XPath which must correspond
to the actual instance in which it occurs, which is to say that the fully
qualified element names here must correspond to those in the instance. This
XPath can only identify elements and does not allow for any predicates. The
XPath must either be rooted or deep.
/codeBook/stdyDscr/method/dataColl/timeMeth]]>
Specific Elements
Identifies a collection of specific elements via
their identifiers in the refs attribute, which allows for a tokenized list of
identifier values which must correspond to identifiers which exist in the
instance. The authorizedCodeValue attribute can be used to provide a valid code
value corresponding to the meaning of the content in the element or attribute
when the identified element or attribute does not use an actual valid value
from the controlled vocabulary.
]]>
Attribute
Identifies an attribute within the element(s)
identified by the selector or specificElements in which the controlled
vocabulary is used. The fully qualified name used here must correspond to that
in the instance, which is to say that if the attribute is namespace qualified,
the prefix used here must match that which is defined in the
instance.
type]]>
Copyright
Copyright statement for the work at the appropriate
level. Copyright for data collection
(codeBook/stdyDscr/citation/prodStmt/copyright) maps to Dublin Core Rights.
Inclusion of this element is recommended.
Copyright(c) ICPSR, 2000
]]>
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.
]]>
]]>
]]>
Data Access
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".
Other Forms of Data Appraisal
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. Attribute
type allows for optional typing of data appraisal processes and option for
controlled vocabulary.
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."
]]>
Extent of Processing Checks
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:
The archive produced a codebook for this collection.
]]>
Consistency checks were performed by Data Producer/ Principal Investigator.
]]>
Consistency checks performed by the archive.
]]>
The archive generated SAS and/or SPSS data definition statements for this collection.
]]>
Frequencies were provided by Data Producer/Principal Investigator.
]]>
Frequencies provided by the archive.
]]>
Missing data codes were standardized by Data Producer/ Principal Investigator.
]]>
Missing data codes were standardized by the archive.
]]>
The archive performed recodes and/or calculated derived variables.
]]>
Data were reformatted by the archive.
]]>
Checks for undocumented codes were performed by Data Producer/Principal Investigator.
]]>
Checks for undocumented codes were performed by the archive.
]]>
Data Collection Methdology
Information about the methodology employed in a
data collection.
Sample Frame
Sample frame describes the sampling frame used for
identifying the population from which the sample was taken. For example, a
telephone book may be a sample frame for a phone survey. In addition to the
name, label and text describing the sample frame, this structure lists who
maintains the sample frame, the period for which it is valid, a use statement,
the universe covered, the type of unit contained in the frame as well as the
number of units available, the reference period of the frame and procedures
used to update the frame. Use multiple use statements to provide different uses
under different conditions. Repeat elements within the use statement to support
multiple languages.
Sample Frame Name
Name of the sample frame.
City of St. Paul Directory]]>
Valid Period
Defines a time period for the validity of the
sampling frame. Enter dates in YYYY-MM-DD format.
2009-07-01
2011-06-30
]]>
Reference Period
Indicates the period of time in which the sampling
frame was actually used for the study in question. Use ISO 8601 date/time
formats to enter the relevant date(s).
2009-06-01
]]>
Frame Unit
Provides information about the sampling frame unit.
The attribute "isPrimary" is boolean, indicating whether the unit is primary or
not.
Primary listed owners of published phone numbers in the City of St. Paul
]]>
Unit Type
Describes the type of sampling frame unit. The
attribute "numberOfUnits" provides the number of units in the sampling
frame.
Primary listed owners of published phone numbers in the City of St. Paul
]]>
Target Sample Size
Provides both the target size of the sample (this
is the number in the original sample, not the number of respondents) as well as
the formula used for determining the sample size.
Sample Size
This element provides the targeted sample size in
integer format.
385
]]>
Sample Size Formula
This element includes the formula that was used to
determine the sample size.
n0=Z2pq/e2=(1.96)2(.5)(.5)/(.05)2=385 individuals
]]>
Instrument Development
Describe any development work on the data
collection instrument. Type attribute allows for the optional use of a defined
development type with or without use of a controlled vocabulary.
The questionnaire was pre-tested with split-panel tests, as well as an analysis of non-response rates for individual items, and response distributions.
]]>
Instrument Development
Description of how and with what frequency the
sample frame is updated.
Changes are collected as they occur through registration and loss of phone number from the specified geographic area. Data are compiled for the date June 1st of odd numbered years, and published on July 1st for the following two-year period.
]]>
Custodian
Custodian identifies the agency or individual who
is responsible for creating or maintaining the sample frame. Attribute
affiliation provides the affiliation of the custodian with an agency or
organization. Attribute abbr provides an abbreviation for the
custodian.
DEX Publications
]]>
Collector Training
Describes the training provided to data collectors
including internviewer training, process testing, compliance with standards
etc. This is repeatable for language and to capture different aspects of the
training process. The type attribute allows specification of the type of
training being described.
Describe research project, describe population and sample, suggest methods and language for approaching subjects, explain questions and key terms of survey instrument.
]]>
Data Collector
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. The role attribute specifies the role
of person in the data collection process.
Survey Research Center
]]>
Variable Description
Description of variables.
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.
Kind of Data
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. The type attribute
can be used for forward-compatibility with DDI 3, by providing a type for use
of controlled vocabulary, as this is descriptive in DDI 2 and CodeValue in DDI
3.
survey data
]]>
Missing Data
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.
Missing data are represented by blanks.
]]>
The codes "-1" and "-2" are used to represent missing data.
]]>
Data Sources
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.
"Voting Scores." CONGRESSIONAL QUARTERLY ALMANAC 33 (1977), 487-498.
]]>
United States Internal Revenue Service Quarterly Payroll File
]]>
Definition
Rationale for why the group was constituted in this
way.
The following eight variables were only asked in Ghana.
]]>
The following four nCubes form a single presentation table.
]]>
Date of Deposit
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.
January 25, 1999
]]>
Deposit Requirement
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.
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.
]]>
Depositor
The name of the person (or institution) who
provided this work to the archive storing it.
Bureau of Justice Statistics
]]>
Derivation
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.
Major Deviations from the Sample Design
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. XHTML
formatting may be used in this element for forward-compatibility with DDI 3.
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.
]]>
Data Fingerprint
Allows for assigning a hash value (digital
fingerprint) to the data or data file. Set the attribute flag to "data" when
the hash value provides a digital fingerprint to the data contained in the file
regardless of the storage format (ASCII, SAS, binary, etc.). One approach to
compute a data fingerprint is the Universal Numerical Fingerprint (UNF). Set
the attribute flag to "dataFile" if the digital fingerprint is only for the
data file in its current storage format. Provide the digital fingerprint in
digitalFingerprintValue and identify the algorithm specification used (add
version as a separate entry if it is not part of the specification
entry).
UNF:3:DaYlT6QSX9r0D50ye+tXpA==
UNF v5.0 Calculation Producture [http://thedata.org/book/unf-version-5-0]UNF V5
]]>
File Dimensions
Dimensions of the overall file.
Disclaimer
Information regarding responsibility for uses of
the data collection. This element may be repeated to support multiple language
expressions of the content.
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.
]]>
Date of Distribution
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. If using a text entry in the
element content, the element may be repeated to support multiple language
expressions.
January 25, 1999
]]>
Distributor Statement
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.
Distributor
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.
Ann Arbor, MI: Inter-university Consortium for Political and Social Research
]]>
Dimension
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.
Document 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.
Documentation Source
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.
Documentation Status
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. The
element may be repeated to support multiple language expressions of the
content.
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.
]]>
Derivation Command
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.). The element may be repeated to
support multiple language expressions of the content.
RECODE V1 TO V3 (0=1) (1=0) (2=-1) INTO DEFENSE WELFAREHEALTH.
]]>
Derivation Description
A textual description of the way in which this
variable was derived. The element may be repeated to support multiple language
expressions of the content.
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.
]]>
East Bounding Longitude
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
Embargo
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.
This element may be repeated to support multiple language expressions
of the content.
The data associated with this variable/nCube will not become available until September 30, 2001, because of embargo provisions established by the data producers.
]]>
Table Entry
Estimates of Sampling Error
Measure of how precisely one can estimate a
population value from a given sample.
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.
]]>
Contents of Files
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.
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.
]]>
Data Files 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.
]]>
]]>
File Name
Contains a short title that will be used to
distinguish a particular file/part from other files/parts in the data
collection. The element may be repeated to support multiple language
expressions of the content.
Second-Generation Children Data
]]>
Place of File Production
Indicates whether the file was produced at an
archive or produced elsewhere.
Washington, DC: United States Department of Commerce, Bureau of the Census
]]>
Number of Files
Total number of physical files associated with a
collection.
5 files
]]>
File Structure
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. If the "other" value is used for the type attribute, then the
otherType attribute should have a value specifying the other type.The otherType
attribute should only be used when applying a controlled vocabulary to this
attribute. Use the complex element controlledVocabUsed to identify the
controlled vocabulary to which the selected term belongs. The fileStrcRef
attribute allows for multiple data files with different coverage but the same
file structure to share a single fileStrc. The file structure is fully
described in the first fileTxt within the fileDscr and then the fileStrc in
subsequent fileTxt descriptions would reference the first fileStrcRef rather
than repeat the details.
File-by-File Description
Provides descriptive information about the data
file. A file name and a full bibliographic citation for the file may be
entered, as well as a data fingerprint, if available. Information about the
physical properties of the data file is also supported. Make sure to fill out
topcClass for the study as these can be used by the data file. Note coverage
constraints in fileCont.
File Citation
The complex element fileCitation provides for a
full bibliographic citation option for each data file described in fileDscr. To
support accurate citation of a data file the minimum element set includes:
titl, IDNo, authEnty, producer, and prodDate. If a DOI is available for the
data file enter this in the IDNo (this element is repeatable). If a hash value
(digital fingerprint) has been created for the data file enter the information
regarding its value and algorithm specification in
digitalFingerprint.
ABC News/Washington Post Monthly Poll, December 2010
http://dx.doi.org/10.3886/ICPSR32547.v1
ABC News
The Washington Post
ABC News
2011
]]>
Type of File
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. The element may be repeated to support multiple language
expressions of the content.
ASCII data file
]]>
Data Format
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. The element may be repeated to support
multiple language expressions of the content.
comma-delimited
]]>
Forward Progression
Contains a reference to IDs of possible following
questions. The "qstn" IDREFS may be used to specify the question
IDs.
If yes, please ask questions 120-124.
]]>
Frequency of Data Collection
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.
monthly
]]>
quarterly
]]>
Funding Agency/Sponsor
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.
National Science Foundation
]]>
Sun Microsystems
]]>
Geographic Bounding Box
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.
Nevada State
]]>
-120.005729004
-114.039663
35.00208499998
42.002207
]]>
Norway
]]>
4.789583
33.637497
57.987915
80.76416
]]>
Geographic Map
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.
Geographic Coverage
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. Fpor
forward-compatibility, DDI 3 XHTML tags may be used in this
element.
State of California
]]>
Geographic Unit
Lowest level of geographic aggregation covered by
the data.
state
]]>
Grant Number
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.
J-LEAA-018-77
]]>
G-Ring Latitude
Latitude (y coordinate) of a point. Valid range
expressed in decimal degrees is as follows: -90,0 to 90,0 degrees
(latitude)
G-Ring Longitude
Longitude (x coordinate) of a point. Valid range
expressed in decimal degrees is as follows: -180,0 to 180,0 degrees
(longitude)
Guide to Codebook
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. The element may be
repeated to support multiple language expressions of the content.
Holdings Information
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.
Marked-up Codebook for Current Population Survey, 1999: Annual Demographic File
]]>
Codebook for Current Population Survey, 1999: Annual Demographic File
]]>
Identification Number
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.
6678
]]>
2010
]]>
Imputation
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. This element may be repeated to support
multiple language expressions of the content.
This variable contains values that were derived by substitution.
]]>
Range of Invalid Data Values
Values for a particular variable that represent
missing data, not applicable responses, etc.
98 DK
99 Inappropriate
]]>
Value Item
The counterpart to Range; used to encode individual
values. This is an empty element consisting only of its attributes. The "UNITS"
attribute permits the specification of integer/real numbers. The "VALUE"
attribute specifies the actual value.