Ebiotic
Ebiotic provides a light-weight asynchronous interface for some popular Bioinformatics web services. It is designed to
enable access to the rich data and tools provided by institutes like the European Bioinformatics
Institute (EBI) and the National Center for Biotechnology
Information (NCBI). It's built to serialize
and deserialze data using common formats like JSON and specialised bioinformatics formats like FASTA using the Record
data
structure from the rust-bio library.
The library (currently) does not safeguard against misuse of the endpoints and so it is important to read and understand the terms of use for each API before using this library.
Installation
The library is currently in the early stages of development and is therefore not stable, but remains available
on crates.io. To install, add
the following to your Cargo.toml file:
[]
= "0.0.21"
Usage
The library is designed to be simple to use and to provide a consistent interface to the various APIs. The following example demonstrates how to use the library to search the European Nucleotide Archive (ENA) for a selection of entries.
async
The Dbfetch struct is used to create a new instance of the Dbfetch API. The DbfetchIds struct is used to create a
new instance of the DbfetchIds request. The run method is then called on the Dbfetch instance with
the DbfetchIds instance as an argument. The run method returns a Result which is then unwrapped and converted into
a Vec<Record> using the into_records method.
More examples can be found in the documentation. Including how to run in synchronous code-bases.
Current APIs
NCBI:
- Web-BLAST (currently only supports protein searches as it was used for another project)
EBI:
Job Dispatcher:
- Clustal Omega
Knowledge & Data:
- DBfetch
Contributing
Contributions are more than welcome. To implement a new endpoint follow the structure of the current modules and utilise
the functionality provided by the ebiotic::core module. If you have any questions or need help, feel free to open an
issue or reach out to me on via email.
TODOs
- More tools and data sources
- Add supplementary methods to result types (beyond just returning the data)
- Add more tests
- Add more documentation
- Add more examples
- Add more error handling
- Add logging system beyond print statements (e.g. tracing or log crate)
- Add more configuration options
- Safety checks for API usage (?)