Dictionary Manager

Local dictionaries

Multiple dictionaries can be added and populated to the Registry database, which can be used later during registration or amendment. Dictionaries and also their items can be searched, edited and deleted. To add an item, just click on the [Add item] button and in the opened window just set a name (optionally an item ID can be set as well), then click on [Apply] button.

The item will be automatically added to the list below. If no item Id was given, the system automatically generates one. When you hover over a given item in the list, you will be able to edit it (when clicking on the pencil) or to delete it (when clicking in the trash sign).

{info} Since version 20.19.0 dictionary items are cached for 5 min since last access, thus reducing network traffic especially during bulk registration.

By default, the Compound Registration includes five dictionaries: Chem. Sig. Text (empty), Double bond panel, Geometric Isomerism, Stereocenter panel, and Stereochemistry, which contain items.

The items from the Chem. Sig. Text dictionary can be used as CSTs, which can be retrieved from a drop-down list during registration or amendment. The items in the popup list are present in alphabetical order and they are instantaneously searched when typing.

The items of the Stereochemistry and Geometric isomerism dictionaries currently are present in drop-down lists only on the Registration page of the application. On the Submission page, depending on the "Calculate Stereo Comments" switcher setting, the comment can be either set manually to an arbitrary text or can be calculated using the items of the existing Stereochemistry and Geometric isomerism dictionaries.

The content of the Stereocenter and Double Bond Panels are used on the Submission page for the Stereo Fixer panel.


Dictionary Manager: Local dictionaries

Since version 20.19.0 the IDs of the dictionary items are visible under the name of the items. During item modification the Item ID is visible as read-only value.


Dictionary Manager: Modify dictionary

External dictionaries

Since CompReg version 19.12.0 a dedicated page is added to manage external dictionaries.

Two types of external dictionaries can be accepted by the system:

(A) dictionaries containing Id-value pairs
(B) dictionaries containing only values

{info} If no Id is present in the orginal external dictionary (B), the system will generate one.


A. Ids and values for dictionary items	B. Only values for dictionary items


Adding an external dictionary	Ids and values from a dictionary

Since version 20.19.0 the IDs of the dictionary items are visible under the name of the items.

First, the dictionary should be added, a name should be set and the URL should be provided.

{info} External dictionaries support adding custom headers when querying an external URL.

Then, after applying the dictionary, the fetched values will be listed in the Compound Registration system.

{info} Additional data field improvements: "select" input types can be configured to use the new external dictionaries.

{info} Additional data field improvements: a new validator, "fromList" has been introduced to check if the value of the additional data is amongst the dictionary items. If the value is not present the compound falls to the staging area. This is useful for example to enforce the input of a valid "Project" field.

ID-based fields

Since version 21.3.0 dictionary item identifiers are optionally stored instead of values in order to directly reflect dictionary changes for all business data. There is a new option on the Field Editor page in case of dictionary-based Select fields: ‘Persist Dictionary Ids instead of values’. With the help of this it is possible to create ID-based fields.


Local dictionary example

In case of ID based fields, when a dictionary is not available or an item was deleted from the dictionary, then in the additional data field the IDs will be present not the values and a tooltip will be visible next to the fields: “At least one stored value could not be resolved from the dictionary”.


ID-based field with resolved values	ID-based field with non-resolved values (IDs)

Please find information about how to handle ID-based fields during bulk upload here and about how to search for IDs and Values here. Related API documentation can be found here here.