soda4LCA 5.5.0 release

Dear soda4LCA community,

the 5.5.0 feature release of soda4LCA has been published yesterday. Alongside a significant performance improvement when exporting entire data stocks as ZIP archives, it delivers a few further improvements and addresses a number of issues.

5.5.0

Features:

• Add a language switch to the user interface
• Admin: add a new option to trigger a re-read of the application configuration from the soda4LCA.properties file from the admin menu, without need to restart the instance
• REST API: add “name” as secondary sort criterium when retrieving lists of datasets
• REST API: entries under “compliance” will now be alphabetically sorted
• Add default sort order for EF3.0 LCIA indicators in custom sort mode (display.sort.indicators = custom setting)

Bug fixes:

• Fix an issue where the migration to database schema version 15.1 would fail if some LCIA method dataset were referenced but missing
• Fix an issue where LCIA results would not be displayed
• Manage datasets: fix scrambled column headers in Excel exports
• Manage datasets: fix missing contents in Excel exports
• Manage data stocks: fix issue with persisting data stock name when edited after initial creation
• Fix an issue where a change of name of a data stock would not be persisted
• REST API: fix an issue where langFallback would not be applied to JSON output
• Fix issue where exchanges would reference wrong flow versions

Misc:

• Speed up export of data stocks as ZIP archives
• The Docker image has been adjusted to host configuration and data files in a dedicated location and is now ready for use in production. See the Docker section in the Installation Guide for more details.

Documentation:

• Add instructions for deployments using the soda4LCA Docker image

The complete release notes can be found at

https://bitbucket.org/okusche/soda4lca/src/5.5.0/Doc/src/RELEASE_NOTES.md

As always, you can download the complete package with sources, binaries and documentation at

https://bitbucket.org/okusche/soda4lca/downloads

Please submit any issues using Bitbucket’s issue tracker.

Code contributions are always very welcome! If you’d like to do so, please submit a pull request that’s based on the latest code to ensure quick processing without merge conflicts.