Free Software Disclaimer
This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or the use or other dealings in the software.
Download
While this software is provided free of charge for personal or commercial use, its distribution is strictly controlled. Redistribution of this software by any means—electronic, physical, or otherwise—is not permitted. To ensure version integrity, proper attribution, and access to up-to-date documentation and support, the only authorized method of distribution is via the official download link provided on this page. Unauthorized redistribution, modification, or hosting of the software is expressly prohibited.
Version: 1.0
Launch Date: April 25, 2025
SHA1: e12aa932824c06a23b5960d5cd57701ec98726b5
Client Edition
A Client Edition of Hootify is available for organizations that require additional features or expanded functionality. If you're interested in access, please visit the Contact Us page to inquire about becoming a client and to learn more about what the Client Edition offers.
Existing clients can access the full feature set and support resources through the Client Area. If a specific capability is not currently available, we welcome your input—custom implementations are considered on a case-by-case basis.
Documentation
This documentation applies to the free edition of the software. For the Client Edition, click the ❓ button in the application interface.
The database
The complimentary version supports SQLite databases. The database path, tables, and relevant columns are defined in a YAML configuration file. This file can be provided as a launch argument or selected via a prompt at startup.
YAML file syntax
The configuration uses a standard plain-text YAML format. Below is a customizable example:
database: "aves.db"
recordQuery: |
SELECT record, category
FROM tableToBeClassified
WHERE category is NULL
ORDER BY name;
categoryQuery: |
SELECT category
FROM tableWithCategories;"
Refine the structure to match your schema. We offer a complimentary consultation to tailor your SQL statement—contact us for bespoke guidance.
The interface
The interface is divided into three primary regions:
1. The input table
Not all columns in the input table are editable. A cell can be modified if clicking it highlights the frame. For classification entries in the final column, selections may be made in one of two ways:
- By double-clicking a category in the tree (see Section 3), or
- By typing the initial characters of a category and pressing Enter to confirm the top match.
Controls above the table allow for re-sorting entries or restoring the original sequence.
2. The log table
Accepted changes are recorded in this section and visually distinguished in the input table for clarity. The Client Edition offers the ability to log changes into a structured table for journaling and audit purposes.
3. The category tree
As you type into the input table, the category tree dynamically reorders to present the closest matching entries first. You do not have to type the full category, pressing Enter will accept the top choice. If the category has subcategories, the tree opens up.
While typing is faster, the category tree is
The help button ❓ opens this documentation in the system’s default browser.
The box New Category is used in the Client Edition to define and manage custom categories.