![]() |
||
![]() ![]() |
||
|
|
||
| Home CodebooksLinks to Common Codebooks All Committees Codebook House Committees List Senate Committees List Joint Committees List Topic Codebook Links to Dataset Codebooks Budget- PDF (download) Budget- MS Word (download) Congressional Quarterly Executive Orders- MS Word (download) Hearings Most Important Problem- MS Word (download) New York Times Index Public Laws State of the Union - MS Word (download) Supreme Court Congressional Roll Call Votes - MS Word |
Codebook Appendices | Spaeth & Agendas Comparison | Certs Denied Dataset Supreme Court Dataset CodebookPage Contents: Overview of Data | Coding Scheme | Organization Download the data: Supreme Court Data (.xls) Download the codebook: .doc | .pdf Also see the five appendices that accompany this dataset: Coding Guidelines (A) | Citation Formats (B) | Court Procedures (C) | Glossary (D) | Resources (E) Special Section: Cert Denied Cases and the Supreme Court An Overview of the Data SetThe U.S. Supreme Court Data Set (1953-1998), created for the social scientist interested in the ways the U.S. Supreme Court effects public policy, tracks the policy agenda of the Court over time. If you are unfamiliar with Court procedures and/or terminology, we encourage you to refer to the outline and glossary of terms provided in appendices of this codebook before working with the dataset or for quick reference. Background To establish this dataset, we initially referenced “The Original U.S. Supreme Court Judicial Database” (nickname: ALL COURT) created by Harold J. Spaeth, currently the most comprehensive electronic U.S. Supreme Court data set available. Spaeth’s data set is intended primarily for legal (and policy scholars) researching the decision-making processes of the U.S. Supreme Court (i.e. determining what, when, and how cases are decided). Additionally, the data set includes all cases (granted or denied) where any justice is mentioned as having an opinion or dissent (regardless of whether or not the details of that opinion or dissent are published in U.S. Reports). The Policy Agendas Project's U.S. Supreme Court data set was created with the intent of (1) assigning the Policy Agenda’s Project coding scheme to all cases argued before the U.S. Supreme Court and (2) answering agenda-setting questions of the U.S. Supreme Court. Policy scholars are interested in examining the policy implications of the legal choices made by the Court, and studying whether some policy areas are favored over others by being granted certiorari, while legal scholars could be more interested in the particulars of the legal reasoning underpinning cases.. For more information on these two Supreme Court datasets, read former Undergraduate Fellow Paul Bryce Counts' analysis on this issue. The Dataset Worksheets The following section will walk users through the four data worksheets currently available:
Content CodingWe employed our standard 19 major topic and 220 minor topic codes used in the Policy Agendas Project to code all cases according to the policy content of each case’s summary as cited in U.S. Reports. However, we were careful to pay special attention to those policy areas unique to the Court (See Appendix A: U.S. Supreme Court Coding Guidelines for more information on this topic). The full description of content categories may be found in Topic Index on the Policy Agendas Project’s website. Back To TopOrganizationThe following is a brief description of each data column in the dataset. Each section of this description explains the coding rules for the data collected. Each section title is followed by the abbreviation of the variable as it appears at the top of the spreadsheet .
1. Case Citation ("citation")Most of the case citations (as well as dates of oral arguments and decisions) were taken from Spaeth’s “ ALL COURT” data set. The number corresponds to the volume and page number of U.S. Reports in which the case is listed. For example, 347/0403 à 347 U.S. 403 and can be found in volume 347, page 403 of U.S. Reports. See Appendix B for various case citation formats.Multiple Hits: As previously explained, retrieving multiple hits under a given case citation indicates that these cases are listed in the "Orders" section at the back of a given volume of U.S. Reports. Although little information is provided, some of these cases are included in the Spaeth data set if the do in fact mention a justice as having given an opinion or dissent (regardless of whether or not the details were published). The dataset does not include these case types because, in general, they are irrelevant to policy analysis. 2. Case Name ("name")The case name is placed in this column (e.g. United States v. Gilman).3. Docket Number ("docket #")Each case successfully filed with the Court assigned a docket number and that number placed in this column. See below when for how to handle additional docket numbers. The docket numbers consists of the year and consecutive case number (e.g. 97-3 is the third case filed in the 1997 term). In forma pauperis cases contain the year and begin with the number 5001 (e.g. 97-5003 is the third case filed in the 1997 term). Where no docket number is listed, a “0” is placed in the column as a placeholder. 4. Additional Docket Numbers ("docket x")When looking up a given case number in U.S. Reports, some cases have multiple docket numbers. These (similar) cases have been grouped together and a single Court decision made for all of them. The subsequent docket numbers are place in Column in those columns titled “docket x”. The case names for these subsequent cases are not (at this time) included in the dataset. Furthermore, we added rows to match the number of docket numbers for those cases with multiple docket numbers with ALL information from the original row (case #, description, topic code, dates, terms, case type, status) pasted into the subsequent rows. This allowed us to have a TOTAL count of ALL cases assigned a docket number. (When looking at decision-making processes in which multiple cases (i.e. multiple docket numbers) are grouped together under one ruling, this would not be necessary).For example:
Here there are two docket numbers under one citation. As a result, ALL the information from the original entry has been copied to the line allowing us to maintain a running total of the number of case within each topic/sub-topic code. Note: If no docket number is presented (for either the original docket number or for subsequent cases grouped under one ruling), a “0” is used as a place holder. 5. SummaryA comprehensive description or summary of the case was acquired in order to code each case according to the Policy Agendas Project coding scheme and allow for future isolation of as many potential variables as possible (case type [habeas corpus], policy issue, federal agencies mentioned, etc. In most instances, this information was obtained by searching LexisNexis and taking the “Summary” or the more detailed “Syllabus” of the case if no “Summary” section is present. For the purposes of public policy research, we felt the “Summary” section would suffice. However, if more detailed legal terminology is needed beyond a summary (e.g. detailed reasoning for bringing a given case forward and precedent cases cited), it may be necessary to consult of the “Syllabus” of each case and isolate variables accordingly.In some instances, little codable information is provided in this basic LexisNexis search, particularly for cases where certiorari was denied or cased decided per curiam. When this occurred, the following options were considered:
OR
OR
OR
Note: Summary information for cert-denied cases is usually obtained by looking up the lower court decisions. Unfortunately, coding solely on the basis of the content of each case summary provided in LexisNexis may not capture the intent of the justices for taking on a particular case. For example, a justice may elect to hear a case for the purpose of setting precedent in a given policy area (e.g. commerce), however the actual content of the case may reflect an entirely different policy area (e.g. civil rights). Because the factors involved in determining a justices’ intent for granting/denying certiorari, motions, etc. are far too numerous for our dataset to isolate if not explicitly stated in LexisNexis (See Appendix C: U.S. Supreme Court Procedures), we coded simply for the content/issue before the court (i.e. civil rights in this example), regardless of the court’s reasons for taking the case. Any further analysis as to “why” a given case is brought before the court (for the purpose of setting precedent or otherwise) is left to the researcher to determine. 6. Topic/Subtopic Code ("code")Using the description, the major policy issue of each case was identified and coded according to the coding scheme in the Policy Agendas Project, paying special attention to those policy areas unique to the Court. Refer to U.S. Supreme Court Coding Guidelines. Because the dataset examines agenda setting, cases were coded according to the issue brought before the court and not the issue ultimately decided upon. For example, a case brought before the court as a discrimination, but later ruled as a commerce case is coded as a discrimination. In this regard, adjustments to the coding scheme will need to be made for the purposes of analyzing decision-making policy trends of the court. 7. RulingThis column only applies those cases where a formal ruling was present and lists how each judge voted in a given case (decision, concurring, dissenting opinions.) In most instances, this data was found in the second paragraph of the “Summary” or in the more detailed “Opinion” sections for a given case in LexisNexis. For the purposes of public policy research, the ruling paragraph of the “Summary” section is often sufficient. (In most cases this section begins in the second paragraph of the “Summary” with such phrases as “On certiorari…” or “On Appeal…” and includes all subsequent paragraphs to the of the section). However, if more detailed legal terminology is needed (e.g. detailed reasoning of the court and specific precedent cases cited in the ruling), it may be necessary to consult of the “Opinion” of each case.Additional information on current court rulings (and archives organized by topic, author, etc.) can be found at Legal Information Institute . Special considerations:
8. Case Type ("type")From the ruling, each case type is categorized according to U.S. Reports which correspond to the following abbreviations:
See Types of Cases before the Court in Appendix C: U.S. Supreme Court Procedures 9. Vacated and Dismissed ("vac" and "dis")Those cases granted certiorari, on appeal, motion, or misc. orders but then later vacated or dismissed are organized in the “Orders” section at the back of U.S. Reports. For organizational purposes with this dataset, we treat vacated and dismissed cases as a type of ruling. Therefore, there are separate columns for each within the dataset (“vac” and “dis”, respectively). Cases are coded “1” if ANY part of the case is vacated or dismissed (in full or in part) and “0” if they are not under their respective columns.10. Granted/Denied ("g/d")Each of the cases types are coded either “0” or “1” for granted or denied, respectively according to whether or not the case passed the “rule of four” and came before the court for a formal decision to be rendered. For example, any case granted certiorari, appeal, motion, or misc. order is coded as “0” and any case denied certiorari, appeal, motion, or misc. order would be coded as “1”.11. OralThis is the date the Court began hearing the case. In those instances where no date was provided in this category, we used the “decision” date in order to determine the term/year the case was heard. For these cases, the dates were bolded in order to identify them.12. DecisionThis is the date the case was decided upon.13. Term AThis is the Term in which the case was heard and not necessarily decided upon. Each Court term lasts between October of a given year and June of the following year. Therefore, even if the Court began hearing arguments for the case on May 2, 1966, it still falls under the 1965 term. (e.g. October 1965-June 1966 > 1965)14. Term BIn order to answer our agenda-setting question and make the Court dataset consistent with the Most Important Problem (MIP) and New York Times (NYT) datasets, we adjusted the court terms to calendar year rather than the actual October to June terms. In this way, cases heard from January 1-December 31 of a given year were grouped together (e.g. January 1, 1966-December 31, 1966 > 1966.Back To TopWritten by:Michelle Huynh, fmr. Undergraduate Fellow, CAPP |
|
![]() |
||
| © 2004 University of Washington. All Right Reserved. Credits and Acknowledgements | Disclaimer | Citation Guidelines | ||
| Home | Codebooks | Datasets | Data Tools | Publications | News & Events | Resources | About Us | Site Help | Contact Us | Site Map | ||