2.1.1 released

• several bugfixes
• last update caused a bug removing No Match hits from the top hit selections

2.1.0 released

• for the selection of the top hit with any method all entries with special characters and / or numbers will be ignored in the future. This solves the problem of "garbage" in the BOLD database (e.g. SP199d as species name, or sp. as species name)
• This update leads to much cleaner species lists as well as more hits that can be retrieved via the API correction module

2.0.5 released

• fixed a datatype issue when computing jamp hit

2.0.4 released

• important bugfix on the saving of intermediate results that made the ID engine to crash

2.0.2 released

• fixed a bug where all private hits caused an error in the save function

2.0.0 released

• major bugfix / improvement regarding the finding of the best fitting hit with either the JAMP method or the BOLDigger method. Hit with missing data will be ignored for finding the most common hit which will lead to a more complete taxalist
• This makes BOLDigger incompatible with the command line version for now. I'm already working on the 2nd version of the command-line tool, which will take some time.

1.5.6 released

• bugfix on the API verification option

1.5.5 released

• added a failsave in case the connection to BOLD is closed by BOLD before results come in. In this case the request is going to be resent until it gets a clean response

1.5.4 released

• fixed the hdf to excel converter so split the data in multiple parts to be able to save large datasets in multiple excel files. If the dataset exceeds 50.000 OTUs / sequences, the results will be saved in chunks of 50.000.

1.5.0 released

• found a bug where a NoMatch table would be saved when BOLD sends a malformed response and fixed it
• rewrote the complete code for fetching and saving the data
• Intermediate BOLDResults are now saved in .hdf format. This allows to append new data really quickly and is much faster than writing excel files in general. For large datasets, several hours of saving operations are therefore saved.
• When the download is complete the hdf will be translated into an excel file once.
• The hdf file will be retained and can be edited with e.g. Python or R