The release of CKM 1.4.0 features some major new additions to the functionality of CKM. It also improves on many details in CKM and fixes a number of bugs.
...
When upgrading, the following new configuration items may be set.
| editor-description | A description used to describe an editor of this CKM instance or the CKM instance itself - e.g. "openEHR" for openEHR Editor or openEHR CKM. Could e.g. be Nehta, Norwegian, UK, ... |
| publisher-organisation | The organisation of this CKM. To be used in an archetype, e.g. openEHR Foundation or Nehta |
| publisher-namespace | The namespace of the publisher, e.g. org.openEHR |
| licence | The default licence for resources in this CKM, e.g. Creative Commons SA <https://creativecommons.org/licenses/by-sa/3.0/> |
| max-primary-assets | A max. number of primary assets in this CKM instance |
| resource-type-to-activate-in-resources-explorers | By default, the archetypes tabs are activated on loading on the left hand. Can be any of archetype, template, termset. |
V0 Migration Decision
After upgrading, any unpublished archetypes may be migrated to v0 archetypes and the other_details metadata added as required.
...
- active-branch-handling: What to do if the archetype has an active branch. The active branch can be rejected or ignored when updating to the new revision numbering. Alternatively, the archetype can be skipped completely.
(reject-active-branches, ignore-active-branches, skip-archetype)
- log-messageThe message: The log message to be used for updated archetypes.
...