...
- Termset Reviews cannot be initiated (CKM 1.3.2)
- Release Set Exporter doesn't honour trailing whitespace for XML archetypes exported as Secondary assets (CKM 1.3.2)
- Generic Transformer doesn't honour trailing whitespace for Archetype XML generation (CKM 1.3.2)
- XML Serialiser must serialise the translations section (CKM 1.3.2)
- DV_Ordinal value element of symbol must be serialised (CKM 1.3.2)
- XMLSerialiser creates DV_INTERVAL<_DV_QUANTITY> (CKM 1.3.2)
- Users Select Panel: If in window, button may be barely visible (CKM 1.3.2)
- Select Users Advanced Tab: Only the first Subclass radio option is visible (CKM 1.3.2)
- Select Users Advanced Tab: After search the Select Users button is only half visible (CKM 1.3.2)
- XMLSerialiser should serialise assumed value of a DVCodedText (CKM 1.3.2)
- DVDuration value may not be preserved properly for 0 values (CKM 1.3.2)
- Deleting Termset from CKM should properly unregister the query from OTS as well (CKM 1.3.2)
- Registering termset with non-standard terminology fails (CKM 1.3.2)
New Configuration
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.
Depending on the CKM, this can be a bulk conversion
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
:value ignore-active-branches
:value skip-archetype
:log-message (type=string, max-occurs=1) The log message to be used for updated archetypes.