- Creating an empty RawData is no longer needed in order to add a PrepTemplate. Now, the PrepTemplate is required in order to add a RawData to a study. This is the normal flow of a study, as the PrepTemplate information is usually available before the RawData information is available.
- A user can upload a QIIME mapping file instead of a SampleTemplate. The system will create a SampleTemplate and a PrepTemplate from the information present in the QIIME mapping file. The QIIME required columns for this functionality to work are 'BarcodeSequence', 'LinkerPrimerSequence' and 'Description'. For more information about QIIME mapping files, visit http://qiime.org/documentation/file_formats.html#mapping-file-overview.
- The command line interface has been reorganized:
qiita_env
has been renamedqiita-env
qiita_test_install
has been renamedqiita-test-install
qiita ebi
has been moved toqiita ware ebi
qiita log
has been moved toqiita maintenance log
- A new
qiita pet
command subgroup has been created qiita webserver
has been moved toqiita pet webserver
- Cluster names now use dashes instead of underscores (e.g.,
qiita_general
is nowqiita-general
) qiita-general
is now used as a default argument toqiita-env start_cluster
andqiita-env stop_cluster
if no cluster name is specified- Qiita now now allows for processing of already demultiplexed data without any technical (barcode and primer) section of the read.
- Qiita now includes full portal support, limiting study and analysis access at below the qiita_db level. This allows one database to act as if subsets of studies/analyses are their own specific interface. Commands added for portals creation and maintenance, under
qiita db portal ...
andqiita-env
. Portal specific web user interface support has also been added; each portal is fully CSS customizable. - 403 errors are now not logged in the logging table
- Qiita will execute all DB interactions in transactions. The queue code was moved and improved from SQLConnectionHandler to a new Transaction object. The system implements the singleton pattern. That is, there is only a single transaction in the system, represented by the variable
TRN
, and all DB interactions go through it.
Initial alpha release.