Over the past few days, we have taken an important step in the development of ChromoDB: an active development version is now available online. This environment allows us to begin testing how chromosome-count records will be displayed, queried, and linked outside the internal database management system.
Until now, much of the data management work has relied on Caspio, which has been a useful platform for handling and querying large datasets. However, one of the long-term objectives of ChromoDB is to move progressively towards a dedicated web infrastructure, offering greater flexibility, better integration with future developments, and a clearer public identity for the project.
The initial development version was first made available at https://dev.chromodb.net. This environment has now evolved into a provisional public database interface at https://database.chromodb.net, where we are testing record visualization, navigation, data consistency, and the implementation of stable URLs for individual ChromoDB records. It should not yet be regarded as a definitive public release, but as a working version of the future ChromoDB database.
This step is particularly relevant because ChromoDB is intended to be more than a static data table. Its aim is to become a searchable, documented, and progressively interoperable resource for chromosome-count data. The database remains under active taxonomic, bibliographic, and methodological revision, but the availability of a working web environment provides a clearer framework for transforming a large and heterogeneous body of chromosome information into a usable research and teaching resource.
In parallel, we are also exploring how selected parts of the dataset may later be adapted to standardized formats suitable for biodiversity data infrastructures. In this context, ChromoDB is conceived as the comprehensive and continuously updated project portal, while other platforms may eventually host selected, stable, and standardized subsets of the data.
This development version is still an early step, but it represents a significant transition: ChromoDB is beginning to move from an internal working database towards a dedicated web-based resource.