The OBITools3 are still in beta. If you encounter bugs or want to request a feature, you can do so in issues or by sending an email at firstname.lastname@example.org. You can also see incoming features in the issues.
The OBITools3 rely on an ad hoc database system, inside which all the data that a DNA metabarcoding experiment must consider is stored: the sequences, the metadata (describing for instance the samples), the database containing the reference sequences used for the taxonomic annotation, as well as the taxonomic databases.
DNA metabarcoding data can easily be represented in the form of tables, and each command can be regarded as an operation transforming one or several 'input' tables into one or several 'output' tables, which can be used by the next command.
The new database system used by the OBITools3 (called DMS for Data Management System) relies on column-oriented storage. Each column contains a data element, and several columns can be assembled in views representing the data tables (equivalent to a fasta file).
The OBITools3 syntax
obi command [options] input_URI output_URI
A URI (Uniform Resource Identifier) is a simple way to identify the input and output of a command. For a file, it's simply the path to the file. For a view, it can be the path to the view file in the DMS:
Or a simplified version:
Any hybrid of those 2 works too.
View names must be unique within a DMS, in other words, views can not be overwritten.
All tools accept different input and output DMS.
If the output DMS is not given, the input DMS is used.
For a taxonomy, both those and their hybrids work: