Skip to main content

Taxadb

Build Status Documentation Status made-with-python PyPI version codecov LICENSE

:warning: **This project will not receive updates for the time being :warning:

Taxadb is an application to locally query the ncbi taxonomy. Taxadb is written in python, and access its database using the peewee library.

In brief Taxadb:

  • is a small tool to query the ncbi taxonomy.
  • is written in python >= 3.5.
  • has built-in support for SQLite, MySQL and PostgreSQL.
  • has available pre-built SQLite databases.
  • has a comprehensive API documentation.

Installation

Taxadb requires python >= 3.5 to work. To install taxadb with sqlite support, simply type the following in your terminal:

pip3 install taxadb

If you wish to use MySQL or PostgreSQL, please refer to the full documentation

Usage

Querying the Database

Firstly, make sure you have built the database

Below you can find basic examples. For more complete examples, please refer to the complete API documentation

    >>> from taxadb.taxid import TaxID

    >>> taxid = TaxID(dbtype='sqlite', dbname='mydb.sqlite')
    >>> name = taxid.sci_name(33208)
    >>> print(name)
    Metazoa

    >>> lineage = taxid.lineage_name(33208)
    >>> print(lineage)
    ['Metazoa', 'Opisthokonta', 'Eukaryota', 'cellular organisms']
    >>> lineage = taxid.lineage_name(33208, reverse=True)
    >>> print(lineage)
    ['cellular organism', 'Eukaryota', 'Opisthokonta', 'Metazoa']

    >>> taxid.has_parent(33208, 'Eukaryota')
    True

Get the taxid from a scientific name.

    >>> from taxadb.names import SciName

    >>> names = SciName(dbtype='sqlite', dbname='mydb.sqlite')
    >>> taxid = names.taxid('Physisporinus cinereus')
    >>> print(taxid)
    2056287

Get the taxonomic information for accession number(s).

    >>> from taxadb.accessionid import AccessionID

    >>> my_accessions = ['X17276', 'Z12029']
    >>> accession = AccessionID(dbtype='sqlite', dbname='mydb.sqlite')
    >>> taxids = accession.taxid(my_accessions)
    >>> taxids
    <generator object taxid at 0x1051b0830>

    >>> for tax in taxids:
        print(tax)
    ('X17276', 9646)
    ('Z12029', 9915)

You can also use a configuration file in order to automatically set database connection parameters at object build. Either set config parameter to __init__ object method:

   >>> from taxadb.accessionid import AccessionID

   >>> my_accessions = ['X17276', 'Z12029']
   >>> accession = AccessionID(config='/path/to/taxadb.cfg')
   >>> taxids = accession.taxid(my_accessions)
   >>> ...

or set environment variable TAXADB_CONFIG which point to configuration file:

   $ export TAXADB_CONFIG='/path/to/taxadb.cfg'

then

   >>> from taxadb.accessionid import AccessionID

   >>> my_accessions = ['X17276', 'Z12029']
   >>> accession = AccessionID()
   >>> taxids = accession.taxid(my_accessions)
   >>> ...

Check documentation for more information.

Creating the Database

Download data

The following commands will download the necessary files from the ncbi ftp into the directory taxadb.

$ taxadb download -o taxadb

Insert data

SQLite
$ taxadb create -i taxadb --dbname taxadb.sqlite

You can then safely remove the downloaded files

$ rm -r taxadb
MySQL

Creating databases is a very vendor specific task. Peewee, as most ORMs, can create tables but not databases. In order to use taxadb with MySQL, you'll have to create the database yourself.

Connect to your mysql server

$ mysql -u $user -p
$ mysql> CREATE DATABASE taxadb;

Load data

$ taxadb create -i taxadb --dbname taxadb --dbtype mysql --username <user> --password <pwd> ...
PostgreSQL

Creating databases is a very vendor specific task. Peewee, as most ORMs, can create tables but not databases. In order to use taxadb with PosgreSQL, you'll have to create the database yourself.

Connect to your postgresql server

$ psql -U $user -d postgres
$ psql> CREATE DATABASE taxadb;

Load data

$ taxadb create -i taxadb --dbname taxadb --dbtype postgres --username <user> --password <pwd> ...

You can easily rerun the same command, taxadb is able to skip already inserted taxid as well as accession.

Tests

You can easily run some tests. Go to the root directory of this projects cd /path/to/taxadb and run nosetests.

This simple command will run tests against an SQLite test database called test_db.sqlite located in taxadb/test directory.

It is also possible to only run tests related to accessionid or taxid as follow

$ nosetests -a 'taxid'
$ nosetests -a 'accessionid'

You can also use the configuration file located in root distribution taxadb.ini as follow. This file should contains database connection settings:

$ nosetests --tc-file taxadb.ini

You can easily override configuration file settings using command line options --tc such as:

$ nosetest --tc-file taxadb.ini --tc=sql.dbname:another_dbname

More info at nose-testconfig

Running tests against PostgreSQL or MySQL

First create a test database to insert test data

  • PostgreSQL
$ createdb <test_db>

or

$ psql -U postgres
psql> CREATE DATABASE <test_db>;
  • MySQL
$ mysql -u root
mysql> CREATE DATABASE <test_db>;

Load test data

  • PostgreSQL
$ gunzip -c /path/to/taxadb/taxadb/test/test_mypg_db.sql.gz | psql -d <test_db> -U <user>
  • MySQL
$ gunzip -c /path/to/taxadb/taxadb/test/test_mypg_db.sql.gz | mysql -D <test_db> -u <user> -p

Run tests

Either edit taxadb.ini to fit database configuration or use --tc command line option and set appropriate values like username, password, port, hostname, dbtype(postgres or mysql), dbname.

  1. PostgreSQL
$ nosetests --tc-file taxadb.ini
OR
$ nosetests -tc-file taxadb.ini --tc=sql.dbtype:postgres --tc=sql.username:postgres --tc=sql.dbname:test_db2
  1. MySQL
$ nosetests --tc-file taxadb.ini
OR
$ nosetests -tc-file taxadb.ini --tc=sql.dbtype:mysql --tc=sql.username:root --tc=sql.dbname:newdbname

License

Code is under the MIT license.

Issues

Found a bug or have a question? Please open an issue

Contributing

Thought about a new feature that you'd like us to implement? Open an issue or fork the repository and submit a pull request

Metadata

Release files for taxadb 0.12.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for taxadb 0.12.1
File Size Uploaded Provenance Actions
taxadb-0.12.1.tar.gz 18.0 kB Without provenance Details for taxadb-0.12.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for taxadb 0.12.1
File Interpreter ABI Platform Actions
taxadb-0.12.1-py3-none-any.whl Python 3 none any Details for taxadb-0.12.1-py3-none-any.whl

Total release size: 37.7 kB

Release files / taxadb-0.12.1.tar.gz

Download URL taxadb-0.12.1.tar.gz
Size 18.0 kB
Tags Source
SHA-256 checksum
How to use checksums
eca577cd0f4ff2f26c7d8f68d7f5a0d2f7a2f73e623139ded2493e429b23cecd
BLAKE2b-256 checksum
How to use checksums
0ae232f9a11d0a99beb7973f2fe2f8116a994d9c4eb7abfe18ccecfcd11b3c51
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.2

Release files / taxadb-0.12.1-py3-none-any.whl

Download URL taxadb-0.12.1-py3-none-any.whl
Size 19.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cdfe000e474eb56d2174349fa40b2eacb6801687a748349c10e7db06a4247a3b
BLAKE2b-256 checksum
How to use checksums
eaf8b29e362cf7e174d79deb3df244cceb71c975e98c3e15572fb7ee44d5fe49
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.2

Security for taxadb 0.12.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page