Releases: GreenDelta/epd-editor
Version 6.0
This release fixes the issues of milestone 6: https://github.com/GreenDelta/epd-editor/milestone/6?closed=1
Among other things, the following has changed:
- The indicator table has now a different layout which makes it more compact and easier to use:
- The import and export Excel format for indicator values have also changed, so that it matches the layout in the user interface:
- The reference data and EPD profiles have been updated and errors regarding indicator and unit IDs have been fixed:
- It is now easier to add and edit translations directly in a dataset:
- Updated validation profiles are shipped with this release, see the editor settings to enable them:
For more details, please see the issue descriptions of the milestone.
Version 5.0
add a `refresh` action to the navigation (just in case...)
Version 4.0.0
Note that this is a pre-release and there are maybe still bugs that need to be fixed. The EPD-Editor now runs on Java 14 and Eclipse 2020-03. The following issues should be fixed:
- #12 do not write empty extension points into the data set information element of products
- #48 hide password in connection editor
- #45 added collapse all and expand all actions
- #27 better column widths
- #39 check for non-ASCII characters in external file names
- #7 export single data set with optional dependencies to a zip file
When adding flow properties like Area or Volume a dialog now pops up with hints for additional material properties that probably should be added:
The editor now also supports the following fields of the ILCD-EPD format:
- License type
- Data set generator / modeller
- Preceding data set version
- Registration number
- Registration authority
- Commissioner
- Project
- Intended Applications
Version 3.1.0
Version 3.0.1
This release improves the version handling of referenced data sets (issues #9 and #15).
When a data set is opened, the references are now checked against the data set index of the application. When there are newer versions of the data set references in the index the following dialog is shown:
When the user clicks on ok these references are updated with the last versions from the index (when they are newer). The version of the data set is then incremented, and the data set is saved. Note that there is now also a Reload button in the data set toolbar which also triggers this check:
Related to issue #15 there is now a new option Check EPDs on product updates available in the settings:
When this option is enabled, a reverse index of product -> EPD relations is initialized (depending on the number of existing EPDs in a workspace this could take a while):
Then, when you update a product that is already used in an EPD, you get asked if these EPDs should be also updated:
Version 3.0.0
The main new feature of this version are EPD profiles. An EPD profile defines the life cycle modules and indicators of an EPD scheme. With this, it is possible to work with different EPD schemes in the editor. Also, it is possible to store an URL to a data stock with reference data in a profile with which it is possible to download and update all reference data related to a profile / EPD scheme in the editor.
Version 2.0.2
Fixed issues of milestone 2.0.2