cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.7910/dvn/9argzn/mucfwi
title: Model_oc_88_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nsugqj
title: Model_ic_22_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/o0a1bp
title: Model_oc_26_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pkplk6
title: Model_oc_86_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qftabm
title: Model_oc_127_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ramaxl
title: Model_ic_33_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/rf9bmj
title: Model_oc_172_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/rfb7sb
title: Model_ic_59_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/rp01f1
title: Model_oc_56_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/tuhmm0
title: Model_oc_73_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/txxuyr
title: Model_oc_50_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/uryild
title: Model_oc_28_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/wyqgr5
title: Model_ic_64_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/xhn6cc
title: Model_oc_64_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/xvurec
title: Model_ic_27_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/yxnkm8
title: Model_oc_299_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/yzhyjl
title: Model_oc_5_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/z7dp0i
title: Model_oc_74_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/z9srkl
title: Model_oc_48_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/0d8rct
title: Model_oc_56_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/1y0mht
title: Model_ic_50_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/2bir1k
title: Model_oc_57_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/2gkuzt
title: Model_oc_3_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/2teivo
title: Model_oc_291_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/8wgddg
title: Model_oc_73_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/aezeu1
title: Model_oc_292_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/aieoim
title: Model_oc_175_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/aqg1pr
title: Model_ic_27_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/bars3d
title: Model_oc_220_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/de2fv0
title: Model_oc_28_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/geuq8f
title: Model_oc_91_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/gf89ez
title: Model_oc_41_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/h59qtd
title: Model_oc_1_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/hy7wqg
title: Model_oc_298_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/i5oypv
title: Model_ic_57_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/jt0bmo
title: Model_ic_36_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/kyahmr
title: Model_oc_67_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/lkawcu
title: Model_oc_9_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/mtkogf
title: Model_oc_55_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/n8ywby
title: Model_ic_44_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nqbohh
title: Model_oc_284_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nshljh
title: Model_ic_11_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nwiiaf
title: Model_oc_105_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nybwlt
title: Model_oc_38_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/okpsyx
title: Model_oc_5_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pcslum
title: Model_oc_70_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ptnh7m
title: Model_ic_36_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qcwpyr
title: Model_oc_12_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qnxjnu
title: Model_oc_56_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/szglbw
title: Model_oc_225_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ta4oyo
title: Model_ic_63_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/tvnyfx
title: Model_oc_25_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/u6fxag
title: Model_oc_11_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/vx7pzi
title: Model_ic_32_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/xgcd0f
title: Model_ic_60_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/xjasnr
title: Model_oc_19_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/zcu7us
title: Model_oc_17_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/zgvmdt
title: Model_ic_42_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/zm3us8
title: Model_ic_16_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/zqzist
title: Model_oc_36_M&A (v0=1e14).tab

description: :unav
DOI: 10.21227/zg80-0a10
title: Coronavirus (COVID-19) Geo-tagged Tweets Dataset

description: This dataset contains the IDs of geo-tagged tweets. The tweets were captured by an on-going project deployed at https://live.rlamsal.com.np. The geolocation data was extracted from the tweets which mentioned anything about “corona”, "coronavirus", "covid" and possible variants of "sarscov2", "nCov", "covid-19", "ncov2019". Complying with Twitter's content redistribution policy, only the tweet IDs are shared. You can re-construct the dataset by hydrating these IDs. The tweet IDs in this dataset belong to the tweets tweeted providing an exact location. Please note that this dataset should be solely used for non-commercial research purposes (ignore every other LICENSE category given on this page).Note: I started sharing the IDs of the tweets that contained the exact location information, only since April 28, 2020, with some genuine requests coming in from academic researchers who did not want to hydrate the whole lists of IDs (above 150+ million tweets) shared in the Coronavirus (COVID-19) Tweets Dataset.If you need the geolocation-based data starting March 20, 2020, then use the Coronavirus (COVID-19) Tweets Dataset and hydrate the IDs while adding the following condition:data = json.loads(data)if data["coordinates"]: longitude, latitude = data["coordinates"]["coordinates"]The data is available in two formats: CSV and JSON. I'll be sharing new files every day, and the files will be named period-wise. For example, april28-april29.* will contain tweet ID and sentiment data of the tweets that were tweeted between April 28, 2020, and April 29, 2020.Why are only tweet IDs being shared? It is Twitter's content redistribution policy that restricts the sharing of tweet information other than tweet IDs and/or user IDs. Twitter wants researchers to always pull fresh data using their API. Why? Here's my opinion. Maybe, some user might want to delete a particular tweet after a couple of minute(s)/hour(s)/day(s), and if the same tweet has already been pulled and is shared on a public domain, then it might make the user/community vulnerable to many inferences coming out of the shared data.
DOI: 10.7910/dvn/9argzn/2wlcgp
title: Model_oc_57_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/5stord
title: Model_ic_49_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/8ds1nf
title: Model_oc_286_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/avtoer
title: Model_oc_89_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/bg69az
title: Model_oc_86_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/bj4on1
title: Model_oc_43_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/bmhzsf
title: Model_oc_68_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/eaebtg
title: Model_oc_125_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/f7cfct
title: Model_oc_46_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/fkmy7t
title: Model_oc_16_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/fnapla
title: Model_ic_20_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/fplkbd
title: Model_oc_19_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/fwkcac
title: Model_oc_31_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/fyjzut
title: Model_oc_50_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/gvmde7
title: Model_oc_75_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/h2shda
title: Model_oc_122_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ielzlk
title: Model_ic_17_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/jetspn
title: Model_ic_44_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/jibamq
title: Model_oc_12_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/kaiyqw
title: Model_oc_84_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/l1iwhb
title: Model_oc_168_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/lnhpjg
title: Model_ic_15_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/lppjlj
title: Model_oc_99_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/lt8ric
title: Model_ic_6_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/o3qoct
title: Model_oc_100_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pg5i0d
title: Model_oc_48_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pk5frz
title: Model_oc_79_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/q2bls8
title: Model_ic_54_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qomkmg
title: Model_oc_223_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qqh0e6
title: Model_ic_32_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qzytjt
title: Model_oc_119_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/riqajz
title: Model_oc_56_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/rjxtg0
title: Model_ic_33_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/se4mkk
title: Model_ic_49_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/t2mupf
title: Model_ic_56_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/tvo5wb
title: Model_oc_260_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/un0p5v
title: Model_oc_64_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/un9pxr
title: Model_ic_63_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/uuqrfx
title: Model_oc_38_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/w1tamq
title: Model_ic_26_M&A (v0=1e13).tab

description: :unav
DOI: 10.21227/5jyx-js64
title: Intel Open Wi-Fi RTT Dataset

description: Dataset used for "A Machine Learning Approach for Wi-Fi RTT Ranging" paper (ION ITM 2019). The dataset includes almost 30,000 Wi-Fi RTT (FTM) raw channel measurements from real-life client and access points, from an office environment. This data can be used for Time of Arrival (ToA), ranging, positioning, navigation and other types of research in Wi-Fi indoor location. The zip file includes a README file, a CSV file with the dataset and several Matlab functions to help the user plot the data and demonstrate how to estimate the range. Please see the README file for more details.
DOI: 10.7910/dvn/9argzn/2dwy8e
title: Model_oc_105_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/7irplj
title: Model_oc_16_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/7swnhi
title: Model_oc_28_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ao81lr
title: Model_oc_21_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ap1p01
title: Model_ic_53_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/d7w925
title: Model_oc_79_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/e9tdfi
title: Model_oc_142_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/f8ysgd
title: Model_ic_49_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/hc7nn5
title: Model_oc_80_M&A (v0=1e12).tab

description: :unav
DOI: 10.7910/dvn/9argzn/hqqihr
title: Model_oc_31_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ibgnjg
title: Model_oc_261_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ibjiwa
title: Model_ic_45_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/lrwlbz
title: Model_oc_233_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ma5zav
title: Model_oc_59_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/mbievh
title: Model_oc_28_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/mqybre
title: Model_oc_169_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nc9rmu
title: Model_oc_84_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ndxqsi
title: Model_oc_274_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/nzgzf2
title: Model_oc_18_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pjc43m
title: Model_ic_40_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/pxrujj
title: Model_ic_13_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qjkfxj
title: Model_ic_28_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qljqcy
title: Model_ic_34_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/qt8s0a
title: Model_ic_19_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/quprzp
title: Model_ic_17_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/ra2i1c
title: Model_oc_2_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/saaag3
title: Model_oc_43_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/sorbr1
title: Model_oc_2_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/spdiuz
title: Model_oc_149_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/stu2m1
title: Model_ic_62_M&A (v0=1e13).tab

description: :unav
DOI: 10.7910/dvn/9argzn/t3qurb
title: Model_oc_169_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/vcdk2n
title: Model_oc_55_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/x2laeh
title: Model_ic_61_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/xrqxez
title: Model_oc_86_V1 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/z7kbpy
title: Model_oc_64_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/zd0dvn
title: Model_ic_27_V3 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/02qltm
title: Model_oc_30_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/1hwav6
title: Model_oc_6_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/3njgse
title: Model_oc_286_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/58ligk
title: Model_oc_89_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/5uhdxm
title: Model_oc_126_M&A (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/7beibu
title: Model_oc_49_V2 (v0=1e14).tab

description: :unav
DOI: 10.7910/dvn/9argzn/7goczx
title: Model_oc_77_V2 (v0=1e14).tab

description: :unav
DOI: 10.15156/bio/sh146278.07fu
title: SH146278.07FU

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/sh146279.07fu
title: SH146279.07FU

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/sh146280.07fu
title: SH146280.07FU

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/sh146281.07fu
title: SH146281.07FU

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/sh146282.07fu
title: SH146282.07FU

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/sh146283.07fu
title: SH146283.07FU

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/sh146284.07fu
title: SH146284.07FU

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.