From j.b.gager at verizon.net Fri Jun 3 10:55:44 2005 From: j.b.gager at verizon.net (J Gager) Date: Fri Jun 3 10:56:02 2005 Subject: [DDI-ADG] Tuesday Agenda Message-ID: <000901c5684c$54ff2e20$6501a8c0@CPQ95163179221> Hi All - I will be trying to put together a breif agenda for our meetings. For this coming Tuesday, I would like to cover the following: * Review of Edinburgh meeting - mainly for every one that was not there. I will be sending out the goals and scope that we came up with shortly after this. * Begin reviewing the geography as it relates the the Universe. In the package that was sent from the SRG, there is an Excel workbook titled DDI-Version3-SRG_TagNames.xls. On the worksheet, REUSABLE CLASSES you will find a section SpatialCoverage - Row 49. I think this would be a good place to get the discussion started. * Form agenda for the next meeting. If anyone wants to add to the agenda, please let me know. Thanks, J Gager -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050603/f030c444/attachment.html From j.b.gager at verizon.net Fri Jun 3 10:56:09 2005 From: j.b.gager at verizon.net (J Gager) Date: Fri Jun 3 10:56:31 2005 Subject: [DDI-ADG] ADG Goals and Scope Message-ID: <000e01c5684c$63c07e50$6501a8c0@CPQ95163179221> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: ADGGoals.doc Type: application/msword Size: 32256 bytes Desc: not available Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050603/c511c3ef/ADGGoals-0001.doc From j.b.gager at verizon.net Fri Jun 3 10:56:46 2005 From: j.b.gager at verizon.net (J Gager) Date: Fri Jun 3 10:57:36 2005 Subject: [DDI-ADG] Aggregate Data Materials Message-ID: <001401c5684c$7cc1b540$6501a8c0@CPQ95163179221> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: How to markup aggregate data.doc Type: application/msword Size: 111616 bytes Desc: not available Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050603/bc4f060a/Howtomarkupaggregatedata-0001.doc -------------- next part -------------- A non-text attachment was scrubbed... Name: locMap-nCube-taglib.zip Type: application/x-zip-compressed Size: 31007 bytes Desc: not available Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050603/bc4f060a/locMap-nCube-taglib-0001.bin From j.b.gager at verizon.net Fri Jun 3 15:08:38 2005 From: j.b.gager at verizon.net (J Gager) Date: Fri Jun 3 15:09:19 2005 Subject: [DDI-ADG] Aggregate Data Materials In-Reply-To: Message-ID: <003901c5686f$abf11810$6501a8c0@CPQ95163179221> All- San is absolutely right. Another good place to start is the Key Family Tutorial - it can be found in Section VII - Appendix II of the Information Model document (DOC02 in the zip file). I am also attaching an SDMXBasics document that Arofan has been working on. I am not sure if it is final yet, but it could be useful. J -----Original Message----- From: Sandra.A.Cannon@frb.gov [mailto:Sandra.A.Cannon@frb.gov] Sent: Friday, June 03, 2005 11:12 AM To: J Gager Cc: DDI-ADG; ddi-adg-bounces@icpsr.umich.edu Subject: Re: [DDI-ADG] Aggregate Data Materials J, If I can make a suggestion... having waded through all the SDMX stuff, I have found that the most useful starting point is the Implementor's Guide (I think it's labeled Doc05 in that Zip file). If you aren't familiar with key families and the like, this is a good overview of the things to worry about without getting bogged down with the details on the different types of schema formats. Maybe all these concepts are familiar to everyone else but they were new to me. Just my 2 cents (or pence or florins or whatever other coins are left...) /san/ ------------------------------------------------- San Cannon Chief, Economic Information Management Federal Reserve Board Washington DC 20551 (202) 452-3710 scannon@frb.gov "J Gager" To Sent by: "DDI-ADG" ddi-adg-bounces@i cc cpsr.umich.edu Subject [DDI-ADG] Aggregate Data Materials 06/03/2005 10:56 AM All - As I promised in Edinburgh, I am sending out some materials on cubed data to help those unfamiliar with it. It may be a few weeks before we get to reviewing the cubed data section, so for now, you can probably review these at your leisure. DDI: Wendy Thomas wrote a straight forward document describing some use cases of marking up nCubes in DDI 2.0 (How to markup aggregate data.doc). It may also be helpful to look at an excerpt form the tag library about nCube and LocationMaps (locMap-nCube-taglib.zip). These should provide a good starting point for understanding where the model currently stands. If you want more in depth information, I will try to provide it. SDMX: Since we are talking about aligning with SDMX, it will be useful to review the 1.0 model. You can download the entire distribution at: http://www.sdmx.org/news/document.aspx?id=125&nid=49. There are varying level of details here, including specifcation documents and samples. Which you will find more useful is really up to you. Happy Reading, J[attachment "How to markup aggregate data.doc" deleted by Sandra A Cannon/BOARD/FRS] [attachment "locMap-nCube-taglib.zip" deleted by Sandra A Cannon/BOARD/FRS] _______________________________________________ DDI-ADG mailing list DDI-ADG@icpsr.umich.edu http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg -------------- next part -------------- A non-text attachment was scrubbed... Name: SDMXBasics_v2.doc Type: application/msword Size: 104960 bytes Desc: not available Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050603/93457364/SDMXBasics_v2-0001.doc From j.b.gager at verizon.net Mon Jun 6 11:19:51 2005 From: j.b.gager at verizon.net (J Gager) Date: Mon Jun 6 11:20:22 2005 Subject: [DDI-ADG] Phone Numbers Please Message-ID: <004e01c56aab$32f78000$6501a8c0@CPQ95163179221> All - If you haven't already, please send me the phone number where you would like to be called for tomorrow's meeting. Thanks, J -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050606/23efade0/attachment.html From Sandra.A.Cannon at frb.gov Fri Jun 3 11:12:06 2005 From: Sandra.A.Cannon at frb.gov (Sandra.A.Cannon@frb.gov) Date: Mon Jun 6 13:38:19 2005 Subject: [DDI-ADG] Aggregate Data Materials In-Reply-To: <001401c5684c$7cc1b540$6501a8c0@CPQ95163179221> Message-ID: J, If I can make a suggestion... having waded through all the SDMX stuff, I have found that the most useful starting point is the Implementor's Guide (I think it's labeled Doc05 in that Zip file). If you aren't familiar with key families and the like, this is a good overview of the things to worry about without getting bogged down with the details on the different types of schema formats. Maybe all these concepts are familiar to everyone else but they were new to me. Just my 2 cents (or pence or florins or whatever other coins are left...) /san/ ------------------------------------------------- San Cannon Chief, Economic Information Management Federal Reserve Board Washington DC 20551 (202) 452-3710 scannon@frb.gov "J Gager" To Sent by: "DDI-ADG" ddi-adg-bounces@i cc cpsr.umich.edu Subject [DDI-ADG] Aggregate Data Materials 06/03/2005 10:56 AM All - As I promised in Edinburgh, I am sending out some materials on cubed data to help those unfamiliar with it. It may be a few weeks before we get to reviewing the cubed data section, so for now, you can probably review these at your leisure. DDI: Wendy Thomas wrote a straight forward document describing some use cases of marking up nCubes in DDI 2.0 (How to markup aggregate data.doc). It may also be helpful to look at an excerpt form the tag library about nCube and LocationMaps (locMap-nCube-taglib.zip). These should provide a good starting point for understanding where the model currently stands. If you want more in depth information, I will try to provide it. SDMX: Since we are talking about aligning with SDMX, it will be useful to review the 1.0 model. You can download the entire distribution at: http://www.sdmx.org/news/document.aspx?id=125&nid=49. There are varying level of details here, including specifcation documents and samples. Which you will find more useful is really up to you. Happy Reading, J[attachment "How to markup aggregate data.doc" deleted by Sandra A Cannon/BOARD/FRS] [attachment "locMap-nCube-taglib.zip" deleted by Sandra A Cannon/BOARD/FRS] _______________________________________________ DDI-ADG mailing list DDI-ADG@icpsr.umich.edu http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg From atle.alvheim at nsd.uib.no Tue Jun 7 11:33:50 2005 From: atle.alvheim at nsd.uib.no (Atle Alvheim) Date: Tue Jun 7 11:48:15 2005 Subject: [DDI-ADG] Phone Numbers Please In-Reply-To: <004e01c56aab$32f78000$6501a8c0@CPQ95163179221> Message-ID: <5.0.0.25.2.20050607173038.02a94fe0@POP.uib.no> http://europa.eu.int/comm/eurostat/ramon/nuts/home_regions_en.html http://www.wordiq.com/definition/Nomenclature_of_Territorial_Units_for_Statistics Atle From j.b.gager at verizon.net Tue Jun 7 12:17:23 2005 From: j.b.gager at verizon.net (J Gager) Date: Tue Jun 7 12:19:25 2005 Subject: [DDI-ADG] NUTS In-Reply-To: <5.0.0.25.2.20050607173038.02a94fe0@POP.uib.no> Message-ID: <008d01c56b7c$63d2c000$6501a8c0@CPQ95163179221> Just resending Atle's email with a new subject, so it doesn't get lost. -----Original Message----- From: ddi-adg-bounces@icpsr.umich.edu [mailto:ddi-adg-bounces@icpsr.umich.edu] On Behalf Of Atle Alvheim Sent: Tuesday, June 07, 2005 11:34 AM To: DDI-ADG@icpsr.umich.edu Subject: Re: [DDI-ADG] Phone Numbers Please http://europa.eu.int/comm/eurostat/ramon/nuts/home_regions_en.html http://www.wordiq.com/definition/Nomenclature_of_Territorial_Units_for_S tatistics Atle _______________________________________________ DDI-ADG mailing list DDI-ADG@icpsr.umich.edu http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg From maryv at icpsr.umich.edu Tue Jun 7 13:40:57 2005 From: maryv at icpsr.umich.edu (Mary Vardigan) Date: Tue Jun 7 13:41:04 2005 Subject: [DDI-ADG] Comments Message-ID: <6.0.1.1.2.20050607131653.0290d258@icpsr.umich.edu> Hello, everyone. Thanks for participating in the phone call -- it was a good start. I wanted to make the comment that it might be useful to have ALL of the elements and attributes pertaining to geography anywhere in the Version 3.0 "candidates" pulled together and grouped according to what module or class they are in. That is, we have been looking at the Universe reusable class, but I see, for example, that geoMap, which used to be a variable-level element, appears now as a "type" under Other Materials. Plus, there is "geographic" (Y/N) and "geographicVocabulary" under Variable in the Logical Products section. Also, it looks as if there is a new "label" element under Variable Group, Variable, Category Group, and Category that has attributes of country, language, time, and date. I don't want to get hung up by considering too much at one time, but having such a list would help me in decision-making and figuring out relationships among elements and attributes. Wendy, would you be willing to pull together a list like this? You know the candidates the best. Also, do we want to create a Web site that we could use to post this and other documents, such as the use cases? Again, thanks to all. Mary Mary Vardigan Director, Collection Delivery Inter-university Consortium for Political and Social Research (ICPSR) University of Michigan P.O. Box 1248, Ann Arbor, MI 48106-1248 Phone: 734-615-7908 Fax: 734-647-8200 www.icpsr.umich.edu From wlt at pop.umn.edu Tue Jun 7 13:47:22 2005 From: wlt at pop.umn.edu (Wendy Thomas) Date: Tue Jun 7 13:47:31 2005 Subject: [DDI-ADG] Comments In-Reply-To: <6.0.1.1.2.20050607131653.0290d258@icpsr.umich.edu> Message-ID: Yes I can try to get this done. Wendy On Tue, 7 Jun 2005, Mary Vardigan wrote: > Hello, everyone. Thanks for participating in the phone call -- it was a > good start. > > I wanted to make the comment that it might be useful to have ALL of the > elements and attributes pertaining to geography anywhere in the Version 3.0 > "candidates" pulled together and grouped according to what module or class > they are in. That is, we have been looking at the Universe reusable class, > but I see, for example, that geoMap, which used to be a variable-level > element, appears now as a "type" under Other Materials. Plus, there is > "geographic" (Y/N) and "geographicVocabulary" under Variable in the Logical > Products section. Also, it looks as if there is a new "label" element under > Variable Group, Variable, Category Group, and Category that has attributes > of country, language, time, and date. > > I don't want to get hung up by considering too much at one time, but having > such a list would help me in decision-making and figuring out relationships > among elements and attributes. Wendy, would you be willing to pull together > a list like this? You know the candidates the best. > > Also, do we want to create a Web site that we could use to post this and > other documents, such as the use cases? > > Again, thanks to all. > > Mary > > Mary Vardigan > Director, Collection Delivery > Inter-university Consortium for Political and Social Research (ICPSR) > University of Michigan > P.O. Box 1248, Ann Arbor, MI 48106-1248 > Phone: 734-615-7908 > Fax: 734-647-8200 > www.icpsr.umich.edu > > _______________________________________________ > DDI-ADG mailing list > DDI-ADG@icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt@pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From wlt at pop.umn.edu Wed Jun 8 10:00:44 2005 From: wlt at pop.umn.edu (Wendy Thomas) Date: Wed Jun 8 10:00:52 2005 Subject: [DDI-ADG] Geographic/spatial elements Message-ID: Geographic/Spatial elements/attributes are found at the following locations: Resuable Class: Universe SpatialCoverage LogicalProduct (both basic and nCube) Variable geographic [a logical Y|N switch to identify a geographic variable] geogrpahicVocabulary [identifies coding scheme used ex. NUTS2, FIPS] label [found in Variable, VariableGroup, nCube, nCubeGroup, DimensionVariable] country [allows for the association of a country code for labels that differ by country - example: wording difference between UK and Germany] Note that the use of "country" in label limits geographic differntiation between labels based on country rather than a more generalized geographic unit. For example: I cannot use this to indicate that in Minnesota the Party name for the Democratic Party is Democratic-Farmer-Labor Party whereas in the rest of the US its Democratic Party. The use of the geographic (Y|N) and geographicVocabulary [controlled vocabulary identifier] is for the specific purpose of informing a program that this field can be used for geographic identification and the coding structure being used. Many files contain the same information in multiple coding schemes. The intent was to flag these....there are multiple ways to do this if you want a more centralized reference. Location of these items within the DDI-Version3-SRG_TagNames spreadsheets: SpacialCoverage: sheet: REUSABLE CLASSES lines: 49-69 geographic and geographicVocabulary: sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable in "- nCube") lines: 48-49 county (within label): sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable variableGroup and dimensionVariable in - nCube) lines: 20, 52, 84, 95 sheet: PKG LOGICAL PRODUCT - nCube (in addition to repeated classes) lines: 127, 192 Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt@pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From maryv at icpsr.umich.edu Thu Jun 9 08:52:05 2005 From: maryv at icpsr.umich.edu (Mary Vardigan) Date: Thu Jun 9 08:52:12 2005 Subject: [DDI-ADG] Geographic/spatial elements In-Reply-To: References: Message-ID: <6.0.1.1.2.20050609082625.02b741d8@icpsr.umich.edu> Thanks, Wendy. I am wondering how the reusable class Universe (subject, geography, and time) relates to the attributes on the label (the ones I found in various label elements are country, language, time, date, year). That is, would there ever be a situation in which one would override the other? It looks as if the reusable classes apply at the module and/or element level. In that case, would we maybe want to design a reusable class (Universe or something else) to hold general attributes that encompass the attributes on the various labels? Should label itself be part of a reusable class? Maybe we should review at all the generic (i.e., reusable) elements, like label, from Version 2.0? Again, I hope this doesn't get us too far afield from our subject matter, but want to advance the discussion. Also, in Version 2.0, I think language was available on every element as part of the XML syntax. Mary At 10:00 AM 6/8/2005, Wendy Thomas wrote: >Geographic/Spatial elements/attributes are found at the following >locations: > >Resuable Class: > Universe > SpatialCoverage > >LogicalProduct (both basic and nCube) > Variable > geographic [a logical Y|N switch to identify a geographic variable] > geogrpahicVocabulary [identifies coding scheme used ex. NUTS2, FIPS] > > label [found in Variable, VariableGroup, nCube, nCubeGroup, >DimensionVariable] > country [allows for the association of a country code for labels that >differ by country - example: wording difference between UK and Germany] > > >Note that the use of "country" in label limits geographic differntiation >between labels based on country rather than a more generalized geographic >unit. For example: I cannot use this to indicate that in Minnesota the >Party name for the Democratic Party is Democratic-Farmer-Labor Party >whereas in the rest of the US its Democratic Party. > >The use of the geographic (Y|N) and geographicVocabulary [controlled >vocabulary identifier] is for the specific purpose of informing a program >that this field can be used for geographic identification and the coding >structure being used. Many files contain the same information in multiple >coding schemes. The intent was to flag these....there are multiple ways to >do this if you want a more centralized reference. > >Location of these items within the DDI-Version3-SRG_TagNames spreadsheets: > >SpacialCoverage: > sheet: REUSABLE CLASSES > lines: 49-69 > >geographic and geographicVocabulary: > sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable in "- nCube") > lines: 48-49 > >county (within label): > sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable variableGroup >and dimensionVariable in - nCube) > lines: 20, 52, 84, 95 > sheet: PKG LOGICAL PRODUCT - nCube (in addition to repeated classes) > lines: 127, 192 > > >Wendy L. Thomas Phone: +1 612.624.4389 >Data Access Core Director Fax: +1 612.626.8375 >Minnesota Population Center Email: wlt@pop.umn.edu >University of Minnesota >50 Willey Hall >225 19th Avenue South >Minneapolis, MN 55455 > >_______________________________________________ >DDI-ADG mailing list >DDI-ADG@icpsr.umich.edu >http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg Mary Vardigan Director, Collection Delivery Inter-university Consortium for Political and Social Research (ICPSR) University of Michigan P.O. Box 1248, Ann Arbor, MI 48106-1248 Phone: 734-615-7908 Fax: 734-647-8200 www.icpsr.umich.edu From wlt at pop.umn.edu Thu Jun 9 09:54:46 2005 From: wlt at pop.umn.edu (Wendy Thomas) Date: Thu Jun 9 09:54:54 2005 Subject: [DDI-ADG] Geographic/spatial elements In-Reply-To: <6.0.1.1.2.20050609082625.02b741d8@icpsr.umich.edu> Message-ID: The material you are looking at in the spreadsheet was a first attempt to sort out the current DDI elements into the modules of the conceptual model. Some things were added to reflect conversatoins within the SRG, the Expert Group, and the former DDI group, or to provide a means of pointing/linking to reusable classes. Label is a class that would be defined once and reused. However, unlike the "reusable classes" it is a class that will get nested into other structures such as variable, category, variableGroup, ncube, ncube group etc. I think it is the name "reusable class" here that is confusing. The SRG is looking at the various classses (elements) and making sure that those that are used in a number of different situations are used consistantly. Needless to say, the more eyes on this particular piece the better, so if you find multiple occurances (particularly with different uses) let me know. Regarding "overrides": definitions at a higher level of the tree are overriden by lower level definitions. For example: If the Wrapper Module has a defined topical coverage of "Households, Families and Persons" and individual data file structure may only have "Persons". In the same way a particular label could be a subset of a large time, language, or country set. I want to clarify only thing about the "reusable class" as it related to the module. The content of the "reusable class" must be linked or related to elements within the module. For example: points to the then it applies to everything within . If pints to then it overrides in that particular instance. Am I correct in this J? So the real point in the current label structuring is...does it serve a purpose that is different from the purpose of the geographic and time cover in the reusable class? If not, perhaps it should be handled by the reusable class. For example, define each county once in the reusable classes and then point the labels to that information. Language is probably an issue you don't want to get into within this group, primarily because there have been long discussions about this already and it is so much broader than the identification of the language of the PCDATA expressed within the element. Language will be addressed in version 3.0 in a more extensive and integrated way. You won't lose any functionality you currently have (I did not put in the standard attributes for every element in the spreadsheet or it would have been 3-4 times as large) and if there are specific language needs that see should be addressed, relay that information to the SRG via J or I. You don't need to solve it...just point it out. As for finding multiple uses (reuses) of the same element or attribute, its already been done by running a program over the element names and noting multiple uses. Our primary concern in this was to identify element/attribute names that had multiple definitions or applications so that these could be renamed with single definitions. Sorry for the length of the note...hope it helps Wendy On Thu, 9 Jun 2005, Mary Vardigan wrote: > Thanks, Wendy. I am wondering how the reusable class Universe (subject, > geography, and time) relates to the attributes on the label (the ones I > found in various label elements are country, language, time, date, year). > That is, would there ever be a situation in which one would override the > other? > > It looks as if the reusable classes apply at the module and/or element > level. In that case, would we maybe want to design a reusable class > (Universe or something else) to hold general attributes that encompass the > attributes on the various labels? Should label itself be part of a reusable > class? Maybe we should review at all the generic (i.e., reusable) elements, > like label, from Version 2.0? Again, I hope this doesn't get us too far > afield from our subject matter, but want to advance the discussion. Also, > in Version 2.0, I think language was available on every element as part of > the XML syntax. > > Mary > > At 10:00 AM 6/8/2005, Wendy Thomas wrote: > >Geographic/Spatial elements/attributes are found at the following > >locations: > > > >Resuable Class: > > Universe > > SpatialCoverage > > > >LogicalProduct (both basic and nCube) > > Variable > > geographic [a logical Y|N switch to identify a geographic variable] > > geogrpahicVocabulary [identifies coding scheme used ex. NUTS2, FIPS] > > > > label [found in Variable, VariableGroup, nCube, nCubeGroup, > >DimensionVariable] > > country [allows for the association of a country code for labels that > >differ by country - example: wording difference between UK and Germany] > > > > > >Note that the use of "country" in label limits geographic differntiation > >between labels based on country rather than a more generalized geographic > >unit. For example: I cannot use this to indicate that in Minnesota the > >Party name for the Democratic Party is Democratic-Farmer-Labor Party > >whereas in the rest of the US its Democratic Party. > > > >The use of the geographic (Y|N) and geographicVocabulary [controlled > >vocabulary identifier] is for the specific purpose of informing a program > >that this field can be used for geographic identification and the coding > >structure being used. Many files contain the same information in multiple > >coding schemes. The intent was to flag these....there are multiple ways to > >do this if you want a more centralized reference. > > > >Location of these items within the DDI-Version3-SRG_TagNames spreadsheets: > > > >SpacialCoverage: > > sheet: REUSABLE CLASSES > > lines: 49-69 > > > >geographic and geographicVocabulary: > > sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable in "- nCube") > > lines: 48-49 > > > >county (within label): > > sheet: PKG LOGICAL PRODUCT - BASIC (repeated in variable variableGroup > >and dimensionVariable in - nCube) > > lines: 20, 52, 84, 95 > > sheet: PKG LOGICAL PRODUCT - nCube (in addition to repeated classes) > > lines: 127, 192 > > > > > >Wendy L. Thomas Phone: +1 612.624.4389 > >Data Access Core Director Fax: +1 612.626.8375 > >Minnesota Population Center Email: wlt@pop.umn.edu > >University of Minnesota > >50 Willey Hall > >225 19th Avenue South > >Minneapolis, MN 55455 > > > >_______________________________________________ > >DDI-ADG mailing list > >DDI-ADG@icpsr.umich.edu > >http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg > > Mary Vardigan > Director, Collection Delivery > Inter-university Consortium for Political and Social Research (ICPSR) > University of Michigan > P.O. Box 1248, Ann Arbor, MI 48106-1248 > Phone: 734-615-7908 > Fax: 734-647-8200 > www.icpsr.umich.edu > > _______________________________________________ > DDI-ADG mailing list > DDI-ADG@icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt@pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From wlt at pop.umn.edu Thu Jun 9 10:32:02 2005 From: wlt at pop.umn.edu (Wendy Thomas) Date: Thu Jun 9 10:32:47 2005 Subject: [DDI-ADG] a few more notes Message-ID: Sorry, about the odd usage of the english language in the previous email and for the need for this addendum....caffine is only slowly kicking in this morning... I just wanted to add that the geoMap (4.3.24) element in version 2.0 was reflected in the otherMaterials reusable class for the following reasons. The original tag contained no additional information (other than "level") to what was found in other definitions to outside materials. The ability to point to this from any element allows you to point to it from a specific variable category level, the variable itself, or from any other appropriate location. For example a map could be the composit of multiple variables or be simply geography or...well I don't know. Anyway it frees it up to be used where needed rather than just within the variable. I have also attached some of the original geographic element discussion that resulted in the elements currently found on lines 56-69 of REUSABLE CLASSES. Think of it as a history lesson :-) Wendy p.s. Note that these were proposals and may not have been fully incorporated. The proposals themselves were the result of meetings with the Alexandria Digital Library Gazetteer group at UCSB. Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt@pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 -------------- next part -------------- A non-text attachment was scrubbed... Name: agg-geog overview.doc Type: application/octet-stream Size: 102912 bytes Desc: Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050609/7c08f4e8/agg-geogoverview-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: BoxPolyProposal02-17-03.doc Type: application/octet-stream Size: 30720 bytes Desc: Url : http://www.icpsr.umich.edu/pipermail/ddi-adg/attachments/20050609/7c08f4e8/BoxPolyProposal02-17-03-0001.obj From mcneillh at MIT.EDU Thu Jun 9 17:23:17 2005 From: mcneillh at MIT.EDU (Katherine McNeill-Harman) Date: Thu Jun 9 17:23:37 2005 Subject: [DDI-ADG] initial use case ideas: user searching Message-ID: <5.2.1.1.2.20050609171843.03bd36e0@po11.mit.edu> Following is my initial brainstorming on use cases for geography. I'm starting from the perspective of ways in which users would want to search by geography, giving examples of types of data, rather than specific files (maybe we also want latter). So this is coming from the perspective of how we want systems to be designed to be useful to users (as well as to be able to accommodate various file types). Not sure if this is what the group had in mind, but hopefully it's a helpful start. This is based on my experience in helping users find and work with data files, and many are actual questions I've received; this is not based on experience actually implementing 2.0, so I'm sure others who have will have other helpful ideas. I've started to try to group them into categories, but even describing those categories proved to be a challenge. Ways in which users want to use geography to search for data: 1. Searching for variable information within a specific geographic coverage area at a specific level of geographic unit (yet still aggregated), e.g. - data on voter registration by precinct within the United States - unemployment rate by county within the United States - population and housing data for Eastern European cities (in this case the coverage and unit of analysis are more closely related than in the above examples) 2. Similar to "a" above, but for microdata, in which case the information is not aggregated to a certain level, but where the user wants a micro-level identifier at a certain geographic level, e.g. - want public opinion poll on a certain topic and to be able to differentiate among user responses by state (i.e. where state of residence was a question asked of the respondent) 3. Situations in which a time series has a quasi-geographic aspect, but geography isn't exactly a variable, e.g. - historical prices for municipal bonds within the United States (i.e. the geographic level of a municipality is a quality of the bond (i.e., as opposed to federal bonds), so might users think to search by geographic level?) 4. User looking to compare information about similar-level (yet differently-defined) geographic areas (either aggregate or microdata), e.g. - comparing literacy rates at the sub-national level among several countries (i.e. some countries call those areas "states," others "provinces;" how will they readily identify both?) (Relating to some of this week's discussion about labels on variables) 5. Issues of geographic correspondence (this may seem to be more of a data management issue, so I'm not sure exactly how it applies to the DDI, but there are some data files designed to provide correspondence) - users needing to match up two data files by a common geographic unit of analysis (e.g. a data file on education variables to be merged with one on economic variables, both with a common county code). - user needing to expand their geographic understanding of a data file, either for its own sake or to match two data files with different geographic units, e.g. one user requesting a particular data product that matches zip codes to telephone area codes (something one might not think of as a geographic ID, but they can function as such in the U.S.) Hope this is a helpful start. Kate ___________________________________________ Katherine McNeill-Harman Data Services Librarian Dewey Library for Management and Social Sciences Massachusetts Institute of Technology 77 Massachusetts Avenue, E53-100 Cambridge, MA 02139 mcneillh@mit.edu 617-253-0787 From wlt at pop.umn.edu Tue Jun 14 12:12:54 2005 From: wlt at pop.umn.edu (Wendy Thomas) Date: Tue Jun 14 12:13:04 2005 Subject: [DDI-ADG] Abusing frogs and alcohol Message-ID: abusing frogs.... http://hatethatfrog.desktopcreatures.com/index.asp?q=Crazy+Frog+Axel+F and alcohol http://www.wagenschenke.ch/ compliments of the SRG :-) From sandai at icpsr.umich.edu Fri Jun 24 15:34:29 2005 From: sandai at icpsr.umich.edu (Sanda Ionescu) Date: Fri Jun 24 15:34:55 2005 Subject: [DDI-ADG] Fwd: Use Case No.1 Message-ID: <6.0.1.1.2.20050624153127.01d5cdf0@icpsr.umich.edu> > > >Hi, all. > >Mary and I thought that looking at some concrete examples might give us a >better insight into the use of available geographic tags, and also reveal >any gaps that we might want to try to fill in the specification. > >Starting from Kate's first set of questions >(1. Searching for variable information within a specific geographic >coverage area at a specific level of geographic unit (yet still >aggregated), e.g. >- data on voter registration by precinct within the United States >- unemployment rate by county within the United States) > > >we picked up a codebook that documents just this type of data. It's ICPSR >study no. 9405 and I'm sending it as an attachment to this message. > >At variable level: >As you will see, there are 3 geographic variables in this dataset - state >code (V4) county name (V5) and county code (V6). >Although there is no region variable, analysis by region is also possible, >because the code for region is embedded in the state code (see V4). This >information is included in a free text note to the variable - should we >attempt to capture this kind of information in such a way that it would >become machine-readable? if yes, how do we go about it? >Same question for V6 - in the DDI, we would probably include just the >county code in the category values tags, because that's what we have in >the data. However, these codes can only be used in conjunction with the >codes in V4. Do we want to code this information in any way that will >assist "machine actionability'? > >At study level (more closely related to search and discovery, and Kate's >questions): >Trying to mark up the info with the tags provided in the V 3.0 spreadsheet - >1. from what I see here, geographicCover becomes a "container element" >with no PCDATA allowed (?) and the actual textual information is now >supposed to go in its child (?) , that replaces the from >V 2.0? >That's okay, I suppose. So , then, we would have: >United States. >Farther down, however, it gets more confusing (at least to me it does). >Looking at the way elements are structured, it appears that countryCode, >subCountryCode, geographicUnit, geographicKind and geoBndBox are all >children of geographicCover on a par with . If I'm reading the >spreadsheet correctly, this kind of structure is counterintuitive to the >new definition of geographicCover, which is "largest geographic extent". >The elements' structure only provides for a list of various levels of >coverage without indicating a hierarchy. If, for instance, we find geoKind >defined as line, or point, or polygon, how will we know whether this >refers to the geographicUnit (lowest level of coverage) or (largest >extent) or , or what? > > - will it be an element spelling out the name of the >country(ies) covered with an attribute containing the ISO code? this is >not clear in the spreadsheet. We probably need both name and code (If the > under geogCover were "Europe" we would need to list all countries >included both by name and code). >Going back to our example above, where our largest coverage is one >country, would we repeat the name of the country, and then add its ISO code? >United States > > - this seems to be intended for lower-than-country levels >of coverage. How do we actually use it? If we have more than one >subcountry level, do we just repeat the element for each level? - again, >this does not allow for establishing a hierarchy among the said levels >(maybe we should enable some kind of a nesting structure here? going down >from largest extent to smallest unit (geographicUnit)? >In the attached study, we have three subcountry levels - region, state, >and county. Do we mention each within its own element? >region >state >county >The presence of the word "code" in the name of the element suggest that we >would have actual codes here - but that seems unlikely? as the codes will >be listed in the variables' description or in an external document. So >from here we would probably only have a link to either the geographic >variable(s), or the said document. If this seems right, we should enable >such a link. And maybe rename this element as ? >Not sure if "authority" is meant to be an attribute - probably yes. In our >example, it would read "ICPSR". But if we're only listing levels here, it >should accompany the codes, wherever they are - or qualify the link to the >codes. > >It also seems appropriate to point from the levels listed here to the >variables that cover them - region and state to V4, county to V5 and V6. >This is not the same thing as linking to the codes; the codes may not be >embedded in the variable description, and there is not always a one-to-one >match between levels, codes, and geographic variables. > >Finally, in our example, would be "county". >I won't go into the actual mapping with this example. > >I will raise one last question that's not related to our example. Some >studies may cover regions that are above country level (like Eastern >Europe, for instance) but smaller than total coverage (or largest extent). >So far, we don't seem to have a way of accounting for this kind of coverage. > >One last word about the exercise above: it obviously raises more questions >than provides answers, and that's precisely why we hope it will be a good >starting point for our next discussion(s). > >Sanda and Mary > > > >Sanda Ionescu, >Research Associate >Inter-university Consortium for Political and Social Research (ICPSR) >The University of Michigan >P.O. Box 1248 >Ann Arbor, MI 48106 > >Phone: (734) 615-7890 >Fax: (734) 615-7890 > (734) 647-8200 -------------- next part -------------- 1 0 - - - VOTER REGISTRATION IN THE UNITED STATES, 1968-1988 (ICPSR 9405) 0 - - - Principal Investigator Inter-university Consortium for + Political and Social Research - - - First ICPSR Edition February 1991 - Inter-university Consortium for Political and Social Research P.O. Box 1248 Ann Arbor, Michigan 48106 1 1 - - BIBLIOGRAPHIC CITATION 0 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. The bibliographic citation for this data collection is: 0 Inter-university Consortium for Political and Social Research. VOTER REGISTRATION IN THE UNITED STATES, 1968-1988 [Computer file]. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [producer and distributor], 1991. - REQUEST FOR INFORMATION ON USE OF ICPSR RESOURCES 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 each completed manuscript or thesis abstract. Please indicate in a cover letter which data were used. - DATA 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. 1 1 - - TABLE OF CONTENTS 0 PAGE NO. - INTRODUCTION 0 Data Collection Description I 0 Data Collection Procedures VIII 0 File Structure IX 0 Codebook Information X 0 ICPSR Processing Information XII 0 VARIABLE DESCRIPTION LIST XIII 0 CODEBOOK 1 0 APPENDICES 0 A. ICPSR Registration Category Codes 0 B. ICPSR County Codes 1 1 I 0 INTRODUCTION 0 DATA COLLECTION DESCRIPTION 0 The Inter-university Consortium for Political and Social Research has constructed a file containing county-level voter registration information from 1968 through 1988. Analysts may wish to use this file in conjunction with such other ICPSR collections as CANDIDATE AND CONSTITUENCY STATISTICS OF ELECTIONS IN THE UNITED STATES (ICPSR Study 7757), CANDIDATE NAME AND CONSTITUENCY TOTALS (ICPSR Study 0002), REFERENDA AND PRIMARY ELECTION MATERIALS (ICPSR Study 0006), GENERAL ELECTION DATA FOR THE UNITED STATES (ICPSR Study 0013), and STATE LEGISLATIVE ELECTION RETURNS IN THE UNITED STATES (ICPSR Study 8907). This first edition of the collection contains all currently available data for 48 states (North Dakota does not require registration and Wisconsin does not report statewide voter registration figures). The number of total registered voters is presented for each county in these 48 states. If available, county-level figures are also presented for registration by political party or other similar category (e.g., declined to state, miscellaneous, other, etc.) provided by the reporting agency of the state. Registration totals by race, if available, are also included in the collection. Whenever a state provided registration figures for more than one time period during an election year, the data representing the period closest to the general election was selected for entry. The following provides a summary of voter registration data presented for each state in this collection: 0 Alabama: Data for 1968-1972 are missing. Registration data for 1974, 1976, and 1986 are dated in October, data for 1978 in August, data for 1980, 1982, and 1984 in November; in 1988 the totals for each county are dated separately, with dates ranging from 5/5/88 to 2/6/90. 1982 has a breakdown of registered voters by race; 1988 has a breakdown by race for about two-thirds of the counties. 0 Alaska: no voter registration existed before 1970. Months of compilation of data for 1970-1974 data are illegible on copies sent to ICPSR; for 1976-1988 the data are dated in November. 1 II 0 Arizona: registration data are dated in November for 1968-1978 and in September for 1980-1988. In 1980, the data are arranged by congressional district--Maricopa and Pinal counties are split between two districts and the registration figures for those two counties were aggregated. 0 Arkansas: registration data are dated in June for 1968-1976, in May for 1978-1982, 1986, and 1988, and in November for 1984. 0 California: all registration data are dated in November, with the exception of the 1982 data, which are dated in June. 0 Colorado: data for 1968-1976 and 1986-1988 are dated in November, while data for 1978-1984 are dated in October. 0 Connecticut: all the registration data are dated in November. For the years 1982-1988, figures are listed for towns and cities--aggregation was required to get county totals. 0 Delaware: registration data for 1968-1988 are dated in November. There is a breakdown by party for all years. For 1968-1970, there are separate figures given for Wilmington and rural New Castle county which had to be added to get New Castle county totals. 0 Florida: registration data for 1968, 1972, 1976-1988 are dated in October, data for 1970 in August, and for 1974 in September. There are breakdowns by party and race for each year. 0 Georgia: data for 1968-1982 are not dated; data for 1984-1988 are dated in November. There is a breakdown by race for 1982-1988. 0 Hawaii: 1968-1988 data are dated in November. 1 III 0 Idaho: 1968-1988 data are dated in November. 0 Illinois: 1968-1988 data are dated in November. For 1968-1984, separate figures were given for major cities--these had to be added to their respective county figures to get county totals. 0 Indiana: 1968-1988 are dated in November. In 1974, some counties used registration figures from the primary election. 0 Iowa: 1968-1974 data are currently unavailable. 1976 data are dated in August, data for 1978 in March, for 1980 in January, for 1982, 1984, and 1988 in December, and for 1986 in November. For 1986, figures given for Calhoun and Shelby counties are described as not final. There is a breakdown by party for 1976-1988. 0 Kansas: statewide voter registration was not required until 1972. 1972 data are dated in August, data for 1974 are not dated, data for 1976 and 1978 are dated in May, for 1980-1986 in October, and for 1988 in June. There is a breakdown by party for 1974-1988. 0 Kentucky: 1976 data are currently unavailable. 1968-1972 data are not dated. 1974 data are dated in December, data for 1978 and 1984-1988 are dated in November, for 1980 in October, and for 1982 in May. There is a breakdown by party for 1968, 1970, 1974, and 1978-1988. There is a breakdown by race for 1980-1988. 0 Louisiana: data for 1968 and 1972-1980 are dated in March, data for 1970 are dated in April, for 1982, 1986, and 1988 in October, and for 1984 in September. There are breakdowns by party and race for all years. In 1974, Acadia, St. Helena, and Washington parishes used registration figures from 12/31/73. In 1978, St. Helena parish used figures from 12/31/77. In 1984, Plaquemines and Tangipahoa parishes used figures from 8/29/84. In 1984, some voters in Evangeline and Orleans parishes did not indicate their race. 1 IV 0 Maine: 1968-1984 data are dated in November, data for 1986 and 1988 are dated in June. There is a party breakdown for 1986 and 1988. There was incomplete reporting of registration for the following counties and years: in 1970--Aroostock, Oxford, Penobscot and Washington, in 1972--Penobscot (Grand Falls Plantation did not report) and Washington (Perry did not report), and in 1974--Penobscot (Grand Falls Plantation). 0 Maryland: 1968-1984 and 1988 data are dated in October, data for 1986 in November. There is a breakdown by party for all years. 0 Massachusetts: 1968-1972 data are dated in November, data for 1974 in October, for 1976-1980, 1984, and 1988 in August, and for 1982 and 1986 in September. There is a breakdown by party for 1976-1988. For 1986, the registration figures are given for towns and cities, and aggregation was required to get county totals. 0 Michigan: 1968-1976 and 1980-1988 data are dated in October and data for 1978 are dated in November. 0 Minnesota did not require statewide voter registration prior to 1974. 1974-1988 data are dated in November. In 1974, data are missing for Crow Wing, Kittson, Lake of the Woods, Lyon, Pope, Traverse, and Sherburne counties. In 1976, data are missing for Pope county. For all years Minnesota gives two registration statistics for each election: "voters registered prior to 7 a.m. election day" and "voters registering during election day." These two categories were added to derive total registered voters. 0 Mississippi did not compile statewide registration statistics until 1980. 1980 data are not dated, 1982-1988 data are dated in October. 1 V 0 Missouri: no registration data are currently available for 1968-1972. 1974-1988 data are dated in November. 0 Montana: 1968-1988 data are dated in November. 0 Nebraska: 1968-1988 data are dated in November. There is a breakdown by party for each year. 0 Nevada: 1968-1986 data are dated in October; 1988 data are dated in January. There is a breakdown by party for 1968-1984 and 1988. 0 New Hampshire: 1968-1980 and 1984-1988 data are dated in November, data for 1982 in September. There is a party breakdown for 1982 and 1984. 0 New Jersey: 1968-1988 data are dated in November. 0 New Mexico: 1968-1982 data are dated in November, data for 1984 in December, and 1986 and 1988 in October. There is a party breakdown for each year. 0 New York: 1968-1980 data are dated "fall," 1982 and 1988 data are dated in April, 1984 data are dated in March, and 1986 data are not dated, but presumably the enrollment was done in March or April. There is a party breakdown for 1968-1988. 0 North Carolina: 1968 and 1970 data are dated in December, data for 1972-1988 in October. There is a party breakdown for each year, and a breakdown by race for 1970-1988. 1 VI 0 North Dakota does not require registration. 0 Ohio: 1968-1988 data are dated in November. Registration was not mandatory for all counties until Bill S125 was passed in 1977; For the years 1968-1976, only counties which had complete registration data were entered into this collection. For the years 1978-1988 all counties had complete registration. 0 Oklahoma: 1968, 1970, 1974-1984 data are dated in January, data for 1972 in June, and 1986-1988 in November. There is a party breakdown for each year. 0 Oregon: 1968-1988 data are dated in November. There is a party breakdown for each year. 0 Pennsylvania: 1968-1988 data are dated in November. There is a party breakdown for each year. 0 Rhode Island: 1968-1988 data are dated in November. Registration statistics are provided only at the level of the town or city which were aggregated to get county totals. 0 South Carolina: 1968-1974 and 1982-1988 data are dated in October. 1976-1980 are dated in November. There is a breakdown by race for each year. 0 South Dakota: 1968, 1970, and 1974-1984 data are dated in October. 1972, 1986, and 1988 are dated in November. There is a party breakdown for each year. In 1968, four counties (Beadle, Brookings, Hughes, and Minnehaha) do not supply a party breakdown. 0 Tennessee: 1968, 1972-1976, and 1984 data are dated in October, data for 1970, 1982, 1986, and 1988 in June, for 1978 in November, and for 1980 in December. 1 VII 0 Texas: 1968-1974 data are currently unavailable. 1976-1988 data are dated in November. 0 Utah: 1968-1988 data are dated in November. 0 Vermont: 1968-1988 data are dated in November. 0 Virginia: 1968-1972, 1980, and 1984 are currently unavailable. Data for 1974-1978, 1982, 1986 and 1988 are dated in October. In 1974, data are missing for Franklin City, Poquoson, Manassas, and Manassas Park. In 1986 and 1988, data are broken down by congressional district--some counties were split and, therefore, aggregation was necessary to produce county totals. 0 Washington: 1968-1988 data are dated in November. 0 West Virginia: 1968-1988 data are dated in November. There is a party breakdown for each year. 0 Wisconsin does not produce statewide voter registration statistics. 0 Wyoming: 1968 data are dated in August, data for 1970 and 1972 in March, for 1974-1988 in October. 1 VIII 0 DATA COLLECTION PROCEDURES 0 These data were obtained from state election officials who are, at present, the only source of county-level data currently available. As such users should be aware of the limitations of these data for subsequent analysis. As reported by such scholars as Frances Fox Piven and Richard A. Cloward in WHY AMERICANS DON'T VOTE (New York: Pantheon Books, 1988) and more recently in "Government Statistics and Conflicting Explanations of Nonvoting", PS: POLITICAL SCIENCE AND POLITICS, Vol. XXII, No. 3, September, 1989, pp. 580-588, state registration totals are often inflated because of people who have died or moved out of a particular county if state officials did not quickly purge such "deadwood" from the voting rolls. For alternate estimates users might wish to consult the other principal source of information on voting and registration in the United States: the postelection sample surveys reported in the series of voter supplement files to the CURRENT POPULATION SURVEYS of the Bureau of the Census. Currently ICPSR possesses such files for all even election years from 1972 through 1988 (ICPSR Study Numbers 0060, 7558, 7699, 7876, 7875, 8193, 8457, 8707, and 9318). 0 Most of the source materials used in the preparation of these data files have been collected over the last twenty years by the Consortium through direct appeal to election personnel in each of the fifty states. Prior to entry work on this project, a concerted effort was made to fill any gaps which existed in our holdings. A project Steering Committee was established to aid in this effort and to offer advice and counsel on designing data formats and documentation for this dataset. This Committee was chaired by Malcolm E. Jewell of the University of Kentucky who served as principal advisor to the project. The members of the Committee were William H. Flanigan of the University of Minnesota, Samuel C. Patterson of Ohio State University, and Ronald E. Weber of the University of Wisconsin at Milwaukee. All of these data were put into machine-readable form at the offices of the Inter-university Consortium for Political and Social Research in Ann Arbor. Principal funding for this project was provided by a grant from the National Science Foundation (Grant #SES-8618482). 1 IX - FILE STRUCTURE 0 Voter Registration in the United States, 1968-1988 is available from the ICPSR in a single data file and is constructed with one logical record for each county in all 48 states which collect and disseminate registration data in the United States. There are 325 variables and 3018 cases. 0 Information concerning the location and format for each variable in these data files is available in an SPSS control card file which accompanies this collection. This file may be used with the SPSS software package to access the data file. The data file may also be accessed directly through software packages or programs which do not use SPSS control card files by specifying the tape locations of the desired variables. These tape locations are given in the Codebook. A single codebook accompanies this data collection and contains complete documentation and variable descriptions. It also includes lists of codes of ICPSR registration categories and counties used in this collection. 1 X - CODEBOOK INFORMATION The example below is a reproduction of information appearing in the machine-readable codebook for a typical variable. The numbers in brackets do not appear but are references to the descriptions which follow this example. ............................................................ [1] VAR 0004 [2] ICPSR STATE CODE [3] NO MISSING DATA CODES REF 0004 [4] LOC 7 WIDTH 2 [5] IMP DEC = 0 [6] ICPSR state code [7] These are the standard ICPSR state codes used in all ICPSR data files. The first digit of this code serves as the region code. The year of entry into the Union for each state is in parentheses. ------------------------------------------ [8] [9] 01. Connecticut (1788) . Maine (1820) . . . Hawaii (1959) ............................................................ 0 [1] Indicates the variable and reference numbers. A variable number and a reference number are assigned to each variable in the data collection. In the present codebook which documents the archived data collection these numbers are identical. Should the data be subsetted or rearranged by an OSIRIS program (e.g., MMP to intersperse data from another source, or TCOT to produce an analysis deck), the variable numbers would change to reflect the order of the new data collection, while the reference number would remain unchanged to reflect the variable number in the codebook describing the archived data collection. 0 [2] Indicates the abbreviated variable name (maximum of 24 characters) used to identify the variable for the user. An expanded version of the variable name can be found in the variable description list. 1 XI 0 [3] Indicates the code values of missing data. In this example, there are no missing data codes Alternative statements for other variables are "MD=9999999," or "MD=0." Some analysis software packages (including the OSIRIS software package) require that certain types of data which the user desires to be excluded from analysis be designated as "MISSING DATA," e.g., inappropriate, unascertained, unascertainable, or ambiguous data categories. Although these codes are defined as missing data categories, this does not mean that the user should not or cannot use them in a substantive role if so desired. 0 [4] Indicates the starting location and width of this variable when the data are stored on a magnetic tape in LRECL format. If the variable is of a multiple-response type, the width referenced is that of a single response. In this example the variable named "ICPSR STATE CODE" is two columns wide and is located in the first column within the record. 0 [5] A variable containing data with implied decimals is denoted by the message "IMP DEC= 0," where 0 is the number of decimal places implied in the variable. 0 [6] This is the full text (question) supplied by the investigator to describe the variable. The question text and the numbers and letters that may appear at the beginning reflect the original wording of the questionnaire item. 0 [7] A comment optionally appears here in the codebook to provide explanatory information about the variable. 0 [8] Indicates the code values occurring in the data for this variable. 0 [9] Indicates the textual definitions of the codes. 1 XII 0 ICPSR PROCESSING INFORMATION 0 The data collection was processed according to the standard ICPSR processing procedures. The data were checked for illegal code values which, when found, were corrected by rechecking the original source materials. Whenever pertinent registration data were not available or judged too incomplete, missing data values were inserted for relevant variables. Numerous consistency checks were performed on these data in both the entry and processing stages of the construction of this data collection. Statements bracketed in "<" and ">" signs in the body of the codebook were added by the processors for explanatory purposes. 0 The data files in this collection are sorted by V4: ICPSR State Code and V6: ICPSR County Code, both in ascending order. 1 XIII 0 VARIABLE DESCRIPTION LIST 0 1 ICPSR Study Number-9405 2 ICPSR Edition Number-1 3 ICPSR Part Number-1 4 ICPSR State Code 5 County Name 6 ICPSR County Code 7 Number of voters registered with Democratic Party affiliation, 1968 8 Number of voters registered with Conservative Party affiliation, 1968 9 Number of voters registered with Republican Party affiliation, 1968 10 Number of voters registered with American Party affiliation, 1968 11 Number of voters registered with Independent Party affiliation, 1968 12 Number of voters registered with Liberal Party affiliation, 1968 13 Number of voters registered with Constitutional Party affiliation, 1968 14 Number of voters registered with American Independent Party affiliation, 1968 15 Number of voters registered with Peace and Freedom Party affiliation, 1968 16 Number of voters registered with American Party of [Nebraska] affiliation, 1968 17 Number of voters registered with "Miscellaneous" party affiliation, 1968 18 Number of voters registered with "minor parties" affiliation, 1968 19 Number of voters registered with "Ind. or N.P." affiliation [North Carolina], 1968 20 Number of voters registered with "Other" party affiliation, 1968 21 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1968 22 Number of voters registered with "Non Partisan" affiliation, 1968 23 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1968 24 Number of voters registered with "Declined to State" Party affiliation, 1968 25 Number of voters registered with "no party affiliation/no preference", 1968 26 Number of White registered voters, 1968 27 Number of Black registered voters, 1968 28 Number of Indians registered to vote, 1968 29 Number of Orientals registered to vote, 1968 1 30 Total registered voters, 1968 31 Number of voters registered with Democratic Party affiliation, 1970 32 Number of voters registered with Conservative Party affiliation, 1970 33 Number of voters registered with Republican Party affiliation, 1970 34 Number of voters registered with American Party affiliation, 1970 35 Number of voters registered with Independent Party affiliation, 1970 36 Number of voters registered with Liberal Party affiliation, 1970 37 Number of voters registered with Constitutional Party affiliation, 1970 38 Number of voters registered with American Independent Party affiliation, 1970 39 Number of voters registered with Peace and Freedom Party affiliation, 1970 40 Number of voters registered with American Party of [Nebraska] affiliation, 1970 41 Number of voters registered with "Miscellaneous" party affiliation, 1970 42 Number of voters registered with "minor parties" affiliation, 1970 43 Number of voters registered with "Ind. or N.P." affiliation [North Carolina], 1970 44 Number of voters registered with "Other" party affiliation, 1970 45 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1970 46 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1970 47 Number of voters registered with "Declined to State" Party affiliation, 1970 48 Number of voters registered with "Unclassified" affiliation, 1970 49 Number of White registered voters, 1970 50 Number of Black registered voters, 1970 51 Number of Non-White registered voters, 1970 52 Number of Indians or others registered to vote, 1970 53 Number of Indians registered to vote, 1970 54 Number of Orientals registered to vote, 1970 55 Total registered voters, 1970 56 Number of voters registered with Democratic Party affiliation, 1972 57 Number of voters registered with Conservative Party affiliation, 1972 58 Number of voters registered with Republican Party affiliation, 1972 59 Number of voters registered with American Party affiliation, 1972 60 Number of voters registered with Independent Party affiliation, 1972 1 61 Number of voters registered with Liberal Party affiliation, 1972 62 Number of voters registered with Constitutional Party affiliation, 1972 63 Number of voters registered with American Independent Party affiliation, 1972 64 Number of voters registered with Peace and Freedom Party affiliation, 1972 65 Number of voters registered with "Miscellaneous" party affiliation, 1972 66 Number of voters registered with "minor parties" affiliation, 1972 67 Number of voters registered with "Ind or N.P." affiliation [North Carolina], 1972 68 Number of voters registered with "Other" party affiliation, 1972 69 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1972 70 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1972 71 Number of voters registered with "Declined to State" Party affiliation, 1972 72 Number of voters registered with "Declined to State and others" Party affiliation, 1972 73 Number of voters registered with "Unclassified" affiliation, 1972 74 Number of White registered voters, 1972 75 Number of Black registered voters, 1972 76 Number of Non-White registered voters, 1972 77 Number of Indians or others registered to vote, 1972 78 Number of Indians registered to vote, 1972 79 Number of Orientals registered to vote, 1972 80 Total registered voters, 1972 81 Number of voters registered with Democratic Party affiliation, 1974 82 Number of voters registered with Conservative Party affiliation, 1974 83 Number of voters registered with Republican Party affiliation, 1974 84 Number of voters registered with American Party affiliation, 1974 85 Number of voters registered with Independent Party affiliation, 1974 86 Number of voters registered with Liberal Party affiliation, 1974 87 Number of voters registered with Labor Party affiliation, 1974 88 Number of voters registered with Constitutional Party affiliation, 1974 89 Number of voters registered with Independent American Party affiliation, 1974 90 Number of voters registered with American Independent Party affiliation, 1974 91 Number of voters registered with Peace and Freedom 1 Party affiliation, 1974 92 Number of voters registered with "Miscellaneous" party affiliation, 1974 93 Number of voters registered with "minor parties" affiliation, 1974 94 Number of voters registered with "Ind. or N.P." affiliation [North Carolina], 1974 95 Number of voters registered with "Other" party affiliation, 1974 96 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1974 97 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1974 98 Number of voters registered with "Declined to State" Party affiliation, 1974 99 Persons registered as of 7 AM election day [Minnesota], 1974 100 Persons registering on election day [Minnesota], 1974 101 Number of voters registered with "Unclassified" affiliation, 1974 102 Number of voters registered with "No party affiliation/no preference" affiliation, 1974 103 Number of White registered voters, 1974 104 Number of Black registered voters, 1974 105 Number of Non-White registered voters, 1974 106 Number of Indians or others registered to vote, 1974 107 Number of Indians registered to vote, 1974 108 Number of Orientals registered to vote, 1974 109 Total registered voters, 1974 110 Number of voters registered with Democratic Party affiliation, 1976 111 Number of voters registered with Conservative Party affiliation, 1976 112 Number of voters registered with Republican Party affiliation, 1976 113 Number of voters registered with American Party affiliation, 1976 114 Number of voters registered with Independent Party affiliation, 1976 115 Number of voters registered with Liberal Party affiliation, 1976 116 Number of voters registered with Constitutional Party affiliation, 1976 117 Number of voters registered with Independent American Party affiliation, 1976 118 Number of voters registered with American Independent Party affiliation, 1976 119 Number of voters registered with Peace and Freedom Party affiliation, 1976 120 Number of voters registered with Libertarian Party affiliation, 1976 121 Number of voters registered with American Party of [Nebraska] affiliation, 1976 122 Number of voters registered with "Miscellaneous" 1 party affiliation, 1976 123 Number of voters registered with "minor parties" affiliation, 1976 124 Number of voters registered with "Ind. or N.P." affiliation [North Carolina], 1976 125 Number of voters registered with "new parties" affiliation, 1976 126 Number of voters registered with "Other" party affiliation, 1976 127 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1976 128 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1976 129 Number of voters registered with "Declined to State" Party affiliation, 1976 130 Number of voters registered with "Unenrolled" Party affiliation, 1976 131 Number of voters registered with "Decline to State and others" Party affiliation, 1976 132 Persons registered as of 7 AM election day [Minnesota], 1976 133 Persons registering on election day [Minnesota], 1976 134 Number of voters registered with "Unclassified" affiliation, 1976 135 Number of White registered voters, 1976 136 Number of Black registered voters, 1976 137 Number of Non-White registered voters, 1976 138 Number of Indians or others registered to vote, 1976 139 Number of Indians registered to vote, 1976 140 Number of Orientals registered to vote, 1976 141 Total registered voters, 1976 142 Number of voters registered with Democratic Party affiliation, 1978 143 Number of voters registered with Conservative Party affiliation, 1978 144 Number of voters registered with Republican Party affiliation, 1978 145 Number of voters registered with American Party affiliation, 1978 146 Number of voters registered with Independent Party affiliation, 1978 147 Number of voters registered with Liberal Party affiliation, 1978 148 Number of voters registered with Independent American Party affiliation, 1978 149 Number of voters registered with American Independent Party affiliation, 1978 150 Number of voters registered with Peace and Freedom Party affiliation, 1978 151 Number of voters registered with Right to Life Party affiliation, 1978 152 Number of voters registered with Libertarian Party affiliation, 1978 153 Number of voters registered with "Miscellaneous" 1 party affiliation, 1978 154 Number of voters registered with "minor parties" affiliation, 1978 155 Number of voters registered with "Other" party affiliation, 1978 156 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1978 157 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1978 158 Number of voters registered with "Declined to State" Party affiliation, 1978 159 Number of voters registered with "Unenrolled" Party affiliation, 1978 160 Number of voters registered with "Decline to State and others" Party affiliation, 1978 161 Persons registered as of 7 AM election day [Minnesota], 1978 162 Persons registering on election day [Minnesota], 1978 163 Number of voters registered with "Unclassified" affiliation, 1978 164 Number of White registered voters, 1978 165 Number of Black registered voters, 1978 166 Number of Indians or others registered to vote, 1978 167 Number of Indians registered to vote, 1978 168 Number of Orientals registered to vote, 1978 169 Total registered voters, 1978 170 Number of voters registered with Democratic Party affiliation, 1980 171 Number of voters registered with Conservative Party affiliation, 1980 172 Number of voters registered with Republican Party affiliation, 1980 173 Number of voters registered with Independent Party affiliation, 1980 174 Number of voters registered with Liberal Party affiliation, 1980 175 Number of voters registered with American Independent Party affiliation, 1980 176 Number of voters registered with Peace and Freedom Party affiliation, 1980 177 Number of voters registered with Right to Life Party affiliation, 1980 178 Number of voters registered with Libertarian Party affiliation, 1980 179 Number of voters registered with "minor parties" affiliation, 1980 180 Number of voters registered with "Other" party affiliation, 1980 181 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1980 182 Number of voters registered with "Non Partisan" affiliation, 1980 183 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1980 1 184 Number of voters registered with "Declined to State" Party affiliation, 1980 185 Number of voters registered with "Unenrolled" Party affiliation, 1980 186 Number of voters registered with "Decline to State and others" Party affiliation, 1980 187 Persons registered as of 7 AM election day [Minnesota], 1980 188 Persons registering on election day [Minnesota], 1980 189 Number of voters registered with "Unclassified" affiliation, 1980 190 Number of voters registered with "No party affiliation/no preference" affiliation, 1980 191 Number of White registered voters, 1980 192 Number of Black registered voters, 1980 193 Number of Indians or others registered to vote, 1980 194 Number of Indians registered to vote, 1980 195 Number of Orientals registered to vote, 1980 196 Total registered voters, 1980 197 Number of voters registered with Democratic Party affiliation, 1982 198 Number of voters registered with Conservative Party affiliation, 1982 199 Number of voters registered with Republican Party affiliation, 1982 200 Number of voters registered with Independent Party affiliation, 1982 201 Number of voters registered with Liberal Party affiliation, 1982 202 Number of voters registered with Socialist Workers Party affiliation, 1982 203 Number of voters registered with American Independent Party affiliation, 1982 204 Number of voters registered with Peace and Freedom Party affiliation, 1982 205 Number of voters registered with Right to Life Party affiliation, 1982 206 Number of voters registered with Libertarian Party affiliation, 1982 207 Number of voters registered with "minor parties" affiliation, 1982 208 Number of voters registered with "Other" party affiliation, 1982 209 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1982 210 Number of voters registered with "Non Partisan" affiliation, 1982 211 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1982 212 Number of voters registered with "Declined to State" Party affiliation, 1982 213 Number of voters registered with "Unenrolled" Party affiliation, 1982 214 Number of voters registered with "Decline to State 1 and others" Party affiliation, 1982 215 Number of voters registered with "Undeclared Names on Checklist" [New Hampshire] affiliation, 1982 216 Persons registered as of 7 AM election day [Minnesota], 1982 217 Persons registering on election day [Minnesota], 1982 218 Number of voters registered with "Unclassified" affiliation, 1982 219 Number of voters registered with "No party affiliation/no preference" affiliation, 1982 220 Number of White registered voters, 1982 221 Number of Black registered voters, 1982 222 Number of voters registered with "Other race category" affiliation, 1982 223 Number of Non-White registered voters, 1982 224 Number of "Uncertain race category" registered voters, 1982 225 Number of Indians registered to vote, 1982 226 Number of Orientals registered to vote, 1982 227 Total registered voters, 1982 228 Number of voters registered with Democratic Party affiliation, 1984 229 Number of voters registered with Conservative Party affiliation, 1984 230 Number of voters registered with Republican Party affiliation, 1984 231 Number of voters registered with Independent Party affiliation, 1984 232 Number of voters registered with Liberal Party affiliation, 1984 233 Number of voters registered with Socialist Workers Party affiliation, 1984 234 Number of voters registered with American Independent Party affiliation, 1984 235 Number of voters registered with Peace and Freedom Party affiliation, 1984 236 Number of voters registered with Right to Life Party affiliation, 1984 237 Number of voters registered with Libertarian Party affiliation, 1984 238 Number of voters registered with Colorado Prohibition Party affiliation, 1984 239 Number of voters registered with Concerns of People Party, [Colorado] affiliation, 1984 240 Number of voters registered with "Miscellaneous" party affiliation, 1984 241 Number of voters registered with "minor parties" affiliation, 1984 242 Number of voters registered with "Other" party affiliation, 1984 243 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1984 244 Number of voters registered with "Non Partisan" affiliation, 1984 245 Number of voters registered with "Unaffiliated/ 1 Non-Affiliated" affiliation, 1984 246 Number of voters registered with "Declined to State" Party affiliation, 1984 247 Number of voters registered with "Unenrolled" Party affiliation, 1984 248 Number of voters registered with "Decline to State and others" Party affiliation, 1984 249 Number of voters registered with "Undeclared Names on Checklist" [New Hampshire] affiliation, 1984 250 Persons registered as of 7 AM election day [Minnesota], 1984 251 Persons registering on election day [Minnesota], 1984 252 Number of voters registered with "No party affiliation/no preference" affiliation, 1984 253 Number of White registered voters, 1984 254 Number of Black registered voters, 1984 255 Number of voters registered with "Other race category" affiliation, 1984 256 Number of "Unknown race category" registered voters, 1984 257 Number of Indians registered to vote, 1984 258 Number of Orientals registered to vote, 1984 259 Total registered voters, 1984 260 Number of voters registered with Democratic Party affiliation, 1986 261 Number of voters registered with Conservative Party affiliation, 1986 262 Number of voters registered with Republican Party affiliation, 1986 263 Number of voters registered with Independent Party affiliation, 1986 264 Number of voters registered with Liberal Party affiliation, 1986 265 Number of voters registered with American Independent Party affiliation, 1986 266 Number of voters registered with Peace and Freedom Party affiliation, 1986 267 Number of voters registered with Right to Life Party affiliation, 1986 268 Number of voters registered with Consumer Party affiliation, 1986 269 Number of voters registered with Libertarian Party affiliation, 1986 270 Number of voters registered with Colorado Prohibition Party affiliation, 1986 271 Number of voters registered with Concerns of People Party, [Colorado] affiliation, 1986 272 Number of voters registered with "minor parties" affiliation, 1986 273 Number of voters registered with "Independent or other" Party, [West Virginia] affiliation, 1986 274 Number of voters registered with "Other" party affiliation, 1986 275 Number of voters registered with "Blank, Void, and Missing" affiliation [New York], 1986 1 276 Number of voters registered with "Non Partisan" affiliation, 1986 277 Number of voters registered with "Unaffiliated/ Non-Affiliated" affiliation, 1986 278 Number of voters registered with "Declined to State" Party affiliation, 1986 279 Number of voters registered with "Unenrolled" Party affiliation, 1986 280 Persons registered as of 7 AM election day [Minnesota], 1986 281 Persons registering on election day [Minnesota], 1986 282 Number of voters registered with "No party affiliation/no preference" affiliation, 1986 283 Number of White registered voters, 1986 284 Number of Black registered voters, 1986 285 Number of voters registered with "Other race category" affiliation, 1986 286 Number of voters registered with "Unknown race category" affiliation, 1986 287 Number of Indians registered to vote, 1986 288 Number of Orientals registered to vote, 1986 289 Total registered voters, 1986 290 Number of voters registered with Democratic Party affiliation, 1988 291 Number o