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.
32
datasets available to search
ShareScore release 0.9.0
Dataset results
32 results for “biomedical dataset”
Workflow for detecting biomedical articles with openly available underlying datasets - Datasets and extraction forms
<p>The open data screening datasets contain both automatically detected (TRUE) Open Data statements by <a href="https://github.com/quest-bih/oddpub">ODDPub</a>, and its manual validation using <a href="https://github.com/bgcarlisle/Numbat">Numbat</a> extraction tool. Furthermore, extraction forms for both screenings – 2020 and 2021 – are included. The manually processed dataset for the calculation of the inter-rater reliability of manual validation can be also found here. </p> <p>(i) Data from articles published in 2020 (file ‘<em>charite_open_data_2020.csv</em>’) have been collected applying a slightly different sequence of questions in the extraction workflow than the articles published in 2021 (file ‘<em>charite_open_data_2021.csv</em>’). Both datasets were cleaned for any personal data or internal comments. Thus, they do not contain the default columns which in the raw export from Numbat contained commentaries regarding different question. Also, in another regard these files do not represent raw outputs of the Numbat extraction tool, but a processed version. This means that articles validated by more than two raters were first reconciled in Numbat, resulting in one final decision (output of extractions <strong>after reconciliation</strong>). Then from the output of extractions <strong>before reconciliation</strong> those articles validated by only 1 rater (and thus not part of the inter-rater reliability calculation) were selected, which were afterwards joined with the already reconciled dataset. </p> <p>The actual decision about Openness of validated dataset can be analysed in various ways: </p> <ol> <li>Column ‘<em>open_data_assessment</em>’/’<em>assessment</em>’ shows a binary decision between Open Data TRUE and FALSE. </li> <li>If that column indicates ‘<em>NULL</em>’, the dataset was classified into ‘non’-open category, and the result can be found on one of the following ways: <ul> <li>Column ‘<em>reference_to_data</em>’ as ‘<em>n_a</em>’ for excluded articles, e.g. not producing any data.</li> <li>Column ‘<em>data_access</em>’ as ‘<em>restricted</em>’. </li> <li>Column ‘<em>own_or_reuse_data</em>’ as ‘<em>open_data_reuse</em>’. </li> </ul> </li> </ol> <p>The original extraction form contains an option ‘unsure_open_data’ besides ‘<em>open_data</em>’/’<em>no_open_data</em>’ which was resolved either during reconciliation between multiple raters or by case-related consultation with a second rater in case of doubt, and is not included here. </p> <p>(ii) The inter-rater reliability calculation was made on randomly selected 100 articles for 2 raters. The third rater screened 20 articles sample, which is part of 100 sample. The tables provided here include both article-level data, and dataset-level data. </p> <p>(iii) The Numbat extarction forms used for the screenings in 2020 and 2021 are included in two formats - JSON and Markdown.</p> <p>(iv) ‘<em>data_dictionary_open_data.csv</em>’ table documents all variables of each data file containing here. </p>
[MedMNIST+] 18x Standardized Datasets for 2D and 3D Biomedical Image Classification with Multiple Size Options: 28 (MNIST-Like), 64, 128, and 224
<h2><strong>Code</strong> [<a href="https://github.com/MedMNIST/MedMNIST" target="_blank" rel="noopener">GitHub</a>] | <strong>Publication</strong> [<a href="https://doi.org/10.1038/s41597-022-01721-8" target="_blank" rel="noopener">Nature Scientific Data'23</a> / <a href="https://doi.org/10.1109/ISBI48211.2021.9434062" target="_blank" rel="noopener">ISBI'21</a>] | <strong>Preprint</strong> [<a href="https://arxiv.org/abs/2110.14795" target="_blank" rel="noopener">arXiv</a>]</h2> <p> </p> <p><strong>Abstract</strong></p> <p>We introduce MedMNIST, a large-scale MNIST-like collection of standardized biomedical images, including 12 datasets for 2D and 6 datasets for 3D. All images are pre-processed into 28x28 (2D) or 28x28x28 (3D) with the corresponding classification labels, so that no background knowledge is required for users. Covering primary data modalities in biomedical images, MedMNIST is designed to perform classification on lightweight 2D and 3D images with various data scales (from 100 to 100,000) and diverse tasks (binary/multi-class, ordinal regression and multi-label). The resulting dataset, consisting of approximately 708K 2D images and 10K 3D images in total, could support numerous research and educational purposes in biomedical image analysis, computer vision and machine learning. We benchmark several baseline methods on MedMNIST, including 2D / 3D neural networks and open-source / commercial AutoML tools. The data and code are publicly available at <a href="https://medmnist.com/">https://medmnist.com/</a>.</p> <p><em><strong>Disclaimer</strong></em>: The only official distribution link for the MedMNIST dataset is <a href="https://doi.org/10.5281/zenodo.10519652">Zenodo</a>. We kindly request users to refer to this original dataset link for accurate and up-to-date data.</p> <p><strong><em>Update</em>:</strong> We are thrilled to release <a href="https://github.com/MedMNIST/MedMNIST/blob/main/on_medmnist_plus.md">MedMNIST+</a> with larger sizes: 64x64, 128x128, and 224x224 for 2D, and 64x64x64 for 3D. As a complement to the previous 28-size MedMNIST, the large-size version could serve as a standardized benchmark for medical foundation models. Install the latest API to try it out!</p> <p> </p> <p><strong>Python Usage</strong></p> <p>We recommend our official <a href="https://github.com/MedMNIST/MedMNIST">code</a> to download, parse and use the MedMNIST dataset:</p> <blockquote> <pre>% pip install medmnist<br>% python</pre> <div> <div>To use the standard 28-size (MNIST-like) version utilizing the downloaded files:</div> <br> <div>>>> from medmnist import PathMNIST</div> <div>>>> train_dataset = PathMNIST(split="train")</div> <br> <div>To enable automatic downloading by setting `download=True`:</div> <br> <div>>>> from medmnist import NoduleMNIST3D</div> <div>>>> val_dataset = NoduleMNIST3D(split="val", download=True)</div> <br> <div>Alternatively, you can access MedMNIST+ with larger image sizes by specifying the `size` parameter:</div> <br> <div>>>> from medmnist import ChestMNIST</div> <div>>>> test_dataset = ChestMNIST(split="test", download=True, size=224)</div> </div> </blockquote> <p> </p> <p><strong>Citation</strong></p> <p>If you find this project useful, please cite both v1 and v2 paper as:</p> <blockquote> <p>Jiancheng Yang, Rui Shi, Donglai Wei, Zequan Liu, Lin Zhao, Bilian Ke, Hanspeter Pfister, Bingbing Ni. Yang, Jiancheng, et al. "MedMNIST v2-A large-scale lightweight benchmark for 2D and 3D biomedical image classification." Scientific Data, 2023.</p> <p>Jiancheng Yang, Rui Shi, Bingbing Ni. "MedMNIST Classification Decathlon: A Lightweight AutoML Benchmark for Medical Image Analysis". IEEE 18th International Symposium on Biomedical Imaging (ISBI), 2021.</p> </blockquote> <p>or using bibtex:</p> <blockquote> <pre>@article{medmnistv2, title={MedMNIST v2-A large-scale lightweight benchmark for 2D and 3D biomedical image classification}, author={Yang, Jiancheng and Shi, Rui and Wei, Donglai and Liu, Zequan and Zhao, Lin and Ke, Bilian and Pfister, Hanspeter and Ni, Bingbing}, journal={Scientific Data}, volume={10}, number={1}, pages={41}, year={2023}, publisher={Nature Publishing Group UK London} } @inproceedings{medmnistv1, title={MedMNIST Classification Decathlon: A Lightweight AutoML Benchmark for Medical Image Analysis}, author={Yang, Jiancheng and Shi, Rui and Ni, Bingbing}, booktitle={IEEE 18th International Symposium on Biomedical Imaging (ISBI)}, pages={191--195}, year={2021} }</pre> </blockquote> <p>Please also cite the corresponding paper(s) of source data if you use any subset of MedMNIST as per the description on the <a href="https://medmnist.github.io/">project website</a>.</p> <p> </p> <p><strong>License</strong></p> <p>The MedMNIST dataset is licensed under <em>Creative Commons Attribution 4.0 International</em> (<a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>), except DermaMNIST under <em>Creative Commons Attribution-NonCommercial 4.0 International</em> (<a href="https://creativecommons.org/licenses/by-nc/4.0/">CC BY-NC 4.0</a>).</p> <p>The code is under <a href="https://github.com/MedMNIST/MedMNIST/blob/main/LICENSE">Apache-2.0 License</a>.</p> <p> </p> <p><strong>Changelog</strong></p> <p><a href="https://doi.org/10.5281/zenodo.10519652">v3.0</a> (this repository): Released MedMNIST+ featuring larger sizes: 64x64, 128x128, and 224x224 for 2D, and 64x64x64 for 3D.</p> <p><a href="https://doi.org/10.5281/zenodo.10519195">v2.2</a>: Removed a small number of mistakenly included blank samples in OrganAMNIST, OrganCMNIST, OrganSMNIST, OrganMNIST3D, and VesselMNIST3D. </p> <p><a href="https://doi.org/10.5281/zenodo.6496656">v2.1</a>: Addressed an issue in the NoduleMNIST3D file (i.e., nodulemnist3d.npz). Further details can be found in this <a href="https://github.com/MedMNIST/MedMNIST/issues/22#issuecomment-1103438191">issue</a>.</p> <p><a href="https://doi.org/10.5281/zenodo.5208230">v2.0</a>: Launched the initial repository of MedMNIST v2, adding 6 datasets for 3D and 2 for 2D.</p> <p><a href="https://doi.org/10.5281/zenodo.4269852">v1.0</a>: Established the initial repository (in a separate repository) of MedMNIST v1, featuring 10 datasets for 2D.</p> <p> </p> <p><strong>Note</strong>: This dataset is <strong>NOT</strong> intended for clinical use.</p>
TBGA: A Large-Scale Gene-Disease Association Dataset for Biomedical Relation Extraction
<p>This repository contains the TBGA dataset. TBGA is a large-scale, semi-automatically annotated dataset for Gene-Disease Association (GDA) extraction. The dataset consists of three text files, corresponding to train, validation, and test sets, plus an additional JSON file containing the mapping between relation names and IDs. Each record in train, validation, or test files corresponds to a single GDA extracted from a sentence. Records are represented as JSON objects with the following structure:</p> <ul> <li><strong>text:</strong> sentence from which the GDA was extracted.</li> <li><strong>relation:</strong> relation name associated with the given GDA.</li> <li><strong>h: </strong>JSON object representing the gene entity, composed of: <ul> <li><strong>id: </strong>NCBI Entrez ID associated with the gene entity.</li> <li><strong>name:</strong> NCBI official gene symbol associated with the gene entity.</li> <li><strong>pos: </strong>list consisting of starting position and length of the gene mention within text.</li> </ul> </li> <li><strong>t:</strong> JSON object representing the disease entity, composed of: <ul> <li><strong>id: </strong>UMLS CUI associated with the disease entity.</li> <li><strong>name:</strong> UMLS preferred term associated with the disease entity.</li> <li><strong>pos:</strong> list consisting of starting position and length of the disease mention within text.</li> </ul> </li> </ul> <p>TBGA contains over 200,000 instances and 100,000 bags.<br> The zip file consists of one folder, named TBGA, containing the files corresponding to the dataset.</p> <p>If you use or extend our work, please cite the following: https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-022-04646-6#citeas<br> TBGA paper can be found at: <a href="https://rdcu.be/cKkY2">https://rdcu.be/cKkY2</a><br> TBGA code is available at: https://github.com/GDAMining/gda-extraction</p>
Building Large-Scale Gene-Disease Association Datasets for Biomedical Relation Extraction
<p>This repository contains the GDAb and GDAt datasets. GDAb and GDAt are large-scale, distantly supervised, and manually enhanced datasets for Gene-Disease Association (GDA) extraction. Each dataset consists of three text files, corresponding to train, validation, and test sets, plus an additional JSON file containing the mapping between relation names and IDs. Each record in train, validation, or test files corresponds to a single GDA extracted from a sentence. Records are represented as JSON objects with the following structure:</p> <ul> <li><strong>text:</strong> sentence from which the GDA was extracted.</li> <li><strong>relation:</strong> relation name associated to the given GDA.</li> <li><strong>h: </strong>JSON object representing the gene entity, composed of: <ul> <li><strong>id: </strong>UMLS CUI associated to the gene entity.</li> <li><strong>name:</strong> UMLS preferred name associated to the gene entity.</li> <li><strong>pos: </strong>list consisting of starting position and length of the gene mention within text.</li> </ul> </li> <li><strong>t:</strong> JSON object representing the disease entity, composed of: <ul> <li><strong>id: </strong>UMLS CUI associated to the disease entity.</li> <li><strong>name:</strong> UMLS preferred name associated to the disease entity.</li> <li><strong>pos:</strong> list consisting of starting position and length of the disease mention within text.</li> </ul> </li> </ul> <p>Both datasets contain over 2,500,000 sentences and 500,000 bags.<br> The zip file consists of two folders, GDAb and GDAt, containing the files corresponding to the two datasets, respectively.</p> <p> </p>
Ontology Enrichment from Texts (OET): A Biomedical Dataset for Concept Discovery and Placement
<p>A biomedical dataset supporting ontology enrichment from texts, by concept discovery and placement, adapting the MedMentions dataset (PubMed abstracts) with SNOMED CT of versions in 2014 and 2017 under the Diseases (disorder) sub-category and the broader categories of Clinical finding, Procedure, and Pharmaceutical / biologic (CPP) product.</p> <p>The dataset is documented in the work, <em>Ontology Enrichment from Texts: A Biomedical Dataset for Concept Discovery and Placement</em>, on arXiv: <a href="https://arxiv.org/abs/2306.14704">https://arxiv.org/abs/2306.14704</a> (CIKM 2023). The companion code is available at https://github.com/KRR-Oxford/OET.</p> <p>Out-of-KB mention discovery (including the settings of mention-level data) is further partly documented in the work, <em>Reveal the Unknown: Out-of-Knowledge-Base Mention Discovery with Entity Linking</em>, on arXiv: <a href="https://arxiv.org/abs/2302.07189">https://arxiv.org/abs/2302.07189</a> (CIKM 2023).</p> <p>ver4: we made a version of mention-level data for out-of-KB discovery and concept placement separately: the former (for out-of-KB discovery) has out-of-KB mentions in training data, while the latter (for concept placement) has only out-of-KB mentions during the evaluation (validation and test) and not in the training data. Also, we split the original "test-NIL.jsonl" (now "test-NIL-all.jsonl") into "valid-NIL.jsonl" and "test-NIL.jsonl" for a better evaluation.</p> <p>ver3: we revised and updated mention-level data (syn_full, synonym augmentation setting) and the folder structure, and also updated the edge catalogues with complex edges.</p> <p>ver2: we revised the mention-level data by only keeping out-of-KB mentions (or "NIL" mentions) associated with one-hop edges (including leaf nodes, as <leaf node, NULL>) and two-hop edges in the ontology (SNOMED CT 20140901).</p> <p>Acknowledgement of data sources and tools below:</p> <p>* SNOMED CT https://www.nlm.nih.gov/healthit/snomedct/archive.html (and use snomed-owl-toolkit to form .owl files)<br>* UMLS https://www.nlm.nih.gov/research/umls/licensedcontent/umlsarchives04.html (and mainly use MRCONSO for mapping UMLS to SNOMED CT)<br>* MedMentions https://github.com/chanzuckerberg/MedMentions (source of entity linking)</p> <p>* Protégé http://protegeproject.github.io/protege/<br>* snomed-owl-toolkit https://github.com/IHTSDO/snomed-owl-toolkit<br>* DeepOnto https://github.com/KRR-Oxford/DeepOnto (based on OWLAPI https://owlapi.sourceforge.net/) for ontology processing and complex concept verbalisation</p>
Extracting Biomedical Entities from Noisy Audio Transcripts--Dataset
<p><strong>SUMMARY</strong>:</p> <p>This repo contains the CADEC and Synthetic BTACT datasets that were used for the paper titled "<em>Extracting Biomedical Entities from Noisy Audio Transcripts</em>."</p> <p>The dataset includes two sets: i) CADEC (Karimi et al., 2015) and ii) Synthetic BTACT. CADEC is a well-known NER dataset used to identify adverse drug reactions based on what patients have written about their experiences. Synthetic BTACT is the data that we have made up. It is created based on questions similar to those in the Brief Test of Adult Cognition by Telephone (BTACT)(Tun et al., 2006).</p> <p>CADEC includes two sets of audio files; one is read from the original CADEC, and the other one is with additional audio noise. It also includes the original CADEC scripts, annotations, and the transcripts of the noisy audio. The transcripts are generated using Whisper. The annotations encompass named entities, their types, and string indexes of their occurrence in the text. Annotations also include "AnnotatorNotes" which explains some of the annotations.</p> <p>The synthetic BTACT data include two types: i) animals and ii) fruits. Similar to CADEC, it includes two sets of audio files: one that is read from the original scripts and another one with additional audio noise. The text files include the original scripts, annotations, and the Whisper-transcribed of the noisy audio files. The annotations include indexes of named entities, their string indices and types.</p> <p><strong>REFERENCES</strong>:</p> <p>Karimi, S., Metke-Jimenez, A., Kemp, M., & Wang, C. (2015). Cadec: A corpus of adverse drug event annotations. Journal of biomedical informatics, 55, 73-81.</p> <p>Tun, P. A., & Lachman, M. E. (2006). Telephone assessment of cognitive function in adulthood: the Brief Test of Adult Cognition by Telephone. Age and Ageing, 35(6), 629-632.</p> <p><strong>DETAILS</strong>:</p> <p>Data_1: CADEC (1250 TextFiles, 1000 Audio, types=5):</p> <p> General Categories and Counts<br> ADR (Adverse Drug Reactions): 5316<br> DRUG: 1797<br> FINDING: 397<br> DISEASE: 280<br> SYMPTOM: 255<br> Specific Items (Drugs) and Counts<br> Arthrotec: 145<br> cambia: 4<br> cataflam: 10<br> diclofenac-potassium: 3<br> diclofenac-sodium: 7<br> flector: 1<br> Lipitor: 997<br> Pennsaid: 4<br> solarez: 3<br> voltaren: 46<br> voltaren-rx: 22<br> zipsor: 5</p> <p>Data_2: Synthetic BTACT (500 Fruits, 500 Animals, types=2)</p> <p>>> Audios can be matched with annotations, scripts and transcripts using their filenames. </p> <p>---<br>audio [original&noisy]:<br> 1. cadec<br> 1.1 cadec original<br> 1.2 cadec noisy<br> 2. synthetic btact<br> 2.1 btact original<br> 2.1.1 fruits<br> fruit-script[0:500].mp3<br> 2.1.2 animals<br> script-[0:500].mp3<br> 2.2 btact noisy<br> 2.2.1 fruits<br> fruit-script[0:500].mp3<br> 2.2.2 animals<br> script-[0:500].mp3<br>text[scripts, annotations, transcripts]:<br> 1. cadec<br> 1.1 scripts [1,250]<br> 1.2 annotations [1,250] (index/AnnotatorsNote, type, indices, named-entities)<br> 1.3 transcripts [1,000]<br> 2. synthetic btact<br> 2.1 animals<br> 2.1 scripts (original scripts)<br> script-[0:500].txt<br> 2.2 annotations<br> script-[0:500].ann (index, type, start/end indices, named entity)<br> 2.3 transcripts<br> script-[0:500].txt<br> 2.2. fruits<br> 2.1 scripts (original scripts)<br> script-[0:500].txt<br> 2.2 annotations<br> script-[0:500].ann (index, type, start/end indices, named entity)<br> 2.3 transcripts<br> fruit-script-[0:500].txt</p> <p> </p> <p><strong>CITATION</strong>:</p> <p>Ebadi, N., Morgan, K., Tan, A., Linares, B., Osborn, S., Majors, E., Davis, J., & Rios, A. (2024). Extracting biomedical entities from noisy audio transcripts. In Proceedings of the 2024 Joint International Conference on Computational Linguistics, Language Resources and Evaluation (LREC-COLING 2024).</p>
PrimeKGQA, the dataset from paper: Bridging the Gap: Generating a Comprehensive Biomedical Knowledge Graph Question Answering Dataset
<p>Despite the plethora of resources such as large-scale corpora and manually curated Knowledge Graphs (KGs), the ability to perform reasoning with natural language inputs over biomedical graphs remains challenging due to insufficient training data. We propose a novel method for automatically constructing a Biomedical Knowledge Graph Question Answering (BioKGQA) dataset sourced from PrimeKG, the largest precision medicine-oriented KG. In total,<br>we create 83999 question-answer pairs along with their respective SPARQL queries. Our approach generates a diverse array of contextually relevant questions covering a wide spectrum of biomedical concepts and levels of complexity. We evaluate our method based on automatic metrics alongside manual annotations. We establish novel standards tailored for KGQA systems to highlight the linguistic correctness and semantical faithfulness of the generated questions based on extracted KG facts. The compiled dataset – PrimeKGQA – serves as a valuable benchmarking resource for advancing knowledge-driven biomedical research and evaluating KGQA system.</p>
CZ Software Mentions: A large dataset of software mentions in the biomedical literature
<p>We describe the CZ Software Mentions dataset, a new dataset of software mentions in biomedical papers. Plain-text software mentions are extracted with a trained SciBERT model from several sources: the NIH PubMed Central collection and from papers provided by various publishers to the Chan Zuckerberg Initiative. The dataset provides sources, context and metadata, and, for a number of mentions, the disambiguated software entities and links. We extract 1.12 million unique string software mentions from 2.4 million papers in the NIH PMC-OA Commercial subset, 481k unique mentions from the NIH PMC-OA Non-Commercial subset (both gathered in October 2021) and 934k unique mentions from 4 million papers in the Publishers' collection. There is variation in how software is mentioned in papers and extracted by the NER algorithm. We propose a clustering-based disambiguation algorithm to map plain-text software mentions into distinct software entities and apply it on the NIH PubMed Central Commercial collection. Through this methodology, we disambiguate 1.12 million unique strings extracted by the NER model into ~97000 unique software entities, covering 78% of all links. We link 185 000 of the mentions to a repository, covering about 55% of all software-paper links. We make all data and code publicly available as a new resource to help assess the impact of software (in particular scientific open source projects) on science.</p>
FAIRness Assessment of Biomedical Data Using Automated Tools (Dataset)
<p>The data were collected as part of a Master's thesis project aimed at evaluating various automated FAIR assessment tools, applying them to biomedical data. The data sets identifiers were gathered as part of the Open Data LoM and IoM incentivization at Charité Universitätsmedizin Berlin, available at <a title="Dataset of the results of data validation for articles from 2021" href="https://doi.org/10.5281/zenodo.8249758">https://doi.org/10.5281/zenodo.8249758</a>, and reused in this project.</p> <p>The data represents cleaned, aggregated, and transformed results obtained from the API services of the following FAIR assessment tools: F-UJI, FAIR Enough, FAIR-Checker, and FAIR EVA.</p> <p>The raw data in .Rdata format will be shared on GitHub repository at <a title="FAIR Tools Analysis" href="https://github.com/anastasiabright/fair-tools-analysis">https://github.com/anastasiabright/fair-tools-analysis</a>.</p>
Dataset: Clearside Biomedical, Inc. (CLSD) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Talis Biomedical Corporation (TLIS) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Psyence Biomedical Ltd. (PBM) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Psyence Biomedical Ltd. (PBMWW) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Ocean Biomedical, Inc. (OCEAW) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Ocean Biomedical, Inc. (OCEA) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Dataset: Lifecore Biomedical, Inc. (LFCR) Stock Performance
This dataset provides historical stock market performance data for specific companies. It enables users to analyze and understand the past trends and fluctuations in stock prices over time. This information can be utilized for various purposes such as investment analysis, financial research, and market trend forecasting.
Bio-ML: Machine Learning-Friendly Biomedical Datasets for Equivalence and Subsumption Ontology Matching
<p> </p> <blockquote> <p><strong>This version is used in the Bio-ML track of the OAEI 2024; the only change compared to the OAEI 2023 is the deletion of certain training subsumption mappings.</strong></p> </blockquote> <p> </p> <h3><strong>Overview</strong></h3> <p>The purpose of these datasets is to support <em>equivalence</em> and <em>subsumption</em> ontology matching.</p> <p>There are five ontology pairs extracted from MONDO and UMLS:</p> <table> <tbody> <tr> <td>Source</td> <td>Task</td> <td>Category</td> <td>#SrcCls</td> <td>#TgtCls</td> <td>#Ref (equiv)</td> <td>#Ref (subs)</td> </tr> <tr> <td>Mondo</td> <td>OMIM-ORDO</td> <td>Disease</td> <td>9,648</td> <td>9,275</td> <td>3,721</td> <td>103</td> </tr> <tr> <td>Mondo</td> <td>NCIT-DOID</td> <td>Disease</td> <td>15,762</td> <td>8,465</td> <td>4,686</td> <td>3,338 (-1)</td> </tr> <tr> <td>UMLS</td> <td>SNOMED-FMA</td> <td>Body</td> <td>34,418</td> <td>88,955</td> <td>7,256</td> <td>5,453 (-53)</td> </tr> <tr> <td>UMLS</td> <td>SNOMED-NCIT</td> <td>Pharm</td> <td>29,500</td> <td>22,136</td> <td>5,803</td> <td>4,224 (-1)</td> </tr> <tr> <td>UMLS</td> <td>SNOMED-NCIT</td> <td>Neoplas</td> <td>22,971</td> <td>20,247</td> <td>3,804</td> <td>213</td> </tr> </tbody> </table> <p>The "-" numbers reflect the changes due to lthe deletion of certain training subsumption mappings.</p> <p>The main track is available at "bio-ml", where each pair is associated with a task folder, containing the source and target ontologies, reference equivalence mappings (in "refs_equiv"), reference subsumption mappings ("refs_subs"). </p> <p>The special sub-track is available at "bio-llm", where each pair is associated with a task folder, containing the source and target ontologies, and the test candidate mappings. </p> <p> </p> <h3><strong>Citation</strong></h3> <p><strong>Bio-ML (Main Track)</strong></p> <pre>```<br>@inproceedings{he2022machine, title={Machine learning-friendly biomedical datasets for equivalence and subsumption ontology matching}, author={He, Yuan and Chen, Jiaoyan and Dong, Hang and Jim{\'e}nez-Ruiz, Ernesto and Hadian, Ali and Horrocks, Ian}, booktitle={International Semantic Web Conference}, pages={575--591}, year={2022}, organization={Springer} }<br>```</pre> <p><strong>Bio-LLM (Sub-track)</strong></p> <pre>```<br>@article{he2023exploring, title={Exploring large language models for ontology alignment}, author={He, Yuan and Chen, Jiaoyan and Dong, Hang and Horrocks, Ian}, journal={arXiv preprint arXiv:2309.07172}, year={2023} }<br>```</pre> <p> </p> <h3><strong>Important Links</strong></h3> <ul> <li>See detailed documentation at: <a href="https://krr-oxford.github.io/DeepOnto/bio-ml">https://krr-oxford.github.io/DeepOnto/bio-ml</a>.</li> <li>See the OAEI Bio-ML track at: <a href="https://www.cs.ox.ac.uk/isg/projects/ConCur/oaei/">https://www.cs.ox.ac.uk/isg/projects/ConCur/oaei/</a></li> <li>See our resource paper for the original Bio-ML at <a href="https://arxiv.org/abs/2205.03447">arxiv</a> or <a href="https://link.springer.com/chapter/10.1007/978-3-031-19433-7_33">springer</a> (accepted at <em>ISWC-2022</em> and nominated as the <em>best resource paper candidate</em>). See our poster paper for the Bio-LLM sub-track at <a href="https://arxiv.org/abs/2309.07172">arxiv </a>(accepted at <em>ISWC-2023 Posters & Demos</em>).</li> </ul> <p> </p> <h3><strong>Changelog</strong></h3> <p>The only change in this version compared to the OAEI 2023 is the deletion of certain training subsumption mappings that can be directly exploited through deductive reasoning.</p>
Dataset of a Study of Computational reproducibility of Jupyter notebooks from biomedical publications
<p>This repository contains the dataset for the study of <a href="https://doi.org/10.1093/gigascience/giad113">computational reproducibility of Jupyter notebooks from biomedical publications</a>. Our focus lies in evaluating the extent of reproducibility of Jupyter notebooks derived from GitHub repositories linked to publications present in the biomedical literature repository, PubMed Central. We analyzed the reproducibility of Jupyter notebooks from GitHub repositories associated with publications indexed in the biomedical literature repository PubMed Central. The dataset includes the metadata information of the journals, publications, the Github repositories mentioned in the publications and the notebooks present in the Github repositories.</p> <p><strong>Data Collection and Analysis</strong></p> <p>We use the code for reproducibility of Jupyter notebooks from the study done by <a href="../record/2592524">Pimentel et al., 2019</a> and adapted the code from <a href="https://github.com/fusion-jena/ReproduceMeGit">ReproduceMeGit</a>. We provide code for collecting the publication metadata from PubMed Central using <a href="https://biopython.org/docs/1.76/api/Bio.Entrez.html">NCBI Entrez utilities via Biopython</a>.</p> <p>Our approach involves searching PMC using the esearch function for Jupyter notebooks using the query: ``(ipynb OR jupyter OR ipython) AND github''. We meticulously retrieve data in XML format, capturing essential details about journals and articles. By systematically scanning the entire article, encompassing the abstract, body, data availability statement, and supplementary materials, we extract GitHub links. Additionally, we mine repositories for key information such as dependency declarations found in files like requirements.txt, setup.py, and pipfile. Leveraging the GitHub API, we enrich our data by incorporating repository creation dates, update histories, pushes, and programming languages.</p> <p>All the extracted information is stored in a SQLite database. After collecting and creating the database tables, we ran a pipeline to collect the Jupyter notebooks contained in the GitHub repositories based on the code from Pimentel et al., 2019.</p> <p>Our reproducibility pipeline was started on 27 March 2023.</p> <p><strong>Repository Structure</strong></p> <p>Our repository is organized into two main folders:</p> <ul> <li><strong>archaeology</strong>: This directory hosts scripts designed to download, parse, and extract metadata from PubMed Central publications and associated repositories. There are 24 database tables created which store the information on articles, journals, authors, repositories, notebooks, cells, modules, executions, etc. in the db.sqlite database file.</li> <li><strong>analyses</strong>: Here, you will find notebooks instrumental in the in-depth analysis of data related to our study. The db.sqlite file generated by running the archaelogy folder is stored in the analyses folder for further analysis. The path can however be configured in the config.py file. There are two sets of notebooks: one set (naming pattern N[0-9]*.ipynb) is focused on examining data pertaining to repositories and notebooks, while the other set (PMC[0-9]*.ipynb) is for analyzing data associated with publications in PubMed Central, i.e.\ for plots involving data about articles, journals, publication dates or research fields. The resultant figures from the these notebooks are stored in the 'outputs' folder.</li> <li><strong>MethodsWorkflow</strong>: The MethodsWorkflow file provides a conceptual overview of the workflow used in this study.</li> </ul> <p><strong>Accessing Data and Resources:</strong></p> <ul> <li>All the data generated during the initial study can be accessed at https://doi.org/10.5281/zenodo.6802158</li> <li>For the latest results and re-run data, refer to this link.</li> <li>The comprehensive SQLite database that encapsulates all the study's extracted data is stored in the db.sqlite file.</li> <li>The metadata in xml format extracted from PubMed Central which contains the information about the articles and journal can be accessed in pmc.xml file.</li> </ul> <p><strong>System Requirements:</strong></p> <ul> <li>Centos 7 (Documentation: https://www.centos.org/)</li> <li>Conda 4.9.4 (Installation Guide: https://docs.anaconda.com/anaconda/install/linux/)</li> <li>Python 3.7.6 (Download Link: https://www.python.org/downloads/)</li> <li>GitHub account (Get Started: https://github.com/, Requires GitHub Username and Token)</li> <li>gcc 7.3.0 (Installation Guide: https://gcc.gnu.org/install/)</li> <li>lbzip2 (Command: `conda install -c conda-forge lbzip2')</li> </ul> <p><strong>Running the pipeline:</strong></p> <ul> <li>Clone the computational-reproducibility-pmc repository using Git:<br>git clone https://github.com/fusion-jena/computational-reproducibility-pmc.git<br> </li> <li>Navigate to the computational-reproducibility-pmc directory:<br>cd computational-reproducibility-pmc/computational-reproducibility-pmc</li> <li>Configure environment variables in the config.py file:<br>GITHUB_USERNAME = os.environ.get("JUP_GITHUB_USERNAME", "add your github username here")<br>GITHUB_TOKEN = os.environ.get("JUP_GITHUB_PASSWORD", "add your github token here")</li> <li>Other environment variables can also be set in the config.py file.<br>BASE_DIR = Path(os.environ.get("JUP_BASE_DIR", "./")).expanduser() # Add the path of directory where the GitHub repositories will be saved<br>DB_CONNECTION = os.environ.get("JUP_DB_CONNECTION", "sqlite:///db.sqlite") # Add the path where the database is stored.</li> <li>To set up conda environments for each python versions, upgrade pip, install pipenv, and install the archaeology package in each environment, execute:<br>source conda-setup.sh</li> <li>Change to the archaeology directory<br>cd archaeology</li> <li>Activate conda environment. We used py36 to run the pipeline.<br>conda activate py36</li> <li>Execute the main pipeline script (r0_main.py):<br>python r0_main.py</li> </ul> <p><strong>Running the analysis:</strong></p> <ul> <li>Navigate to the analysis directory.<br>cd analyses</li> <li>Activate conda environment. We use raw38 for the analysis of the metadata collected in the study.<br>conda activate raw38</li> <li>Install the required packages using the requirements.txt file.<br>pip install -r requirements.txt</li> <li>Launch Jupyterlab<br>jupyter lab</li> <li>Refer to the Index.ipynb notebook for the execution order and guidance.</li> </ul> <p><strong>References:</strong></p> <ul> <li>Sheeba Samuel, Daniel Mietchen. (2024). Computational reproducibility of Jupyter notebooks from biomedical publications, https://doi.org/10.1093/gigascience/giad113, GigaScience</li> <li>Sheeba Samuel, Daniel Mietchen. (2022). Computational reproducibility of Jupyter notebooks from biomedical publications, https://arxiv.org/pdf/2209.04308.pdf, CoRR abs/2209.04308</li> <li>Sheeba Samuel, & Daniel Mietchen. (2022). Dataset of a Study of Computational reproducibility of Jupyter notebooks from biomedical publications [Data set]. Zenodo. https://doi.org/10.5281/zenodo.6802158</li> </ul> <p> </p>
CZ Software Mentions: A large dataset of software mentions in the biomedical literature
Open the record for dataset details and reuse information.
CZ Software Mentions: A large dataset of software mentions in the biomedical literature - Expanded 2024
Open the record for dataset details and reuse information.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research 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.
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.
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.
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.
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.