Skip to main content
ConductScienceScienceDex
Powered by ShareScore

Find research datasets worth reusing

Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.

142

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

142 results for “text data”

Learn how ShareScore rates datasets ↗
zenodo52/100

Invasion Biology WikiProject Scientific Papers: Text Data Mining and LLM-based Information Extraction of Species, Locations, Habitats, and Ecosystems

<p>This dataset contains the abstract and full-text for publication DOIs from the Invasion Biology WikiProject (DOI:&nbsp;<a href="https://www.doi.org/10.5281/zenodo.12518036">10.5281/zenodo.12518036</a>). The data was retrieved using the <a href="https://ask.orkg.org/">ask.orkg.org</a> <a href="https://api.ask.orkg.org/docs#tag/Semantic-Neural-Search/operation/explore_documents_index_explore_get">API</a>. For the <a href="https://github.com/jd-coderepos/invasion-biology-IE/blob/main/scripts/ask-doi-list-fulltext-search.py">script</a> used to obtain the data, refer to the accompanying GitHub repository: <a href="https://github.com/jd-coderepos/invasion-biology-IE/" target="_blank" rel="noopener">https://github.com/jd-coderepos/invasion-biology-IE/</a>.</p> <p>The resulting CSV file includes the following fields: <code>"ASK ID"</code>, <code>"DOI"</code>, <code>"Title"</code>, <code>"Abstract"</code>, and <code>"Full-text"</code>.</p> <p>Of the 49,438 queried DOIs, the ASK database provided:</p> <ul> <li><strong>Total DOIs processed:</strong> 12,636</li> <li><strong>DOIs with neither abstract nor full-text:</strong> 36 (abstract token count was less than 10)</li> <li><strong>DOIs with abstracts but no full-text:</strong> 12,636</li> <li><strong>DOIs with both abstract and full-text:</strong> 2,834</li> </ul> <p>The second part of the dataset contains structured information extracted from the publications using the GPT-4o Large Language Model. This structured data is included in the zipped folder <code>structured-publications.zip</code>.</p> <p>The accompanying GitHub repository provides access to the code and scripts used at various stages of the information extraction (IE) process.</p> <p><strong>Theme of the Study:</strong><br>"Mining for Species, Locations, Habitats, and Ecosystems from Scientific Papers in Invasion Biology: A Large-Scale Exploratory Study with Large Language Models."</p>

opencc-by-4.0Oct 2024View details →
zenodo48/100

Data and analysis script for "The (non)effect of personalization in climate texts on credibility of climate scientists: A case study on sustainable travel"

<p>Dataset and analysis script for the article "<strong>The (non)effect of personalization in climate texts on credibility of climate scientists</strong><strong>: A case study on sustainable travel</strong>", under review at Geoscience Communication (https://doi.org/10.5194/egusphere-2024-543)</p>

opencc-by-4.0Jun 2024View details →
zenodo48/100

Data set for (binary) text classification, involving spoken utterances and written text

<p>This data set contains sentences belonging to either of two classes: Transcripts of spoken<br> (informal) text (Class 0), and written, formal text (Class 1). Sentences in Class 0 were<br> obtained from publicly available transcripts of radio shows (e.g. NPR),<br> whereas Sentences in Class 1 were obtained from Wikipedia.</p> <p>The data set is divided into&nbsp;three subsets: Training, validation, and test (specified&nbsp;by the file names).<br> Each set contains a large number of sentences, belonging to either of the two classes:</p> <p>In total, there are 13,640,458 sentences, of which 6,374,487 in Class 0 and 7,265,971.<br> The training set contains 9.743,188 sentences (of which 4,553,205 in Class 0 and 5,189,983 in Class 1),&nbsp;<br> the validation set contains 1,948,639 sentences (of which 910,641 in Class 0 and 1,037,998 in Class 1), and the&nbsp;<br> test set contains 1,948,631 sentences (of which 910,641 in Class0 and 1,037,990 in Class1).&nbsp;</p> <p>The data sets are in plain text format. Every row contains (i) the class label (0 or 1) and<br> (ii) the text of the sentence, separated from the class label by a tab character.</p> <p>Note that the&nbsp;sentences contain 5 tokens or more (including punctuation marks).&nbsp;&nbsp;</p>

opencc-by-4.0Mar 2023View details →
zenodo44/100

Data_text section_ 11βHSD1_11β-Hydroxysteroid dehydrogenases control access of 7β,27-dihydroxycholesterol to retinoid-related orphan receptor γ

<p>Data from kinetic characterization (Km and vmaxapp) described in text section 3.1 of 11&beta;-Hydroxysteroid dehydrogenases control access of 7&beta;,27-dihydroxycholesterol to retinoid-related orphan receptor &gamma;</p> <p>Dataset (doi:10.1194/jlr.M092908) contains values from kinetic characterization (Km and vmaxapp) described in text section&nbsp;(Kinetic values_11&beta;HSD1.PNG)&nbsp;corresponding to raw data obtained from LC-MS/MS analysis provided as three files in CSV format (31003A-179400_DATE_KB_27Oxysterol_4_6_1-3). All further experiment related information and subsequent data analysis provided as two meta-data-files (31003A-179400_DATE_KB_27Oxysterol_4_6_M_1-2) as TXT format and PDF format.</p>

opencc-by-4.0Jul 2019View details →
zenodo44/100

Connecting U.S. Supreme Court Case Information and Opinion Authorship (SCDB) to Full Case Text Data (CAP), 1791-2011

<p>This dataset was constructed to connect the rich metadata created by the Supreme Court Database (SCDB) to the Caselaw Access Project (CAP) full-text court opinion data. Since the SCDB includes only substantive opinions, it is necessarily a subset of the full range of opinions available through CAP.</p> <p>There are two parts to this data: the map connecting each SCDB ID to its corresponding CAP case number, and a more advanced (but error-prone) version in which the authorship of each opinion text identified for the case in CAP is attributed to the Justice who wrote it. Each of these data products have been hand-corrected to the best of this author&#39;s ability.</p> <p><strong>SCDB-CAP map</strong></p> <p>The SCDB-&gt;CAP map began as a relatively straightforward automated matching process, based on the US Reports citation for each case as expressed in both SCDB and CAP. Slightly over 80% of SCDB entries found a single CAP data match this way. From there, the data was entirely hand-corrected, with non-matches or duplicate matches individually investigated and manually corrected.</p> <p>Some SCDB entries simply could not be matched to an appropriate CAP text. Initially, the entirety of US Reports volume 44 was missing, but with the help of CAP staff, the volume was located as having been filed in the New York jurisdiction rather that the United States jurisdiction. The case numbers were then added to the map, but until the volume is relocated to the United States jurisdiction, it may be necessary to also incorporate the New York jurisdiction in full text analysis so that the cases from volume 44 can be searched. 108 more missing cases are from US Reports volume 131, which was a &quot;catch up&quot; volume published in the 19th century. These catch-up cases, many heard by the Supreme Court decades prior, were numbered with lowercase roman numerals instead of the ordinary&nbsp; numbers, which is almost certainly why CAP&#39;s software dismissed the catch-up section as prefatory material. Many of the rest of the errors seem largely to be examples where the SCDB project recognized a separate court action that CAP did not. Perhaps most of these seem to have been later rehearings for a case previously decided, which in the 19th century particularly were commonly reported out at the end of the first decision text. While SCDB sometimes gave these subsequent but related actions a separate SCDB entry, CAP seems to have largely incorporated them as part of the text of the main case. Additionally, there were a few that simply could not be found, despite a careful look through each database as well as the original US Reports and sometimes adjacent volumes. Finally, the cases were only matched up through the 2011 court term. After the 2011 term, the mismatches between CAP and SCDB were extensive and frequently seemed impossible to resolve.</p> <p>Even so, with the manual correction, the overall error rate is low. Of 28,304 cases, only 191 do not have a match, and of those, 108 are contained within the vol. 131 &quot;catch up&quot; volume. Since most of the rest are extremely short subsequent actions that were separately noted by SCDB, the effect of these non-matched cases would seem to be small in most cases.</p> <p>The typical use case would be that the researcher would generate some kind of results based on searching in the CAP full text, then could use the CAP ID to look up the SCDB ID in the map. With the SCDB ID, of course, the rich metadata from the SCDB can then be connected to each result as needed.</p> <p><strong>Opinion authorship</strong></p> <p>Being able to use the rich metadata of SCDB in conjunction with a case&#39;s full text is exciting, but it immediately prompts a further question -- what if the texts could be attributed directly to the Justices who authored them? SCDB produces its data in two forms; one is &quot;case centered,&quot; where each record represents one case, and the other is &quot;justice centered,&quot; in which each record is the vote of one Justice in one case. CAP, in turn, breaks the total text of the case into distinct opinions, and tries to attribute those opinions to their authors by scraping a string of text from the raw input. Therefore, the challenge was to connect these two sources at the opinion level.</p> <p>Connecting the opinions, like connecting the cases, involved an initial match by machines, followed by manual correction and revision. In this case, the scope of the manual effort was much larger than that posed by the case-level connection, and more errors were noted in both SCDB and CAP.</p> <p>The matching process involved a number of steps. First a list of opinions was generated from the CAP data, then matched to SCDB using the SCDB-CAP connector data described above. (Thus, a case without a CAP match in the SCDB-CAP data will not appear in the opinion author data either.) CAP opinions were numbered in the order they were encountered in each CAP case JSON object, and these numbers are used to distinguish the opinions.</p> <p>Next, a round of automatic matching was performed. If there was only one opinion, and only one author listed in the SCDB data, then the majority opinion author (as listed in SCDB) was safely assumed to be the author. If there was no author listed in SCDB, &quot;percuriam&quot; was recorded as the author in this data. If there were exactly two opinions and two authors, the process was also straightforward, as the SCDB-identified majority opinion author was assigned to opinion 1, and the remaining author assigned opinion 2.</p> <p>Subsequently, cases with more than two opinions were processed. A potential match (i.e. a &quot;guess&quot;) for each opinion in a given case was created by listing each Justice identified by SCDB as having written an opinion in the case. These guesses were then parsed using a semi-automatic procedure with Levenshtein distance fuzzy name matching. With sufficiently conservative parameters, a successful fuzzy match meant that the non-successful guesses for that opinion could be deleted. These sorted guesses were then reviewed manually. Particular care was also taken for any opinion that contained authored opinions by Justices who had similar names (for example, Clark and Black differ by only a single letter). These sorts of cases, as well as instances of co-authorship, were identified and fixed manually.</p> <p>Those opinions whose authorship could not be matched then were fixed by hand. These included some where the CAP author strings were more complicated than SCDB&#39;s strict interpretation; others where the OCR in CAP which contained the Justice name was especially bad; and a number of others where &quot;Mr. Chief Justice&quot; couldn&#39;t be directly matched with an author name by the machine. After this light manual correction, almost 500 opinions with substantial errors remained to be individually investigated in depth, by examining the CAP record, the SCDB record, and images of the US Reports for that case. For these last tough customers, errors in the source data were commonly the cause of matching problems. Typically these were of three kinds: examples where CAP should have split the text but didn&#39;t (e.g. 2 opinions together in one opinion entry in CAP); examples where SCDB either did not identify or mis-identified an author (such as attributing it to Swayne when it was written by Miller); and examples of non-valid opinions (such as where CAP mistakenly split the opinion too early, leaving an opinion fragment).</p> <p>For these errors, a system of codes was created in the author field to signal the error type so that researchers can be suitably cautious. The error code is always at the beginning of the field and is followed by a comma and the names of each author, separated by a comma with no space to facilitate parsing. Note also that co-authors are listed as comma-separated names in this same field with no error code. Researchers will probably want to disaggregate this field to create duplicate records with each individual author for most purposes. The justice number field also contains information about all justices authoring the opinion but the error codes have been omitted here.</p> <ul> <li>!C -- error: multiple opinion texts combined (i.e. CAP splitting error)</li> <li>!X -- error: unattributed or misattributed opinion (not listed in SCDB as writer)</li> <li>!D -- error: extra opinion that should be deleted, i.e. not a valid opinion</li> <li>!W -- error: listed as Writers by SCDB, but should be co-authors</li> </ul> <p>&nbsp;</p> <p><strong>Data file structure</strong></p> <p>&quot;scdb_cap-051820.tsv&quot; is a Tab-separated data file containing 5 columns: SCDB ID, CAP ID, US Reports citation, case date, and case name (the latter three from the SCDB data).</p> <p>&quot;scdb-cap-opinion-authorship_051920.tsv&quot; is a Tab-separated data file containing seven columns: SCDB ID, CAP ID, US Reports citation, case name, opinion number in the case, opinion author, and SCDB justice ID. See above for caveats about disaggregating and error codes in fields six and seven.</p> <p><strong>Errors</strong></p> <p>It is likely that errors remain in this data, and it is also hoped that some of the errors beyond the author&#39;s immediate control might be fixed in the upstream data so that they can be corrected here. Authors would be grateful for error reports, and also reports of errors fixed, if any.</p> <p>&nbsp;</p>

opencc-by-4.0Dec 2020View details →
zenodo44/100

WOLOF TTS(Text To Speech) Data

<p>This contains&nbsp;a WOLOF Text To Speech(TTS) dataset, it contains recordings from two natif Wolof actos (a male and female voice).<br> Each actor recored more than 20 000 sentences.<br> The notebook accompanying the dataset contains a brief analysis of the dataset and the code creating the appropriate train/validation and test set.<br> The file [male, female]train, [male, female]validation and [male, female]test are also present to extract the corespondig audios inside the data-commonvoice.zip</p> <p>The text dataset come from news website, Wikipedia and self curated text. We made sure with the help of our Wolof expert that the text dataset cover the different phonemes in the Wolof language.</p>

opencc-by-4.0Feb 2021View details →
zenodo44/100

Publication text: code, data, and new measures

<p>This Zenodo page describes data collection, processing, and different open access data files related to the text of scientific publications from OpenAlex. If you use the code or data, please cite the following paper:&nbsp;</p> <p>Sam Arts, Nicola Melluso, Reinhilde Veugelers; Beyond Citations: Measuring Novel Scientific Ideas and their Impact in Publication Text. <em>The Review of Economics and Statistics</em> 2025; 1&ndash;33 doi: <a href="https://doi.org/10.1162/rest_a_01561" target="_blank" rel="noopener">https://doi.org/10.1162/rest_a_01561</a></p> <p>&nbsp;</p>

openo-uda-1.0Oct 2024View details →
zenodo44/100

Ground-Truthed Data Set of Zenon Papyri for Handwritten Text Recognition

<p>Diplomatic transcription of papyri found in the Zenon archive [see <a href="https://en.wikipedia.org/wiki/Zenon_of_Kaunos">en.wikipedia.org/wiki/Zenon_of_Kaunos</a>]</p> <p>Manually prepared as PageXML with Transkribus within <a href="http://d-scribes.philhist.unibas.ch/">D-Scribes</a> project.</p> <p>&nbsp;</p>

opencc-by-4.0May 2022View details →
zenodo44/100

XML Data for "Four Early Chan Texts from Dunhuang - A TEI-based Edition"

<p>This zip archive contains the XML data, schema,&nbsp;stylesheets, and associated material that are&nbsp;the basis for a print&nbsp;edition of 48 Dunhuang manuscript witnesses of four early Chan Buddhist texts. The print edition is:</p> <p>Marcus Bingenheimer 馬德偉, Chang Po-Yung 張伯雍 (eds.):&nbsp;<em>Four Early Chan Texts from Dunhuang &ndash; A TEI-based Edition</em>&nbsp;早期禪宗文獻四部 &mdash;&mdash; 以TEI標記重訂敦煌寫卷:楞伽師資記,傳法寶紀,修心要論,觀心論. Taipei: Shin Wen Feng 新文豐, 2018.<br> (Vol. 1: Facsimiles and Diplomatic Transcription 摹寫版 (ISBN: 978-957-17-2274-0), Vol. 2: Parallel, Punctuated and Annotated Edition 對照與點注版 (ISBN: 978-957-17-2275-7), Vol. 3: Calligraphy Practice 抄經版 (ISBN: &nbsp;978-957-17-2276-4).)</p> <p>See the included README.txt for further information.</p>

opencc-by-4.0Dec 2017View details →
zenodo44/100

POLIcy design ANNotAtions (POLIANNA): Towards understanding policy design through text-as-data approaches

<p>The POLIANNA dataset is a collection of legislative texts from the European Union (EU) that have been annotated based on theoretical concepts of policy design. The dataset consists of 20,577 annotated spans in 412 articles, drawn from 18 EU climate change mitigation and renewable energy laws, and can be used to develop supervised machine learning approaches for scaling policy analysis. The dataset includes a novel coding scheme for annotating text spans, and you find a description of the annotated corpus, an analysis of inter-annotator agreement, and a discussion of potential applications in the paper accompanying this dataset. The objective of this dataset to build tools that assist with manual coding of policy texts by automatically identifying relevant paragraphs.</p> <p>Detailed instructions and further guidance about the dataset as well as all the code used for this project can be found in the accompanying <a href="https://doi.org/10.1038/s41597-023-02801-z">paper</a> and on the&nbsp;<a href="https://github.com/kueddelmaier/POLIANNA">GitHub project page</a>. The repository also contains useful code to calculate various inter-annotator agreement measures and can be used to process text annotations generated by&nbsp;<a href="https://inception-project.github.io/">INCEpTION</a>.</p> <p>&nbsp;</p> <p><strong>Dataset Description</strong></p> <p>We provide the dataset in 3 different formats:<br><br><em>JSON: </em>Each article corresponds to a folder, where the Tokens and Spans are stored in a separate JSON file. Each article-folder further contains the raw policy-text as in a text file and the metadata about the policy. This is the most human-readable format.</p> <p><em>JSONL: </em>Same folder structure as the JSON format, but the Spans and Tokens are stored in a <a href="https://jsonlines.org/">JSONL</a> file, where each line is a valid JSON document.</p> <p><em>Pickle: </em>We provide the&nbsp;dataset as a Python object. This is the recommended method when using our own Python framework that is provided on GitHub. For more information, check out the GitHub project page.</p> <p><br><strong>License</strong></p> <p>The POLIANNA dataset is licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license.&nbsp;If you use the POLIANNA dataset in your research in any form, please cite the dataset.</p> <p>&nbsp;</p> <p><strong>Citation</strong></p> <p>Sewerin, S., Kaack, L.H., K&uuml;ttel, J. <em>et al.</em> Towards understanding policy design through text-as-data approaches: The policy design annotations (POLIANNA) dataset. <em>Sci Data</em><strong>10</strong>, 896 (2023). https://doi.org/10.1038/s41597-023-02801-z</p>

opencc-by-4.0Jan 2023View details →
zenodo40/100

Data_text section 3.3_Enzymatic interconversion of the oxysterols 7β,25 dihydroxycholesterol and 7-keto,25-hydroxycholesterol by 11β-hydroxysteroid dehydrogenase type 1 and 2

<p>Data from kinetic characterization (Km and vmaxapp) described in text section 3.3 of Enzymatic interconversion of the oxysterols 7&beta;,25 dihydroxycholesterol and 7-keto,25-hydroxycholesterol by 11&beta;-hydroxysteroid dehydrogenase type 1 and 2</p> <p>Dataset (doi:<a href="https://doi.org/10.1016/j.jsbmb.2019.03.011">10.1016/j.jsbmb.2019.03.011</a>) contains values from kinetic characterization (10.1016_j.jsbmb.2019.03.011_text3.3_Km_vmax) described in text section 3.3 corresponding to raw data obtained from LC-MS/MS analysis provided as three files in CSV format (31003A-179400_date_name_25Oxysterol_4_10_1-3). All further experiment related information and subsequent data analysis provided as two meta-data-files: (31003A-179400_date_name_25Oxysterol_4_9_M_1-2) as TXT and pdf format.</p>

opencc-by-4.0Mar 2019View details →
zenodo40/100

Patent text: code, data, and new measures

<p>This Zenodo page describes data collection, processing, and different open access data files related to the text of USPTO patent documents. The document &quot;Data Description Zenodo.pdf&quot;&nbsp;provides more details.&nbsp;If you use the code or data, please cite the following paper:</p> <p>Arts&nbsp;S, Hou&nbsp;J,&nbsp;Gomez&nbsp;JC&nbsp;(2021). Natural language processing to identify the creation and impact of new technologies in patent text: Code, data, and new measures. <em>Research Policy</em>, 50(2), 104144.&nbsp;(<a href="https://doi.org/10.1016/j.respol.2020.104144">https://doi.org/10.1016/j.respol.2020.104144</a>)</p>

opencc-by-nc-1.0Nov 2020View details →
zenodo40/100

Ancient Greek Literature for Advanced Data Processing: A Text Fabric Representation of Open Access Texts in TEI XML

<p>This data set contains a full conversion of Greek texts available in the Perseus Digital Library and the Open Greek and Latin Project to the Text Fabric data format. The main advantage of the Text Fabric datatype over the original TEI XML format is that it utilizes a strict separation of text and annotation in a flat data structure. At the same time, it permits multiple distinct formats of the same text as well as an unlimited depth of (embedded) annotations. Because of its flat data structure, it facilitates easy and clean procedures to analyze, transform, and enrich the available data. Many of these processes are very difficult to conduct while departing from the hierarchically organized XML tree representation.</p>

opencc-by-4.0Dec 2020View details →
zenodo40/100

Data set on the main text of "A bright and fast source of coherent single photons"

<p>The data set that is presented in the main text is uploaded to the repository. Please note that all the data is scaled according to the axis on the paper, that means if the axis has a multiplication by 1e3 then the data is divided by 1e3.</p> <p>Each file is named after the corresponding subfigure.</p> <p>The preprint version of the article can be found in: https://arxiv.org/abs/2007.12654</p>

opencc-by-4.0Dec 2020View details →
zenodo40/100

Umfrageergebnisse "Bedarf und Anforderungen an Ressourcen für Text und Data Mining"

<p>Daten der Umfrage &quot;Bedarf und Anforderungen an Ressourcen f&uuml;r Text und Data Mining&quot; der Schwerpunktinitiative &quot;Digitale Information&quot; der Allianz der deutschen Wissenschaftsorganisationen, Arbeitsgruppe Text und Data Mining, vom Mai 2015</p>

opencc-zeroOct 2015View details →
zenodo40/100

Text data for keyboard layout evaluation

<div> <h1>Text data</h1> <a href="https://github.com/binarybottle/text_data#text-data"></a></div> <table> <tbody><tr> <th>Text source</th> <th>Information</th> </tr> </tbody><tbody> <tr> <td>"Alice in Wonderland"</td> <td>Alice in Wonderland (Ch.1)</td> </tr> <tr> <td>"Romeo and Juliet"</td> <td><a href="https://www.fulltextarchive.com/page/Romeo-and-Juliet1/" rel="nofollow">Romeo and Juliet</a></td> </tr> <tr> <td>"Bhagavad Gita"</td> <td><a href="https://www.gutenberg.org/files/2388/2388-h/2388-h.htm" rel="nofollow">Bhagavad Gita</a></td> </tr> <tr> <td>"Memento screenplay"</td> <td><a href="https://www.dailyscript.com/scripts/memento.html" rel="nofollow">Memento screenplay</a></td> </tr> <tr> <td>"100K tweets"</td> <td>100,000 tweets from:&nbsp;<a href="https://data.world/data-society/twitter-user-data" rel="nofollow">Sentiment140 dataset</a>&nbsp;training data</td> </tr> <tr> <td>"20K tweets"</td> <td>20,000 tweets from&nbsp;<a href="https://www.kaggle.com/crowdflower/twitter-user-gender-classification" rel="nofollow">Gender Classifier Data</a></td> </tr> <tr> <td>"MASC tweets"</td> <td><a href="http://www.anc.org/data/masc/corpus/" rel="nofollow">MASC</a>&nbsp;tweets (cleaned of html markup)</td> </tr> <tr> <td>"MASC spoken"</td> <td><a href="http://www.anc.org/data/masc/corpus/" rel="nofollow">MASC</a>&nbsp;spoken transcripts (phone and face-to-face: 25,783 words)</td> </tr> <tr> <td>"COCA blogs"</td> <td><a href="https://www.english-corpora.org/coca/" rel="nofollow">Corpus of Contemporary American English</a>&nbsp;<a href="https://www.corpusdata.org/" rel="nofollow">blog samples</a></td> </tr> <tr> <td>"Google website"</td> <td><a href="https://google.com/" rel="nofollow">Google homepage</a>&nbsp;(accessed 10/20/2020)</td> </tr> <tr> <td>"Software languages"</td> <td>"Tower of Hanoi" (programming languages A-Z from&nbsp;<a href="https://rosettacode.org/wiki/Towers_of_Hanoi" rel="nofollow">Rosetta Code</a>)</td> </tr> <tr> <td>"Monkey text"</td> <td>Ian Douglas's English-generated&nbsp;<a href="../record/4642460" rel="nofollow">monkey0-7.txt corpus</a></td> </tr> <tr> <td>"Coder text"</td> <td>Ian Douglas's software-generated&nbsp;<a href="../record/4642460" rel="nofollow">coder0-7.txt corpus</a></td> </tr> <tr> <td>"iweb cleaned corpus"</td> <td>First 150,000 lines of Shai Coleman's&nbsp;<a href="https://colemak.com/pub/corpus/iweb-corpus-samples-cleaned.txt.xz" rel="nofollow">iweb-corpus-samples-cleaned.txt</a></td> </tr> </tbody> </table> <p>Reference for Monkey and Coder texts: Douglas, Ian. (2021, March 28). Keyboard Layout Analysis: Creating the Corpus, Bigram Chains, and Shakespeare's Monkeys (Version 1.0.0). Zenodo.&nbsp;<a href="http://doi.org/10.5281/zenodo.4642460" rel="nofollow">http://doi.org/10.5281/zenodo.4642460</a></p>

opencc-by-4.0May 2021View details →
zenodo40/100

Text-fig. 8. Bivariate diagram of length and width of the lower dentition (m1 and m2) of Pseudarctos, Ictiocyon and Dehmicyon species. a: m2; b: m1; c: length m1 and m2. Data from Schlosser (1904), Helbing (1937), Thenius (1949), Dehm (1950), Crusafont et al. (1950), Ginsburg (1992). Abbreviations: L – length; W – width; Ba – Baigneaux; LRM – Pellecahus. in The Amphicyoninae (Amphicyonidae, Carnivora, Mammalia) Of The Early Miocene From Tuchořice, The Czech Republic

Text-fig. 8. Bivariate diagram of length and width of the lower dentition (m1 and m2) of Pseudarctos, Ictiocyon and Dehmicyon species. a: m2; b: m1; c: length m1 and m2. Data from Schlosser (1904), Helbing (1937), Thenius (1949), Dehm (1950), Crusafont et al. (1950), Ginsburg (1992). Abbreviations: L – length; W – width; Ba – Baigneaux; LRM – Pellecahus.

opencc-by-4.0Dec 2021View details →
zenodo40/100

Text-fig. 1. Bivariate diagram of length and width of the upper dentition of selected European small and middle size Amphicyoninae compared with the Tuchořice specimens. a: P4; b: M1; c: M2; d: m1; e: m2. Data from Schlosser (1899, 1904), Thenius (1949), Dehm (1950), Heizmann (1973), Ginsburg (1977, 1989), Peigné (2012). Dotted line – ranges of maximum and minimum values from the average of teeth of Cynelos lemanensis from Ulm (Peigné and Heizmann 2003). Abbreviations: L – length; W – width. in The Amphicyoninae (Amphicyonidae, Carnivora, Mammalia) Of The Early Miocene From Tuchořice, The Czech Republic

Text-fig. 1. Bivariate diagram of length and width of the upper dentition of selected European small and middle size Amphicyoninae compared with the Tuchořice specimens. a: P4; b: M1; c: M2; d: m1; e: m2. Data from Schlosser (1899, 1904), Thenius (1949), Dehm (1950), Heizmann (1973), Ginsburg (1977, 1989), Peigné (2012). Dotted line – ranges of maximum and minimum values from the average of teeth of Cynelos lemanensis from Ulm (Peigné and Heizmann 2003). Abbreviations: L – length; W – width.

opencc-by-4.0Dec 2021View details →
zenodo40/100

Text-fig. 10. Langtonia bisulcata REID et CHANDLER. a, b, e–g: Holotype, V. 22984, from micro-CT data. a: Dorsiventral view surface rendering. b: Dorsiventral view translucent volume rendering showing outline of locule cast. c: Equatorial transverse fracture showing paired dorsal infolds and locules with shape of a ε in cross section, reflected light, V. 22993. d: Digital transverse section from micro-CT data, of fruit with two well developed ε-shaped locules, V. 22985. e–g: Successive digital transverse sections with one well developed ε-shaped locule and infolds of the abortive locule visible in (g) (arrows). h–j: Physical transverse thin sections of specimen from middle Eocene Clarno Formation, Oregon, USA with well-preserved mesocarp including longitudinal canals in (j) (arrows), USNM 424875; Scale bars 0.5 cm in (a, b), 2.5 mm in (c–g), 5 mm in (h), 2 mm in (i), 1 mm in (j); (a, b) share same scale bar; (c, d) share same scale bar; (e, f, g) share same scale bar. in Mastixioid Fruits (Cornales) From The Early Eocene London Clay Flora: Morphology, Anatomy And Nomenclatural Revision

Text-fig. 10. Langtonia bisulcata REID et CHANDLER. a, b, e–g: Holotype, V. 22984, from micro-CT data. a: Dorsiventral view surface rendering. b: Dorsiventral view translucent volume rendering showing outline of locule cast. c: Equatorial transverse fracture showing paired dorsal infolds and locules with shape of a ε in cross section, reflected light, V. 22993. d: Digital transverse section from micro-CT data, of fruit with two well developed ε-shaped locules, V. 22985. e–g: Successive digital transverse sections with one well developed ε-shaped locule and infolds of the abortive locule visible in (g) (arrows). h–j: Physical transverse thin sections of specimen from middle Eocene Clarno Formation, Oregon, USA with well-preserved mesocarp including longitudinal canals in (j) (arrows), USNM 424875; Scale bars 0.5 cm in (a, b), 2.5 mm in (c–g), 5 mm in (h), 2 mm in (i), 1 mm in (j); (a, b) share same scale bar; (c, d) share same scale bar; (e, f, g) share same scale bar.

opencc-by-4.0Aug 2022View details →
zenodo40/100

Text-fig. 9. Portnallia. a–j: P. bognorensis M.CHANDLER. a–g: Holotype, V. 30421. a: Oblique lateral view with dorsal surface of locule cast facing towards right side. b: Basal view (original illustration from pl. 28, fig. 40 of Chandler 1961). c–g: Micro CT data. c–f: Surface renderings. c: Lateral view with interlocular septum facing forward. d: lateral view with dorsal surface of locule facing forward. e: Basal view. f: Apical view. g: Digital transverse section near equatorial position showing (c) to u-shaped locules. h: Apical view of tetralocular fruit, V. 30423 (original illustration from pl. 28, fig. 42 of Chandler 1961). i: Transverse section of specimen in (h), reflected light. j–o: P. sheppeyensis M.CHANDLER, Holotype V. 30428, here synomomized with P. bognorensis, from micro-CT data. j–m: Surface renderings. j: Lateral view with interlocular septum facing forward. k: Lateral view with dorsal surface of locule facing forward. l: Basal view. m: Apical view. n: Digital equatorial transverse section showing the three preserved locules and extensive cracking due to pyrite decomposition. o: Translucent volume rendering, apical view showing (c) to u-shaped locules. Scale bars 2 mm, bar in (a) applies also to (b), bar in (e) applies to also to (c, d), bar in (g) applies also to (f), bar in (j) applies to applies also to (k–m). in Mastixioid Fruits (Cornales) From The Early Eocene London Clay Flora: Morphology, Anatomy And Nomenclatural Revision

Text-fig. 9. Portnallia. a–j: P. bognorensis M.CHANDLER. a–g: Holotype, V. 30421. a: Oblique lateral view with dorsal surface of locule cast facing towards right side. b: Basal view (original illustration from pl. 28, fig. 40 of Chandler 1961). c–g: Micro CT data. c–f: Surface renderings. c: Lateral view with interlocular septum facing forward. d: lateral view with dorsal surface of locule facing forward. e: Basal view. f: Apical view. g: Digital transverse section near equatorial position showing (c) to u-shaped locules. h: Apical view of tetralocular fruit, V. 30423 (original illustration from pl. 28, fig. 42 of Chandler 1961). i: Transverse section of specimen in (h), reflected light. j–o: P. sheppeyensis M.CHANDLER, Holotype V. 30428, here synomomized with P. bognorensis, from micro-CT data. j–m: Surface renderings. j: Lateral view with interlocular septum facing forward. k: Lateral view with dorsal surface of locule facing forward. l: Basal view. m: Apical view. n: Digital equatorial transverse section showing the three preserved locules and extensive cracking due to pyrite decomposition. o: Translucent volume rendering, apical view showing (c) to u-shaped locules. Scale bars 2 mm, bar in (a) applies also to (b), bar in (e) applies to also to (c, d), bar in (g) applies also to (f), bar in (j) applies to applies also to (k–m).

opencc-by-4.0Aug 2022View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated datasets

Allen Brain Atlas

Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

Annotated Behaviour and Observability Dataset (ABODe)

ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

DANDI Archive for NWB datasets

DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

International Brain Laboratory public data

The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

OpenNeuro

OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.