cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.15156/bio/sh0989315.09fu
title: SH0989315.09FU

description: UNITE provides a unified way for delimiting, identifying, communicating, and working with DNA-based Species Hypotheses (SH). All fungal ITS sequences in the international nucleotide sequence databases are clustered to approximately the species level by applying a set of dynamic distance values (<0.5 - 3.0%). All species hypotheses are given a unique, stable name in the form of a DOI, and their taxonomic and ecological annotations are verified through distributed, web-based third-party annotation efforts. SHs are connected to a taxon name and its classification as far as possible (phylum, class, order, etc.) by taking into account identifications for all sequences in the SH. An automatically or manually designated sequence is chosen to represent each such SH. These sequences are released (https://unite.ut.ee/repository.php) for use by the scientific community in, for example, local sequence similarity searches and next-generation sequencing analysis pipelines. The system and the data are updated automatically as the number of public fungal ITS sequences grows.
DOI: 10.15156/bio/sh0989316.09fu
title: SH0989316.09FU

description: UNITE provides a unified way for delimiting, identifying, communicating, and working with DNA-based Species Hypotheses (SH). All fungal ITS sequences in the international nucleotide sequence databases are clustered to approximately the species level by applying a set of dynamic distance values (<0.5 - 3.0%). All species hypotheses are given a unique, stable name in the form of a DOI, and their taxonomic and ecological annotations are verified through distributed, web-based third-party annotation efforts. SHs are connected to a taxon name and its classification as far as possible (phylum, class, order, etc.) by taking into account identifications for all sequences in the SH. An automatically or manually designated sequence is chosen to represent each such SH. These sequences are released (https://unite.ut.ee/repository.php) for use by the scientific community in, for example, local sequence similarity searches and next-generation sequencing analysis pipelines. The system and the data are updated automatically as the number of public fungal ITS sequences grows.
DOI: 10.15156/bio/sh0989317.09fu
title: SH0989317.09FU

description: UNITE provides a unified way for delimiting, identifying, communicating, and working with DNA-based Species Hypotheses (SH). All fungal ITS sequences in the international nucleotide sequence databases are clustered to approximately the species level by applying a set of dynamic distance values (<0.5 - 3.0%). All species hypotheses are given a unique, stable name in the form of a DOI, and their taxonomic and ecological annotations are verified through distributed, web-based third-party annotation efforts. SHs are connected to a taxon name and its classification as far as possible (phylum, class, order, etc.) by taking into account identifications for all sequences in the SH. An automatically or manually designated sequence is chosen to represent each such SH. These sequences are released (https://unite.ut.ee/repository.php) for use by the scientific community in, for example, local sequence similarity searches and next-generation sequencing analysis pipelines. The system and the data are updated automatically as the number of public fungal ITS sequences grows.
DOI: 10.15156/bio/sh0989318.09fu
title: SH0989318.09FU

description: UNITE provides a unified way for delimiting, identifying, communicating, and working with DNA-based Species Hypotheses (SH). All fungal ITS sequences in the international nucleotide sequence databases are clustered to approximately the species level by applying a set of dynamic distance values (<0.5 - 3.0%). All species hypotheses are given a unique, stable name in the form of a DOI, and their taxonomic and ecological annotations are verified through distributed, web-based third-party annotation efforts. SHs are connected to a taxon name and its classification as far as possible (phylum, class, order, etc.) by taking into account identifications for all sequences in the SH. An automatically or manually designated sequence is chosen to represent each such SH. These sequences are released (https://unite.ut.ee/repository.php) for use by the scientific community in, for example, local sequence similarity searches and next-generation sequencing analysis pipelines. The system and the data are updated automatically as the number of public fungal ITS sequences grows.
DOI: 10.3886/icpsr20303.v1
title: National Incident-Based Reporting System, 2005: Extract Files
title: Version 1

description: The National Incident-Based Reporting System (NIBRS) is a part of the Uniform Crime Reporting Program (UCR), administered by the Federal Bureau of Investigation (FBI). The extract files version of NIBRS is an attempt to simplify working with NIBRS data. Data management issues with NIBRS are significant, especially when two or more segment levels are being merged. These issues require skills separate from data analysis. NIBRS data as formatted by the FBI are stored in a single file. These data are organized by various segment levels (record types). There are six main segment levels: administrative, offense, property, victim, offender, and arrestee. Each segment level has a different length and layout. There are other segment levels that occur with less frequency than the six main levels. Significant computing resources are necessary to work with the data in its single-file format. In addition, the user must be sophisticated in working with data in complex file types. For these reasons and the desire to facilitate the use of NIBRS data, ICPSR created the extract files. The data are not a representative sample of crime in the United States.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Checked for undocumented or out-of-range codes..
description: Datasets: 
 
 DS0: Study-Level Files 
 DS1: Incident-Level File 
 DS2: Victim-Level File 
 DS3: Offender-Level File 
 DS4: Arrestee-Level File
description: National Incident-Based Reporting System (NIBRS) Series
description: self-enumerated questionnaire
description: Law enforcement agencies in the United States participating in the National Incident-Based Reporting System.
DOI: 10.3886/icpsr00101
title: Annotated Bibliography of Papers Using the General Social Surveys [10th Edition], March 1995
title: Archival Version

description: No summary available for this study.
DOI: 10.3886/icpsr00101.v1
title: Annotated Bibliography of Papers Using the General Social Surveys [10th Edition], March 1995
title: Version 1

description: No summary available for this study.
DOI: 10.3886/icpsr03006
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1993
title: Archival Version

description: In response to a growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act required the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and continue for four successive years. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include: number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: 2009-02-11 This data collection has been deaccessioned and is no longer available.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reports hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.
DOI: 10.3886/icpsr03007
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1994
title: Archival Version

description: In response to a growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act required the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and continue for four successive years. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include: number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: 2009-02-11 This data collection has been deaccessioned and is no longer available.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reports hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.
DOI: 10.3886/icpsr03007.v1
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1994
title: Version 1

description: In response to a growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act required the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and continue for four successive years. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include: number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: 2009-02-11 This data collection has been deaccessioned and is no longer available.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reports hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.
DOI: 10.3886/icpsr03008
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1995
title: Archival Version

description: In response to growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act required the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage, or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and continue for four successive years. In September 1994, the Violent Crime Control and Law Enforcement Act amended the Hate Crime Statistics Act to add disabilities, both physical and mental, as factors that could be considered a basis for hate crimes. Although the Act originally mandated data collection for a total of five years, the Church Arson Prevention Act of 1996 amended the collection duration "for each calendar year," making hate crime statistics a permanent addition to the UCR program. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: 2009-02-11 This data collection has been deaccessioned and is no longer available.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reported hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.
DOI: 10.3886/icpsr03008.v1
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1995
title: Version 1

description: In response to growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act required the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage, or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and continue for four successive years. In September 1994, the Violent Crime Control and Law Enforcement Act amended the Hate Crime Statistics Act to add disabilities, both physical and mental, as factors that could be considered a basis for hate crimes. Although the Act originally mandated data collection for a total of five years, the Church Arson Prevention Act of 1996 amended the collection duration "for each calendar year," making hate crime statistics a permanent addition to the UCR program. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: 2009-02-11 This data collection has been deaccessioned and is no longer available.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reported hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.
DOI: 10.3886/icpsr03027
title: Uniform Crime Reporting Program Data [United States]: Hate Crime Data, 1996
title: Archival Version

description: In response to a growing concern about hate crimes, Congress enacted the Hate Crime Statistics Act of 1990. The Act requires the Attorney General to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson and destruction, damage or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and to continue for four successive years. In September 1994, the Violent Crime Control and Law Enforcement Act amended the Hate Crime Statistics Act to add disabilities, both physical and mental, as factors that could be considered a basis for hate crimes. Although the Act originally mandated data collection for five years, the Church Arson Prevention Act of 1996 amended the collection duration "for each calendar year," making hate crime statistics a permanent addition to the UCR program. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data include number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.
description: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes..
description: This data collection has been deaccessioned and is no longer available. Replaced by study 23841.
The data are organized in a hierarchical file structure. There are two record types, batch header and incident record. Each police agency represented in the file has a single batch header record. If a police agency reported hate crime incidents, then one incident record for each hate crime incident is listed in the file immediately after the corresponding batch header record. There are 53 variables for the batch header record and 60 variables for the incident record.
description: Hate crime incidents reported by law enforcement agencies in the United States.