Releases: metadatacenter/cedar-project
CEDAR Release 2.6.33
Maintenance release
CEDAR Release 2.6.19
New features / enhancements:
Bugfixes:
- Script to update CEDAR caDSR CDEs and Categories throws error and stops (#1164)
release-2.6.18
New features / enhancements:
release-2.6.17
New features / enhancements:
- Search CDEs by values in the value set: support [pv] search prefix (#1124)
- Implement consistent relevance ranking
- Disable Cypher logging to avoid Redis out-of-memory issues
- Load value sets ontology when running index regeneration task
Version upgrades:
- Upgrade log4j from 2.16.0 to 2.17.1
release-2.6.16
release-2.6.0
release-2.5.42
We are pleased to announce release 2.5.42 of the CEDAR Workbench.
Main enhancements include:
- Development of an "Import" option to translate caDSR Forms into CEDAR templates (#1105).
- Display artifact version in header (#1112).
This release also incorporates a number of usability and documentation enhancements and bug fixes, including:
release-2.5.38
We are pleased to announce release 2.5.38 of the CEDAR Workbench.
Main enhancements include:
- New microservice (ImpEx service) to support import/export operations on CEDAR artifacts. Despite the ImpEx service is available at the REST API level, it cannot be used from the user interface yet. Our next release will include support for importing caDSR XML forms as CEDAR artifacts via the UI (#1105)
This release also incorporates a number of usability and documentation enhancements and bug fixes, including:
CEDAR Release 2.5.11
We are pleased to announce release 2.5.11 of the CEDAR Workbench.
Main enhancements include:
- Front end support for alternate questions (#817)
- Template/element instructions (#1064)
- Support category search in template designer (#1026)
This release also incorporates several number of usability and documentation enhancements and bug fixes, including:
CEDAR Release 2.5.1
This is a patch release that fixes:
(1) A bug that prevented properties from being added to fields. (Issue #1083.)
(2) Bugs that prevented zero or negative values being added to numeric fields in some circumstances. (Issues #1085 and #1086.)
(3) A bug that prevented multiple term removal when arranging field values can no longer be reproduced in this release.(Issue #1090.)