Releases: DominikBuchner/BOLDigger3
Releases · DominikBuchner/BOLDigger3
3.0.1 released
- bugfix causing the database download to fail due to missing cookies. The download is now initiated with the session instead of urllib.
3.0.0 released
- the previously monolithic identify workflow has been split into two separate commands:
identifyanddownload_db download_dbdownloads the latest BOLD public data package and converts it to a local DuckDB (.ddb) file- BOLDigger3 checks automatically if the local database is already up to date and skips the download if so
- Requires a valid BOLD account (register at boldsystems.org) — username and password are prompted interactively
- Credentials are only needed for download_db; identify does not require a login as before
- identify no has an additional argument pointing at the downloaded database
2.3.0 released
- as BOLD limited the possible number of requests heavily, this is a hotfix to keep BOLDigger3 working.
- In the meantime I'm already considering a local option for BOLDigger4, so stay tuned.
2.2.0 released
- fixed a bug that kept the ID engine stuck at n% whenever one of the request IDs failed to respond. Those request IDs are now being requeued after 15 minutes and downloaded in a second iteration.
2.1.4 released
- Bugfix that caused the ID engine to no longer work. BOLD keeps on silently changing API commands -.-
2.1.3 released
- fixed a bug where streaming to excel would result in an overflow
2.1.2 released
- Implemented the % similarity definition by BOLD. The output of BOLDigger now matches the Web Interface perfectly!
- Fixed a bug where identifying multiple fasta files in the same folder led to an error.
2.1.1 released
- Fixed a bug where the database string led to a different endpoint than the BOLD website
- There's still some disagreement between the web interface and the downloadable JSONL. I'm in contact with BOLD regarding this matter.
2.0.2 released
- bugfix that caused the data cleaning function to fail when taxonomic columns where completly empty.
2.0.1 released
- Fixed a bug, where BOLDigger3 failed when selecting database 2. For unknown reasons BOLD does not return a status when db 2 is used, so the status column has to be updated manually
- Fixed a bug where BOLDigger3 would crash if only no-matches are returned for a query