****************************************************************
******* PARTNERSHIP AND FERTILITY EVENT HISTORY DATA SET *******
****************************************************************
* Authors:

* Christine Schnor
* Affiliation: 	Max Planck Institute for Demographic Research, Konrad-Zuse-Str.1, D-18057 Rostock. 
* Contact: 	schnor@demogr.mpg.de

* Sonja Bastin
* Affiliation: 	Max Planck Institute for Demographic Research, Konrad-Zuse-Str.1, D-18057 Rostock. 
* Contact: 	bastin@demogr.mpg.de


GENERAL NOTES (please read carefully)

01. 	Please notice that the main file of the whole process is Eventhistory.do. 
	The provided additional .do-files (i.e.: biopart_PF.do: biopart_PF_IMP.do; biopart_DD.do; biopart_DD_IMP.do) must not be manipulated.

02. 	DATA:	The original data need to be stored in your working directory (same folder as your .do-files).
                Unfortunately, the handling of the raw data is a bit cumbersome. In principle, you need data from pairfam (Release 3.1) and DemoDiff (Release 2.0).
       		
	a)	PAIRFAM data (Release 3.1): You need the files anchor1.dta, anchor2.dta, anchor3.dta, biopart.dta and biochild.dta
	
	b)	DEMODIFF data (Release 2.0): You need the files anchor1_DD.dta, anchor2_DD.dta, biopart.dta and biochild.dta

	c)	RENAMING: You need to rename the biopart and biochild as follows 
				
			- biopart.dta  (DemoDiff version)	-> 	biopart_DD.dta
			- biochild.dta (DemoDiff version)	-> 	biochild_DD.dta
			- biopart.dta  (pairfam version)	-> 	biopart_R3.dta

	d)	Finally (as mentioned above), put the data in the directory containing the Eventhistory.do and all other files.


03. 	OPEN & SET YOUR WORKING DIRECTORY (!): In Eventhistory.do you need to insert the concrete path where you have stored the original data (line 44). 


04.	RUN Eventhistory.do
 
*****************************************************************************************************
* COPYRIGHT Issues
* The files Eventhistory.do and Eventhistory.dta may be used by other users by citing the pairfam 
* Technical Report "Partners and Babies" (Schnor/Bastin 2013). 
* However, we accept no responsibility for errors that may have arisen during the coding procedures.


