CKM Release 1.1.2

Date: 20th April 10th August 2010

• Termsets: This release adds Termsets (or Teminology subset) to the resources managed by CKM. The usual CKM functionality for versioning, commenting, documenting, etc. is available for them. If you are interested in termsets, please make sure that you check "Receive notification on new termset" and "Receive notification on updated termset" under Tools/Options in the main menu.
• Translation: All archetypes can now be translated into another language by right-clicking on the archetype in the context menu. This does not require any special rights.
• Reassess status and bulk export: There is a new status called Reassess, which comes into play after a resource has been published. If a change to a resource is committed to the trunk after it has been published, CKM will now check if content state, terminology states, translations states are currently published, and if there have been changes, CKM will suggest to update the respective status of the resource to REASSESS. When  bulk-downloading resource, you can then select if you want the latest revision of the resource or the latest published revision of the resource (Also you can now select the current states of resources you want to bulk export - so you can get e.g. all archetypes that have been published in their published revision.
• Comparison Report: Changes to the display of the Archetype Comparison Report. You can select whether you want the diff or a before-after presentation.
  Changes are displayed in categories with separate headings providing a better overview of what has changed. Also there many individual issues with the comparer have been enhanced/fixed as part of this update, such as e.g. that two DV_DURATIONs were not properly compared previously, support for empty code lists, reporting of cardinality changes at the very first level, comparison of includes and excludes for Archetype Slots, comparsing unconstrained DV_TEMPORALs, etc.
• Archetype Validation Report: Is now displayed immediately when an archetype is impoted or updated. This way, the submitted does not have to finish its submission if the archetype has validation errors that should be fixed beforehand. Also, for specialised archetypes, CKM will now directly link this to the current trunk parent, even if the child archetype is on the branch.
• Archetype view: Some additions to what i displayed in the view of an archetype in CKM. For example, for top-level attributes that don't have a separate tab, these will be displayed with a heading in the data tab.
• Submitting a resource process:When a resouce is submitted to CKM, the corresponding workflow has been enhanced. Fo example, as a next step, the submitter can go to branch to inspect it, update the contributors to this resource, or commit.
• Support for uncommon keys (other than text, description and comment) in the archetype ontology.
• Review Round initiation: For adopters and commenters there is now a context menu to access information about a potential reviewer.
• Archetype lifecycle and CKM status are now synchronised on publishing, deprecating where sensible.
• All emails send out by CKM now have a heade starting with [ckm-openehr] (configurable)

...