Product Release 13 December 2024

Authentication Revisited

To be future proof and more flexible concerning authentication methods thisgeneral module in the Coreon cloud has been revised. This has no impact on the daily usage of a repository. However, the Login form as well as the navigation to the dashboard, i.e. the repository administration pages, sees an update:

• Select Repository page with its repository cards has been updated, andalso matches the newer Coreon theme (as on www.coreon.com)
• Login, Dashboard, and Select Repository pages support dark mode (following your operating system setting)
• A first step towards UI localisation (for the Login form now for German) hasbeen achieved. Other modules, main UI etc. to follow in 2025.

In daily interaction the most noteworthy change is how to access the dashboard. It is from the one and the same Select Repository page (dashboard.coreon.com alsodirects to this page now).
On the right top of a repository card, there is a “Settings” gear-like icon that brings you to the familiar dashboard.

The dashboard itself did not change in its functionalities, yet it has also an updated theme. Outlook: Longer term we will move most of the dashboard functionality into the main UI and no longer keep it is a separate application.

With this now unified authentication there is one direct benefit: when logging in and navigating from the dashboard to the main UI, there is no need to re-login again.

What do we mean with “future-proof” and “flexible”? With this revision we are prepared to improve in two main areas:

• One Login form, no matter what client application. This module can now berequested from any app, i.e. the browser app, but also CAT plugins, Chrome extensions and other API based developments. This means that for instancealso the plugins can in the near future support Single Sign On.
• Other methods: For instance, modern “passkeys” based authentication ortwo-factor-authentication can be added to this one central module, and allclient applications immediately will benefit from it.

Needless to say, all existing authentication methods continue to work: Coreon credentials, Single Sign On, API Keys.

Export

• PDF Generation: You may know, transformed export data, for instance as a glossary in a readable HTML page, can also be further rendered as a pdf document. But the (open source) engine behind was no longer maintained by the developer community. Thus we replaced it, namely with a so-called “headless” chromium engine.
• XLSX / RDF: (Very) Large exports stopped with a database cursor error. This has been resolved.
• XLSX: When generating an xlsx file the columns in the generated spreadsheet match the properties and languages configured. However, the language columns were also inserted even for properties where no language was configured. This has been improved: the language column is only written for these properties where configured.

Import

We were particularly reviewing the so-called Import Policy Sets, i.e. sets of behaviours how the imported data will be treated in comparison to the already existing data: merging with existing, adding as new etc. In this context we spent a lot of effort to reliably support a re-import of Excel, i.e. xlsx-based, spreadsheets with the goal to support roundtrips, offline changes via first exporting into Excel and then re-importing the changes.
This is a complex matter for terminological data structures but we are happy to now support the import of Coreon-compatible (i.e. previously exported) xlsx files.
An import policy set then combines various rules what do with new terms vs. existing terms, new property values vs. existing values: should they be added, be replaced, or skipped etc.
Concrete changes:

• Import of XLSX files now possible. The format must be “Coreon compliant”, i.e. be based on a previous export.
• Policy sets revised, particularly for XLSX formats.

Mapping XLSX grid data into a hierarchical concept-oriented terminology structure is a complex matter. Please get in touch with us, we are happy to consult you how to deploy XLSX based export-import workflows.

Miscellaneous

Some complementary improvements also made it into this release.

• Filtering operator “contains”: two improvements for the property type multiselect-picklist:
  • Compare the values, not the matching strings of the values: When havingpicklist values where the one value (say for term type a value such as noun) is string-wise contained in the other value (say proper noun), then when the filter rule looked at the one value (term type = “noun”), also the other value passed the filter, because noun is a substring of proper noun. This has been fixed, only whole values are compared.
  • “equals” operator behaved like “contains” operator: Assume you have a property with two multiselect picklist values selected, and the filter rule was configured to evaluate whether the property values “equals” one value, then the filter passed even when not only the desired one but also two or more further values where given (like “contains”). This has been fixed: the operator “equals” now no longer behaves like the “contains” operator.
• Text annotation service: The xliff parser to scan documents was so far optimised to support the bilingual sdlxliff format. Now also the general “plain” .xliff format is supported.
• Access control / role management: when removing a user from a role the change was not saved. This has been fixed.
• Access control: When granting access to concepts by conditions, namely whether a given property is simply not present at all, then the latter was not properly evaluated to allow access. This has been fixed: if an access rule is configured to grant access by the condition that the property is not present,then access to such a concept is now possible.
• Repository configuration: Cannot remove custom breadcrumb. This has been fixed.
• Repository configuration: Apply snapshot shows empty progress. This has been fixed.
• Repository configuration: Cannot change rating rules, had to use workaround via importing a configuration. This has been fixed.