0.5.2
Released 0.5.2
NOTE
I changed the family field in the Family table to not be an alternateID so that we can have duplicates for family names. To ensure uniqueness for families I added an index so that the family name combined with the species qualifier has to be unique.
In botanical terms this means that we can now have both Malvaceae (s. lat) and Malvaceae (s. str). Normally for a change to the model I would bump the minor version number but I didn't this time. If this affects anyone then dump the database, create a new database and reimport the data and everything should be fine. If anyone get's stung by this then let me know.
- The main new feature is the new species editor. It is along the lines of the new accession editor with a rich interface and continues the move away from spreadsheet like data entry. The species editor also includes the species synonyms and vernacular names editing in the same editor as the species so everything is in one convenient place.
- This release also includes a lot of documentation updates, especially for developers. It should now be alot easier if anyone is interested in writing new plugins for Bauble or customizing the code to suit their organization.
- The species infobox should now be more complete and relative to everything Bauble knows about the species.
- Made the interface more responsive in a lot of places and added progress bars for long operations like importing.
- Changed the header format for CVS import/export.
- And as usual there are lots of small changes that I can't remember and the usual bug fixes.
NOTE
I changed the family field in the Family table to not be an alternateID so that we can have duplicates for family names. To ensure uniqueness for families I added an index so that the family name combined with the species qualifier has to be unique.
In botanical terms this means that we can now have both Malvaceae (s. lat) and Malvaceae (s. str). Normally for a change to the model I would bump the minor version number but I didn't this time. If this affects anyone then dump the database, create a new database and reimport the data and everything should be fine. If anyone get's stung by this then let me know.
