4 Pages

soep-description

Course: ICPSR 20070301, Fall 2009
School: Michigan
Rating:
 
 
 
 
 

Word Count: 1109

Document Preview

of Description the Socio-economic Panel (SOEP) Simplified Model Jan Goebel Date: 3. Dec. 2006 1 Overview The SOEP is a wide-ranging representative longitudinal study of private households. It provides information on all household members, consisting of Germans living in the Old and New German States, Foreigners, and recent Immigrants to Germany. The Panel was started in 1984. In 2005, there were nearly 12,000...

Register Now

Unformatted Document Excerpt

Coursehero >> Michigan >> Michigan >> ICPSR 20070301

Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

Course Hero has millions of student submitted documents similar to the one below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
of Description the Socio-economic Panel (SOEP) Simplified Model Jan Goebel Date: 3. Dec. 2006 1 Overview The SOEP is a wide-ranging representative longitudinal study of private households. It provides information on all household members, consisting of Germans living in the Old and New German States, Foreigners, and recent Immigrants to Germany. The Panel was started in 1984. In 2005, there were nearly 12,000 households, and more than 21,000 persons sampled. Some of the many topics include household composition, occupational biographies, employment, earnings, health and satisfaction indicators. The SOEP started in 1984 with two different Samples (called A and B), one for households where the household head holds a German citizenship, and one (oversampled) for households heads with a NonGerman citizenship. Over the years additional samples where added, as described in table 1. Tab 1: SOEP Sub-Samples Description Sample A B C D E F G H Year Sample of start Size (HH) 1984 1984 1990 1994/5 1998 2000 2002 2006 4528 1393 2179 522 1067 6052 1224 ~ 1000 Sample Region Description West-Germany West-German Sample West-Germany Over sampling of foreigners East-Germany East-German sample Germany Immigrants since 1984 Germany Supplementary Sample Germany Supplementary Innovation Sample Germany Oversampling of households with high income Germany Refreshment Sample 2 Data Structure 2.1 Principles The SOEP data is not one rectangular data file, like most other surveys. The normal SOEP distribution a user gets consist of 265 different data files. The data is collected annually, by personnel interviews with each household member aged 16 or older and one additional interview with the household head. Therefore the lion's share of the SOEP data files are either on personnel or on household level, and give information about one year of observation. In fact the bigger part of the SOEP can be treated as annually cross-sectional time series data for persons and households. However, to benefit from the full potential of the longitudinal features the SOEP Group also provides two special dataset which ensure the linkage between persons and households over time. This central datasets are called HPFAD (for households) and PPFAD (for persons), stemming from the German word Pfad for path. Additional to the datasets which reflect directly the underlying interviews, the SOEP Group provides each year some datasets, which contain generated data. This data encloses a core set of longitudinally checked variables (mostly variables which will be often used by researchers). To keep the model simple other datasets the SOEP encloses are not mentioned here, like never changing Biography information for all persons collected at different years or data on events in spell format. Figure 1 shows the principle structure of the SOEP, at least for some of the main datasets. For a better understanding please have at first a look at the next section about naming conventions. 2.2 Naming conventions The data is collected annually starting in 1984 and one year of collection is called wave. These waves are arranged alphabetically, i.e. the year 1984 is called wave A, year 1985 wave B and so on until 2005 which called wave V. Therefore the following conventions hold for most of the cross-sectional datasets: Tab 2: Dataset naming conventions Digit 1 2 Meaning Wave or Year Indicator (A for 1984, B for 1985 ...), e.g. the A in AP Unit of Analysis (H for households and P for Persons), e.g. the P in BH following Description of the dataset if not purely retrieved from the Person or Household questionnaire, GEN e.g. for generated variables in CHGEN The following Figure 1 shows the principle structure and the possible linkage options between the dataset focused here. In principle the dataset on personnel level can all be linked with the help of a never changing person ID, called (persnr, i.e. Person number). The household can be linked with the help of the household ID. However, households are not stable over time (household split for example because of move outs of children), therefore you need a wave- or year-specific ID to match households and persons. To ensure the possibility to track also households over time you need an additional ID, the so called original household number, called hhnr. Please note that this variable (hhnr) is NOT unique at the household level, except for the first wave in 1984. This special household number do NOT change over time. Newly created households can not get a household ID which was in use by any other household within the SOEP at any time. This makes it possible to create another household ID to match all persons with their corresponding household history (match PPFAD with HPFAD). This variable is called hhnrakt and consists of the last valid household ID given to this household. A household with is not realized within one year gets a value of -2 (not valid) on the current household ID. Time (Years) Wave T 2003 persnr Wave U 2004 Wave V 2005 PPFAD TP persnr TPGEN UP UPGEN VP VPGEN Personal Level persnr hhnrakt thhnr thhnr uhhnr uhhnr 2003 2004 2005 HPFAD thhnr TH THGEN UH UHGEN VH VHGEN thhnr Household Level uhhnr v hhnr Fig. 1: Principle Data Structure (simplified) 3 Description of Variables Apart from the normal description1 of variables a proper SOEP documentation need some additional features. The two main features needed are 1. 2. Track variable names of corresponding variables over time Link to construction variables from other datasets or/and levels or/and years The problem or complexity is that a model for this must be very flexible, because everything you can think of is possible within the SOEP. 3.1 Example 1: LFS05 Variable Label: Labour Force Status in Year 2005. Corresponding Variable Names in Years 2004 is LFS04, in Year 2003 LFS03, ... 1 Under a normal description i subsume things like variable names and labels, frequencies, as well as question text or sample targeted. Construction Variables: Dataset VPGEN: ERWTYP05 (constructed from Variables VP10 and VP24 from dataset VP) Dataset VP: VP05, VP06, VP07, VP08, VP10, VP7201, VP7202, VP7203 Dataset PPFAD: GEBJAHR 3.2 Example 2: AHINC05 Variable Label: Adjusted monthly household net income in Year 2005. Corresponding Variable Names in Years 2004 is AHINC04, in Year 2003 AHINC03, ... Construction Variables: Dataset UHBRUTTO: uhhgr Dataset VHBRUTTO: vhhgr Dataset UPBRUTTO: upzug, ustell Dataset VPBRUTTO: vpzug, vstell Dataset UPGEN: HINC04 (constructed from Variable UH4801 from dataset UH) Dataset VPGEN: HINC05 (constructed from Variable VH5101 from dataset VH) Dataset UP: up09, up5901, up5902, up6801, up6802, up6803, up6804, up6805, up6806, up6807, up6808, up6809, up6810, up6811, up6812, up6813, up6814, up6815, up6816, up6817, up6818, up6819, up6820, up6821, up6822, up6823 vp10, vp7101, vp7102, vp8001, vp8002, vp8003, vp8004, vp8005, vp8006 vp8007, vp8008, vp8009, vp8010, vp8011, vp8012, vp8013, vp8014, vp8015 vp8016, vp8017, vp8018, vp8019, vp8020, vp8021, vp8022, vp10303 vp10304 vp79 GEBJAHR, TODJAHR, UNETTO, VNETTO Dataset VP: Dataset PPFAD:
Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more. Course Hero has millions of course specific materials providing students with the best way to expand their education.

Below is a small sample set of documents:

Michigan - ICPSR - 20070921
NOTES ON CREATING A LIFE-CYCLE USE CASE IN DDI 3.0 ICPSR 5809 was actually a study conducted as research for a doctoral dissertation. I was able to get the dissertation (1967) as well as a book based on it published 1971 from the library, and was usi
Michigan - ICPSR - 20070921
NOTES ON CREATING A LIFE-CYCLE USE CASE IN DDI 3.0 ICPSR 5809 was actually a study conducted as research for a doctoral dissertation. I was able to get the dissertation (1967) as well as a book based on it published 1971 from the library, and was usi
Michigan - CC - 20061218
NameE-MailDateModule, section, elementPascal Heus pheus@opendatafoundation.org Pascal Heus pheus@opendatafoundation.org Pascal Heus pheus@opendatafoundation.org Pascal Heus pheus@opendatafoundation.org12/16/2006 logical porduct 12/16/2006 l
Michigan - ICPSR - 20041027
Michigan - ICPSR - 20041027
Michigan - DF - 20041218
Technical ReviewWorking Name of Proposal: Reinstating Nested Categories Working Group/Initiaor: ICPSR Architect: Sanda Ionescu (sandai@icpsr.umich.edu) Submission Date: 07 October 2004 Technical Review Date: 11 November 2004 Recommendation: Recomme
Michigan - DF - 20041218
Technical ReviewWorking Name of Proposal: Reinstating Nested Categories Working Group/Initiaor: ICPSR Architect: Sanda Ionescu (sandai@icpsr.umich.edu) Submission Date: 07 October 2004 Technical Review Date: 11 November 2004 Recommendation: Recomme
Michigan - ICPSR - 20070614
* DRAFT DO NOT QUOTE / DISSEMINATE *DDI or SDMX: Which Standard to Use?Author: Arofan Gregory (agregory@opendatafoundation.org) Contributors: Pascal Heus (pheus@opendatafoundation.org) Draft 0.2, May 2007 __ Table of Contents Overview.2 I. Introd
Michigan - ICPSR - 20061109
DDI Structural Reform Working Group 9 November 2006 Attending: Wendy Thomas, Minnesota Population Center J Gager, XML Expert Chris Nelson, invited expert Joachim Wackerow, ZUMA Ken Miller, ESRC Cavan Capps, US Census Bureau Missing: Titto Assini, inv
Michigan - ICPSR - 20050706
MetaDaterM e t a d a t a m a n a g e m e n t a n d p r o d u c t i o n s ys t e m f o r s u r v e ys i n e m p i r i c a l s oc i a l s c i e nce r e s e a r c hHandling the repeated Cross-national datasetsAuthor: Reto Hadorn, S I D O S Working
Michigan - ICPSR - 20050706
MetaDate rM e t a d a t a m a n a ge m e n t a n d p r o d u c t i o n system fo r su r v e ys i n emp i r i c a l soci a l science r esea r c hHandling the repeated Cross-national datasetsAuthor: Reto Hadorn, S I D O S Working paper. Status: Dr
Michigan - ICPSR - 20071206
35 UniversalsThe names of system variables begin with a dollar sign ($). You cannot modify a system variable or alter its print or write format. Except for these restrictions, you can use system variables anywhere that a normal variable is used in
Michigan - ICPSR - 20071206
35 UniversalsThe names of system variables begin with a dollar sign ($). You cannot modify a system variable or alter its print or write format. Except for these restrictions, you can use system variables anywhere that a normal variable is used in
Michigan - ICPSR - 20070712
Technical Implementation Committee 12 July 2007 Attending: J Gager, XML Expert Pascal Heus, Open Data Foundation I-Lin Kuo, ICPSR Joachim Wackerow, GESIS-ZUMA Missing: Arofan Gregory, XML Titto Assini, invited expert Angad Bhat, ESRC (invited guest)
Michigan - ICPSR - 20041008
1.) Creating a new account The initial step is to set up an account on Sourceforge which you can do via the following pages: http:/sourceforge.net/account/newuser_emailverify.php Follow the directions for registering a new account and then submit you
Michigan - ICPSR - 20041008
1.) Creating a new account The initial step is to set up an account on Sourceforge which you can do via the following pages: http:/sourceforge.net/account/newuser_emailverify.php Follow the directions for registering a new account and then submit you
Michigan - ICPSR - 20060908
DDI Structural QueriesHere are some issues that need to be discussed by the SRG. There will probably be more as the finalisation of the model and schemas progress.Logical Product and NCube Logical ProductAfter discussions about Categories and Cod
Michigan - A - 20060824
DDI Structural Reform Working Group 24 August 2006 Attending: Wendy Thomas, Minnesota Population Center Mark Diggory, MIT J Gager, XML Expert Chris Nelson, invited expert Missing: Titto Assini, invited expert Oliver Watteler, ZA Jostein Ryssevik, (No
Michigan - ICPSR - 20070403
Instructions for Completion: You can comment on any of the documents in the Technical Specification Parts I through IV-B. Parts I through IV-A have line numbers and these should be noted when making your comment. In order to provide a clear reference
Michigan - ICPSR - 20070403
Instructions for Completion: You can comment on any of the documents in the Technical Specification Parts I through IV-B. Parts I through IV-A have line numbers and these should be noted when making your comment. In order to provide a clear reference
Michigan - ICPSR - 20040129
Proposal for Minor (Non-invalidating) Revision to the DDI SpecificationInstructions To facilitate minor revisions to the DDI specification, the Steering Committee has developed the following alternative mechanism to the procedure for revision descr
Michigan - ICPSR - 20040129
Proposal for Minor (Non-invalidating) Revision to the DDI SpecificationInstructions To facilitate minor revisions to the DDI specification, the Steering Committee has developed the following alternative mechanism to the procedure for revision descr
Michigan - ICPSR - 20070426
Instructions for Completion: You can comment on any of the documents in the Technical Specification Parts I through IV-B. Parts I through IV-A have line numbers and these should be noted when making your comment. In order to provide a clear reference
Michigan - ICPSR - 20070426
Instructions for Completion: You can comment on any of the documents in the Technical Specification Parts I through IV-B. Parts I through IV-A have line numbers and these should be noted when making your comment. In order to provide a clear reference
Michigan - E - 234225
NameE-Mail Module, section, elementSanda Ionescu Sanda Ionescu Sanda IonescuUniverse - Update on previous requests. Logical Product, Variable, ConceptReference Logical Product, Variable, QuestionProblem DescriptionThis is an update on previo
Michigan - ICPSR - 20060929
DDI Structural QueriesVersion 1.4: 27/09/06 Answers to some queries added as a result of the SRG call 27 Sept. New queries added see new queries Sept 28.ScopeThis is a consolidated list of queries and actions taken. New queries can be found at t
Michigan - ICPSR - 20060929
DDI 3.0 Basic Structures and MechanismsDraft 0.3 June 25, 2006 J Gager, Arofan Gregory, Chris NelsonI. PurposeThe most significant change to the DDI in version 3.0 is the introduction of modules that reflect various aspects of a study over the c
Michigan - ICPSR - 20080508
DDI Structural Reform Working Group 1 May 2008 Attending: Wendy Thomas, Minnesota Population Center Arofan Gregory, XML expert Pascal Heus Joachim Wackerow, ZUMA Ken Miller, ESRC lost connection Chris Nelson, invited expert lost connection Missing:
Michigan - ICPSR - 20080508
DDI Structural Reform Working Group 8 May 2008 Attending: Wendy Thomas, Minnesota Population Center Arofan Gregory, XML expert Pascal Heus Joachim Wackerow, ZUMA Ken Miller, ESRC lost connection Chris Nelson, invited expert lost connection Missing:
Michigan - ICPSR - 20080508
DDI Structural Reform Working Group 24 April 2008 Attending: Wendy Thomas, Minnesota Population Center Arofan Gregory, XML expert Pascal Heus Joachim Wackerow, ZUMA Ken Miller, ESRC lost connection Chris Nelson, invited expert lost connection Missi
Michigan - ICPSR - 20060706
LANGUAGE DECISION TREE: Do the items in the group represent multiple languages? NO = There is no formal language relationship between the items in the group (L1) YES Is there a full language equivalence (i.e. those text parts included in both are eq
Michigan - ICPSR - 20060425
Review of DDI 3.0 - 2006-03-24Core data description itemsTyposlogicalproduct.xsd137: CategoryRefernce 502, 548: DataExisitencephysicaldataproduct.xsd270: DecimalSeperatorMissing itemsWhere is the reference (CategorySchemeReference) in logi
Michigan - ICPSR - 20060425
Review of DDI 3.0 - 2006-03-24Core data description itemsTyposlogicalproduct.xsd137: CategoryRefernce 502, 548: DataExisitencephysicaldataproduct.xsd270: DecimalSeperatorMissing itemsWhere is the reference (CategorySchemeReference) in logi
Michigan - D - 20061213
NameSRGE-MailModule, section, elementComparative, ComparisonSRGComparative, ItemMapTypeSanda IonescuGroup, Group Type CodesSanda IonescuComparative, ConceptMap, ConceptMapProblem DescriptionSuggested Solution[QUERY: Should the
Michigan - ICPSR - 20070726
DDI 3.0 USE CASE DESCRIPTION FORMPLEASE RETURN THIS FORM BY JUNE 20th 2007 TO pheus@opendatafoundation.org and wlt@umn.eduIdentificationYou name, agency, and contact informationAlgenta Technologies http:/www.algenta.com/ Jeremy Iverson jeremy
Michigan - C - 20061222
NameSRGE-MailModule, section, elementPhysDataProduct, ValueLocationType, FormatSchemeSRGPhysDataProduct, ValueLocationType, FormatSanda IonescuLogical Product. Category SchemeSanda IonescuCoverage,Sanda IonescuPhysical Instance,
Michigan - DD - 8431
DDI Structural Reform Working Group 7 February 2008 Attending: Wendy Thomas, Minnesota Population Center Joachim Wackerow, ZUMA Pascal Heus Missing: Titto Assini, invited expert Cavan Capps, US Census Bureau Mark Diggory, MIT Arofan Gregory, XML expe
Michigan - DD - 8431
DDI Structural Reform Working Group 7 February 2008 Attending: Wendy Thomas, Minnesota Population Center Joachim Wackerow, ZUMA Pascal Heus Missing: Titto Assini, invited expert Cavan Capps, US Census Bureau Mark Diggory, MIT Arofan Gregory, XML expe
Michigan - E - 20071213
Find all "<xs:import", "E:\DDI\XML_Schema\3.0\2007-10-17_CandidateDraft\DDI_3_0_CR2_2007-10-17_Documentation_XMLSchema\schema", "*.xsd", Exclude: "*.v0.xsd"File E:\DDI\XML_Schema\3.0\2007-10-17_CandidateDraft\DDI_3_0_CR2_2007-10-17_Documentation_XML
Michigan - E - 20071213
Find all "<xs:import", "E:\DDI\XML_Schema\3.0\2007-10-17_CandidateDraft\DDI_3_0_CR2_2007-10-17_Documentation_XMLSchema\schema", "*.xsd", Exclude: "*.v0.xsd"File E:\DDI\XML_Schema\3.0\2007-10-17_CandidateDraft\DDI_3_0_CR2_2007-10-17_Documentation_XML
Michigan - ICPSR - 20080124
Publication Steps for DDI 3.0 FInal Publication (full package) High level documentation update Model update Complete Change list (CR-1 to 3.0) Update examples and Use Cases Minor final revsions (done in real time after CR-3 publication) Complete Use
Michigan - ICPSR - 20080124
Publication Steps for DDI 3.0 FInal Publication (full package) High level documentation update Model update Complete Change list (CR-1 to 3.0) Update examples and Use Cases Minor final revsions (done in real time after CR-3 publication) Complete Use
Michigan - ICPSR - 20040514
Physical Data Concept Collection Process Logical Encoding Encoding ArchivingStudy/Survey DesignData CollectionData ProcessingData DisseminationDiscoveryData AnalysisData
Michigan - ICPSR - 20040514
Physical Data Concept Collection Process Logical Encoding Encoding ArchivingStudy/Survey DesignData CollectionData ProcessingData DisseminationDiscoveryData AnalysisData
Michigan - ICPSR - 20070322
COMPLEX FILES: Summary of Issues and Approach W. Thomas Linking between and within files occurs at multiple levels and needs to be represented in the metadata in both a human readable version and as a machine actionable set of instructions. The high
Michigan - ICPSR - 20060609
DDI Object TypesThis list comprises the classes in the conceptual model and reflects the current state of the model. It is a "best guess" at the moment of the status of each of the classes with regard to Identification, Versioning, and Maintenance.
Michigan - ICPSR - 20061116
NameE-MailJoachim Wackerowwackerow@zuma-mannheim.deModule, section, elementDataCollectionProblem DescriptionLink to visual representation of question necessarySuggested SolutionOtherMaterial below QuestionText would be a solution. I
Michigan - ICPSR - 20061116
NameE-MailJoachim Wackerowwackerow@zuma-mannheim.deModule, section, elementDataCollectionProblem DescriptionLink to visual representation of question necessarySuggested SolutionOtherMaterial below QuestionText would be a solution. I
Michigan - ICPSR - 20070519
DDI: Resource Package as Reusable Set of MetadataSchemes in resource packages can be used in multiple ways.Study Variable ,Occupation of Spouse" Variable ,Occupation of Father" Resource Package Concept ,Work" Variable ,ISCO-88 " Code Scheme ,ISCO-8
Michigan - ICPSR - 20070519
DDI and ISO/IEC 11179Data Element Value DomainPermissible ValueData Element ConceptConceptual DomainValue Meaning
Michigan - ICPSR - 20040506
GOALS for modular design To organize the modules so that they accurately record information about data and the data creations process AND contain the information on structures and relationships necessary for data discovery, extraction and manipul
Michigan - ICPSR - 20040506
GOALS for modular design To organize the modules so that they accurately record information about data and the data creations process AND contain the information on structures and relationships necessary for data discovery, extraction and manipul
Michigan - ICPSR - 20040205
Request for implementation of review process for all changes to DDI Specification: The Structural Reform Group would like to request that the Steering Committee seek to clearly implement the procedures involved with the submission, review, and finali
Michigan - ICPSR - 20040205
Request for implementation of review process for all changes to DDI Specification: The Structural Reform Group would like to request that the Steering Committee seek to clearly implement the procedures involved with the submission, review, and finali
Michigan - ICPSR - 20040426
DDI ManualInstructions for Developing and Expanding the DDI Conceptual SpecificationIssued 1 May 2004[Add logo here]21 Table of Contents1. Overview 2. The DDI Model 3.2.1. 2.2.Conceptual Specification Technical Implementations Definition
Michigan - ICPSR - 20040426
DDI ManualInstructions for Developing and Expanding the DDI Conceptual SpecificationIssued 1 May 2004[Add logo here]21 Table of Contents1. Overview 2. The DDI Model 3.2.1. 2.2.Conceptual Specification Technical Implementations Definition
Michigan - ICPSR - 20061206
NameSanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu SRG Sanda Ionescu SRG SRGE-Mailsandai@icpsr.umich.eduSanda IonescuSanda IonescuSanda Ionescu Sanda Ionescu SRG Sanda Ionescu Sanda Ionescu Sanda Ionescu
Michigan - ICPSR - 20061206
NameSanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu Sanda Ionescu SRG Sanda Ionescu SRG SRGE-Mailsandai@icpsr.umich.eduSanda IonescuSanda IonescuSanda Ionescu Sanda Ionescu SRG Sanda Ionescu Sanda Ionescu Sanda Ionescu
Michigan - ICPSR - 20070524
DDI Structural Reform Working Group 24 May 2007 Attending: Wendy Thomas, Minnesota Population Center Arofan Gregory, XML J Gager, XML Expert Chris Nelson, invited expert Pascal Heus, World Bank Missing: Titto Assini, invited expert Mark Diggory, MIT
Michigan - ICPSR - 20050309
DDI SRGMemoTo:The group raising the nested category proposalDate:From: DDI-SRG group CC: Re:12/06/2009Nested categories proposalSummaryThe Structural Reform Group has evaluated the proposal to reintroduce nested categories in the DDI
Michigan - ICPSR - 20050309
DDI SRGMemoTo:The group raising the nested category proposalDate:From: DDI-SRG group CC: Re:12/06/2009Nested categories proposalSummaryThe Structural Reform Group has evaluated the proposal to reintroduce nested categories in the DDI