cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.5281/zenodo.3782255
title: Stereoretention in styrene heterodimerisation promoted by one-electron oxidants

description: This folder contains the optimised geometries (in .xyz format together with the gas-phase energy, E) accompanying the paper title: <strong>Stereoretention in styrene heterodimerisation promoted by one-electron oxidants</strong> Where conformers occur, they are always named from the lowest Gibbs energy to the highest in ascending order from c1, c2, ... This folder has the following structure and they correspond to the raw data in the SI: /0_sm/ --&gt; contains structures for the starting materials /P1/ --&gt; structures for reaction pathway P1 (trans-anethole + trans-beta-methylstyrene) /P2/ --&gt; structures for reaction pathway P2 (trans-anethole + cis-beta-methylstyrene) /rot_TSs/ --&gt; structures for the rotational TS structures connecting pathways P1 and P2
DOI: 10.13012/b2idb-3074701_v1
title: Soil organic carbon (SOC) response to soil management practices in the continental United States

description: This dataset was compiled between 2010 and 2011 from data published in the scientific literature from articles evaluating the influence of cropping systems and soil management practices on soil organic Carbon. We used the Thomas Reuter Web of Science database and by reviewed the reference sections of key peer-reviewed articles. Articles included in the database presented results from field sites within the continental United States.
DOI: 10.5063/f1mg7mrt
title: INPFC/NPAFC High-seas salmonid tag-recovery database, 1956 - 2013

description: This data set contains information on the high-seas tag recovery program for salmon and steelhead from the 1950s to 2013 in the North Pacific Ocean, Gulf of Alaska, and Bering Sea, from the North Pacific Anadromous Fish Commission. The database was last updated in April of 2016, and this version was provided in November of 2016. Data are provided on the location, species, age, sex, and initial tag location. Annual high seas salmon recovery information have been reported annually to the International North Pacific Fisheries Commission (1981–1992) and to the North Pacific Anadromous Fish Commission (1993–present). The tag recovery program enables the investigation of ocean distribution, migration, and growth of salmon at sea. Here, only information from non-electronic tags are reported. Information are available for salmon species: chinook (Oncorhynchus tshawytscha), chum (Oncorhynchus keta), coho (Oncorhynchus kisutch), pink (Oncorhynchus gorbuscha), sockeye (Oncorhynchus nerka), and steelhead (Oncorhynchus mykiss). Researchers using these data are cautioned to possible biases in the data caused from non-random area of tag release and from recovery of tagged fish in coastal areas that may not reflect the basin or area of origin. A discussion of these issues is provided in Myers et al. (1996). Included maps are generated from the dataset and show the release month by species, and the recovery region at release point. These maps were created by researchers at the National Center for Ecological Analysis and Synthesis.
DOI: 10.15787/vtt1/i6yfo2
title: Analysis of High Visibility Crosswalk Effectiveness in Improving New York State Safety

description: Project Description This study intends to provide new insight into the effectiveness of HVC markings in reducing risks of pedestrian vehicle crashes and conflicts at uncontrolled intersections. Data Request Scope 18 High Visibility Crosswalks (HVCs) were selected for this study, defined by GPS coordinates and roadway Link IDs. Data was generated in three phases. First, data was generated about all HVC crossings contained within SHRP 2 for a given period before and after the HVC was installed. Using this crossing data, specific HVC crossings were identified for additional analysis, and a second phase of data was generated containing front video and time series data, starting 15 seconds prior to crossing and 50 seconds after. Finally, a secondary extraction of data was requested from up to 500 events where a vehicle/pedestrian encounter was detected via video review. Some of the front videos and time series data from phases two and three are only available in a secure data enclave. Data Specification During the first phase, the following data was generated for each traversal for each of the 18 HVCs: • FILE_ID (unique identifier for each data file) • Date of trip (including day of month, month and year) • Binned time of the trip's entrance into the HVC road segment (local to the trip's location) • Participant ID • Participant age (as an age range) • Participant gender • Vehicle ID • Vehicle make • Vehicle model • Vehicle year • Trip exportability • Vehicle heading at the trip's entrance into the HVC road segment During the second phase, front video and time series data was extracted for specifically identified HVC crossings, providing (when available): • timestamp • FILE_ID • accel_x • accel_y • heading • latitude • longitude • speed_gps • speed_network • pedal_brake_state • pedal_gas_position • steering_wheel_position • video_frame • OBJECT_ID for lead vehicle • X_POS_PROCESSED for lead vehicle • Y_POS_PROCESSED for lead vehicle • IS_LEAD_VEHICLE • HEADWAY for lead vehicle In the final phase, the following data was extracted for up to 500 events:: • Eye glance location (coded from video) • Head rotation y • Head rotation y baseline • Head Confidence --
DOI: 10.5066/p93wd0th
title: Chemical and isotopic data for a study of seasonality of nitrate sources and isotopic composition in the Upper Illinois River, 2004-2008

description: This data release contains chemical and isotopic data used in an investigation of nitrate sources and transport in the Upper Illinois River basin. Samples (total = 445) include river water from the Upper Illinois River and its major tributaries plus urban wastewater and agricultural groundwater. Data include concentrations of nitrate, chloride, and sulfate; isotope ratios of N and O in nitrate; and isotope ratios of H and O in water.
DOI: 10.5281/zenodo.1471094
title: Dataset for "Tidal control of the flow through long, narrow straits: a modeling study for the Seto Inland Sea"

description: This dataset contains simulated results used to draw figures in the following paper. Kurogi, M. & Hasumi, H. Tidal control of the flow through long, narrow straits: a modeling study for the Seto Inland Sea, Sci. Rep. 9, 11077 (2019). ==== List of data dep_T.nc: Depth of tracer point<br> dep_V.nc: Depth of velocity point<br> ssh.nc: Sea Surface Height for TIDE (hourly snapshots of July 2012)<br> ubt_TIDE.nc: Eastward barotropic velocity for TIDE (monthly mean)<br> vbt_TIDE.nc: Northward barotropic velocity for TIDE (monthly mean)<br> ubt_NTIDE.nc: Eastward barotropic velocity for NTIDE (monthly mean)<br> vbt_NTIDE.nc: Northward barotropic velocity for NTIDE (monthly mean)<br> ubt_NTIDE_DV0.nc: Eastward barotropic velocity for NTIDE_DV0 (monthly mean)<br> vbt_NTIDE_DV0.nc: Northward barotropic velocity for NTIDE_DV0 (monthly mean)<br> ubt_NTIDE_D.nc: Eastward barotropic velocity for NTIDE_D (monthly mean)<br> vbt_NTIDE_D.nc: Northward barotropic velocity for NTIDE_D (monthly mean)<br> ubt_NTIDE_DV.nc: Eastward barotropic velocity for NTIDE_DV (monthly mean)<br> vbt_NTIDE_DV.nc: Northward barotropic velocity for NTIDE_DV (monthly mean)<br> ubt_NTIDE_DVA.nc: Eastward barotropic velocity for NTIDE_DVA (monthly mean)<br> vbt_NTIDE_DVA.nc: Northward barotropic velocity for NTIDE_DVA (monthly mean)<br> ubt_inout.nc: Eastward barotropic velocity for the inflow-outflow model (monthly mean)<br> vbt_inout.nc: Northward barotropic velocity for the inflow-outflow model (monthly mean)<br> amv_TIDE.nc: Vertical average of vertical viscosity for TIDE (monthly mean)<br> ahv_TIDE.nc: Vertical average of vertical diffusivity for TIDE (monthly mean)<br> amv_NTIDE.nc: Vertical average of vertical viscosity for NTIDE (monthly mean)<br> ahv_NTIDE.nc: Vertical average of vertical diffusivity for NTIDE (monthly mean)<br> ke.nc: Vertical average of kinetic energy per unit mass for TIDE (monthly mean)<br> ke_bt.nc: Vertical average of barotropic kinetic energy per unit mass for TIDE (monthly mean)
DOI: 10.5281/zenodo.1471095
title: Dataset for "Tidal control of the flow through long, narrow straits: a modeling study for the Seto Inland Sea"

description: Please see the new version (2.0).
DOI: 10.21223/p3/cnbvaw
title: Replication data for: A large-scale viability assessment of the potato cryobank at the International Potato Center (CIP)

description: The data describes status and progress in CIP’s potato cryobank from 2013-16. The accessions' recovery and survival rates were analysed by species/subspecies, ploidy level, and country of origin to determine factors that affect the success rate. Additionally, it includes the results of a large-scale viability reassessment of 857 potato accessions, conserved for 1–2 yr in liquid nitrogen, and an assessment of the influence of the human factor on survival and recovery rates (+LN).
DOI: 10.21223/p3/xjja5z
title: Replication data for: The potato cryobank at the International Potato Center (CIP): A model for long-term conservation of clonal plant genetic resources collection for the future

description: The data describes status and progress in CIP’s potato cryobank from 2013-15. The accessions' recovery and survival rates were analysed by species/subspecies. It includes the results of a large-scale viability reassessment of 109 potato accessions, conserved for 1–2 yr in liquid nitrogen.
DOI: 10.23721/100/1478811
title: Building a DGA Classifier: Part 1, Data Preparation

description: The purpose of building a DGA classifier isn’t specifically for takedowns of botnets, but to discover and detect the use on our network or services. If we can you have a list of domains resolved and accessed at your organization, it is possible now to see which of those are potentially generated and used by malware. The dataset consists of three sources (as decribed in the Data-Driven Security blog): Alexa: For samples of legitimate domains, an obvious choice is to go to the Alexa list of top web sites. But it’s not ready for our use as is. If you grab the top 1 Million Alexa domains and parse it, you’ll find just over 11 thousand are full URLs and not just domains, and there are thousands of domains with subdomains that don’t help us (we are only classifying on domains here). So after I remove the URLs, de-duplicated the domains and clean it up, I end up with the Alexa top 965,843. “Real World” Data from OpenDNS: After reading the post from Frank Denis at OpenDNS titled “Why Using Real World Data Matters For Building Effective Security Models”, I grabbed their 10,000 Top Domains and their 10,000 Random samples. If we compare that to the top Alexa domains, 6,901 of the top ten thousand are in the alexa data and 893 of the random domains are in the Alexa data. I will clean that up as I make the final training data set. DGA do: The Click Security version wasn’t very clear in where they got their bad domains so I decided to collect my own and this was rather fun. Because I work with some interesting characters (who know interesting characters), I was able to collect several data sets from recent botnets: “Cryptolocker”, two seperate “Game-Over Zues” algorithms, and an anonymous collection of malicious (and algorithmically generated) domains. In the end, I was able to collect 73,598 algorithmically generated domains. ;
DOI: 10.23721/100/1478816
title: ISOT Fake News Dataset

description: The dataset contains two types of articles fake and real News. This dataset was collected from realworld sources; the truthful articles were obtained by crawling articles from Reuters.com (News website). As for the fake news articles, they were collected from different sources. The fake news articles were collected from unreliable websites that were flagged by Politifact (a fact-checking organization in the USA) and Wikipedia. The dataset contains different types of articles on different topics, however, the majority of articles focus on political and World news topics. ; itraore at ece.uvic.ca
DOI: 10.23721/100/1478825
title: The Columbia/Enhants Dataset

description: This dataset includes radiant light energy measurements from a study by Columbia University's EnHANTs (Energy Harvesting Active Networked Tags) project. ; mag2206@columbia.edu
DOI: 10.23721/100/1478842
title: The hasselt/EDM dataset

description: A complete collection of all management and control frames (including Radiotap headers) observed at our research lab from 28 January to 8 Febuary 2016. This dataset was used to calculate the "stability" and "variability" of Probe Request IEs (see our paper for more details on these metrics). ; pieter.robyns@uhasselt.be
DOI: 10.23721/100/1478860
title: The kyutech/interference dataset

description: The common wisdom tells one not to attach more than 5-10 wireless devices to an access point. This is a problem in wireless educational classes, one can get between 10 and 50 students in the same room. Such spaces are referred to as dense wireless networks. While there are several methods that can be used to deal with dense wireless environments, installing multiple APs and separating them by channel is arguably the most readily available method today. In 802.11g/n the practical advice is to assign CH1, CH5 and CH9 to the three APs. However, even in such environments, wireless channels can become congested. It was noticed that tablet terminals would often fail to complete HTTP requests or fail getting access to the wireless channel entirely. In order to deal with this reliability problem, educational webapps had to be updated in such a way that they would detect failed requests and repeat them multiple times until a valid reply comes back. This dataset contains measurements which can help model such environments and the related application logic. The dataset has slightly non-trivial metrics which described failed/repeated. The experiment was run over multiple parameters and with on-the-fly changes in the layout. The measurement itself was simple -- a web application (in browser) on user terminal would send a GET request to the web server and would download bulk of a randomly selected size. All the performance metrics were recorded at user terminals and gradually uploaded to the server -- specifically, each new request would also contain the variables containing the results of the previous request, which had negligible effect on size but facilitated efficient log-keeping. ; maratishe@gmail.com
DOI: 10.23721/100/1478953
title: TLS in the E-mail Ecosystem (2015-04-01 to 2015-08-01)

description: SSLyze results for e-mail related TCP ports Ports: 25, 110, 143, 465, 587, 993, 995 Format: Tarball of LZ4 compressed XML results of SSLyze. Some files contain exactly one host, other files contain up to 100 targets per XML file. XML-Schema is found in the SSLyze source code (https://github.com/nabla-c0d3/sslyze) ; wmayer@sba-research.org
DOI: 10.23721/100/1478954
title: Alexa Top Million Session Ticket Scans

description: These scans were collected from 03Mar2016 to 04May2016 for the purposes of tracking Session Ticket Encryption Key longevity. Each day, the current Alexa Top Million domains were probed and prompted to issue a session ticket via the Session Ticket Extension in the Client Hello and any issued session ticket was stored for analysis. ; zmap-team@umich.edu
DOI: 10.23721/100/1478959
title: Nonce-Disrespecting Adversaries: Practical Forgery Attacks on GCM in TLS

description: With an Internet-wide scan we identified 184 HTTPS servers repeating nonces, which fully breaks the authenticity of the connections. Affected servers include large corporations, financial institutions, and a credit card company. We present a proof of concept of our attack allowing to violate the authenticity of affected HTTPS connections which in turn can be utilized to inject seemingly valid content into encrypted sessions. Furthermore, we discovered over 70,000 HTTPS servers using random nonces, which puts them at risk of nonce reuse, in the unlikely case that large amounts of data are sent via the same session. Fingerprints are SHA256 not SHA-1 as indicated. ; azet@azet.org
DOI: 10.23721/100/1478960
title: SNI Proxy ZMap Scans

description: zmap.sniproxy.20161024.csv.xz contains the ZMap CSV output of full TCP SYN scans of the IPv4 address against port 443, and contains the following fields: saddr, saddr_raw, daddr, daddr_raw, ipid,ttl, sport, dport, seqnum, acknum, window, classification, success, repeat, cooldown, timestamp_str, timestamp_ts, timestamp_us. scan-sniproxy.20161024.csv.xz contains the CSV output of a custom scan-sniproxy program, which connects to a TLS server using a specific SNI value and records a hash of the certificate returned by the server and any validation errors. The scan-sniproxy output has the following fields: date, target, host, port, sni, elapsed, is_sniproxy, spki_sha256, error. date is a timestamp and elapsed is the time elapsed start to finish for a particular server. target and host are both the IP address of the server (scan-sniproxy allows specifying a target by hostname; in that case the hostname would be in the target field and the IP address would be in the host field). port is always 443 in this dataset. sni is always "sni-scan-for-research-study.bamsoftware.com" in this dataset. is_sniproxy is "T" or "F". spki_sha256 is the SHA-256 hash of the certificate Subject Public Key Info, or blank in the case of a validation error. error is a validation error string, or blank. The value for spki_sha256 that indicates successful proxying is de15ef2559e770a3a283d632c94fe578f988c5768573a40caa28ff13cbd854d5. The file contains one false positive, 50.116.53.83, which was the actual IP address of sni-scan-for-research-study.bamsoftware.com. ; david@bamsoftware.com
DOI: 10.23721/100/1478961
title: Zonefile Database

description: A sqlite3 database of Zonefiles compiled from publicly available sources, that is updated once per month. Concept: - Take the work accomplished by Hanno Böck, and allow it to be queried in meaningful ways - Allow for the addition of new zonefiles - Make this dataset publicly available - Raise general awareness on the inherit risk of allowing for Zonefile Transfers Current Statistics: - Number of Resource Records: 59,157,877 - Domains scanned thus far: 6,853,165 - Domains which allowed for a Zonefile Transfer: 509,919 - Nameservers which allowed for a Zonefile Transfer: 130,404 ; info@ethicalreporting.org
DOI: 10.23721/100/1478964
title: Scan for AXFR DNS replies

description: AXFR is a feature of DNS that is usually not meant to be publicly accessible. However a large number of DNS servers answer to AXFR requests, most of them probably due to misconfiguration. ; hanno@hboeck.de
DOI: 10.23721/100/1478965
title: Security Challenges in an Increasingly Tangled Web Crawls (2016-10-05 to 2016-07-10)

description: Crawl of the Alexa Top Million domains from October 5-7, 2016 using ZBrowse, a headless Chrome browser instrumented to track object dependencies. The dataset contains one JSON blob per website, and presents the dependencies loaded by the website in a tree structure. ; team@censys.io
DOI: 10.23721/100/1478966
title: Alexa Top 1 Million Download and Lookups

description: no description
DOI: 10.23721/100/1478967
title: More SSL Certificates (non-443)

description: The dataset contains a collection of metadata related to the net new X.509 certificates observed in each study when considering all SSL studies that ran prior. The _hosts and _endpoints files provide mapping between the IPs/endpoints and the fingerprint of the X.509 certificate presented. The _certs file provides a mapping of the net new certificates from a given study and the corresponding fingerprint. The _names file provides a mapping of the X.509 certificate name (CN) to its fingerprint. ; research@rapid7.com
DOI: 10.23721/100/1478968
title: SSL Certificates

description: The dataset contains a collection of metadata related to the net new X.509 certificates observed in each study when considering all SSL studies that ran prior. The _hosts and _endpoints files provide mapping between the IPs/endpoints and the fingerprint of the X.509 certificate presented. The _certs file provides a mapping of the net new certificates from a given study and the corresponding fingerprint. The _names file provides a mapping of the X.509 certificate name (CN) to its fingerprint. ; research@rapid7.com
DOI: 10.23721/100/1478969
title: HTTP GET Responses

description: Ths dataset contains the responses to HTTP/1.1 GET requests performed against a variety of IPv4 public HTTP endpoints ; research@rapid7.com
DOI: 10.23721/100/1478973
title: ATG 10001/TCP SYN Scans

description: The datasets here include the list of IP addresses that responded to our TCP SYN scans against port 10001 in a manner that indicates that the port is open. ; research@rapid7.com
DOI: 10.23721/100/1478974
title: TCP Scans

description: The dataset contains regular snapshots of the responses to zmap probes against common TCP services ; research@rapid7.com
DOI: 10.23721/100/1478977
title: Critical.IO Service Fingerprints

description: The current dataset contain a monthly snapshot of each unique service response found on each responsive host. In the cases of services where a unique response is received for each request (HTTP, due to Date headers, etc), each of these will be represented as a unique record in one of the monthly JSON exports. ; research@rapid7.com
DOI: 10.23721/100/1478978
title: National Exposure Scans

description: The dataset represents the raw data collected that was used in the production of Rapid7's 2016-2018 National Exposure report (https://github.com/rapid7/data/tree/master/national-exposure). Each file here contains the IPv4 addresses that responded positively to a particular TCP or UDP probe used in that respective year's analysis. ; research@rapid7.com
DOI: 10.23721/100/1478982
title: Provider Web Abuse Leaderboard

description: This feed is filterable by Rank, Host ASN, Network, Days Unresolved, Insidents Reported, Last Reported: Rank– Rank of UNRESOLVED ISP ABUSE LEADERBOARD Host ASN- unique number that's available globally to identify an autonomous system Network – Network in which attack took place Day Unresolved – amount of days issue was unresolved Insidents Reported –amount of insidents reported Last Reported- Date issue was last reported ;
DOI: 10.23721/100/1478983
title: Provider Net Abuse Leaderboard

description: This feed is filterable by Rank, Host ASN, Network, Days Unresolved, Insidents Reported, Last Reported: Rank– Rank of UNRESOLVED ISP ABUSE LEADERBOARD Host ASN- unique number that's available globally to identify an autonomous system Network – Network in which attack took place Day Unresolved – amount of days issue was unresolved Insidents Reported –amount of insidents reported Last Reported- Date issue was last reported ;
DOI: 10.23721/100/1478984
title: IP Web Abuse Leaderboard

description: This feed is filterable by Rank, Days Unresolved, Insidents Reported, Attacker IP, Network, Reported Emails, Last Calculated: Rank– Rank of IP web Abuse Days Unresolved- number of days unresolved Insidents Reported –amount of insidents reported Attacker IP- Specific IP of abuse attcker ;
DOI: 10.23721/100/1478985
title: IP Net Abuse Leaderboard

description: This feed is filterable by Rank, Host ASN, Network, Days Unresolved, Insidents Reported, Last Reported: Rank– Rank of UNRESOLVED ISP ABUSE LEADERBOARD Host ASN- unique number that's available globally to identify an autonomous system Network – Network in which attack took place Day Unresolved – amount of days issue was unresolved Insidents Reported –amount of insidents reported Last Reported- Date issue was last reported ;