An R package to interact with NCBI's Entrez system, enabling programmatic search and retrieval of biological data.
rentrez is an R package that provides a programmatic interface to NCBI's Entrez system, allowing users to search, retrieve, and analyze data from over 50 biological databases directly within R. It solves the problem of manually accessing biological data through web interfaces by enabling automated, reproducible workflows for bioinformatics research.
Bioinformaticians, computational biologists, and researchers who need to programmatically access NCBI databases like PubMed, GenBank, and Protein for data analysis and reproducible research workflows in R.
Developers choose rentrez because it offers a comprehensive, R-native wrapper for NCBI's E-utilities API, simplifying complex queries and data retrieval tasks while supporting reproducible research through scriptable access to vast biological datasets.
talk with NCBI entrez using R
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Wraps all E-utilities API endpoints, enabling seamless interaction with over 50 databases like PubMed and GenBank, as demonstrated in multi-database query examples.
Functions chain together for complex tasks, such as finding papers and downloading linked sequences, facilitating scriptable research pipelines shown in the vignette.
Supports retrieval in various formats including FASTA and XML, and handles large datasets using web history features, illustrated in the big queries example.
Provides functions like `entrez_db_searchable` to explore databases and searchable fields programmatically, aiding in interactive sessions and query construction.
Tightly coupled with NCBI's API, so changes or downtime in NCBI services can break functionality, and rentrez may lag in supporting new database features or updates.
Exclusively designed for R, making it unsuitable for projects in other programming environments without additional bridging tools or workarounds.
Requires understanding of NCBI's search term syntax and database-specific fields, which can be steep despite simplification, as noted in the need to consult API documentation.