Integration
Identifiers
 |
| Parent Compound Number (PCN) settings |
PCN / CN /LN / AID settings
| Setting |
Description |
| PCN/CN/LN/AID composition |
Separate with commas how the PCN/CN/LN/AID (Alternative ID) should be built. |
| Prefix |
Characters placed at the beginning of the ID. |
| Separator |
Characters that separate the prefix from the generated sequence. |
| Additional fields |
Add data from additional fields to ID. |
| Increment type |
Choose between a string or number based sequence. |
| Increment start |
The starting value of the generated sequence. This can be a number or character as well. |
| Increment format |
Depending on increment type, use a valid Java formatter syntax (e.g. %d, %s) |
| PCN Allocation limit |
The PCN allocation limit setting used to control the maximum number of PCNs that could be reserved through the SOAP API. It is deprecated since version 19.2.0. It is removed from the UI since version 24.3.2. |
| ID prefix field name |
Name of the Alternative ID. |
{warning} Using different letter casing in identifiers is highly discouraged as it can lead to unexpected behavior of the application depending on the operating system, and table collation settings of the database server.
Alternative IDs
Since version 24.3.4 Secondary (alternative) identifiers can be configured on the Administration page to be assigned to the registered compounds.
 |
| Alternative Identifier (AID) settings |
When the "Alternative ID enabled" switcher is set to true, the "Alternative ID prefix" field appears on the Registration page.
 |
| Alternative ID prefix field |
After the registration the Alternative IDs will be visible in the Registration summary and on the Browse page.
 |
| Registration summary with Alternative IDs |
 |
| Browse page with Alternative IDs |
Since version 25.3.1 the alternative IDs can be generated from the Upload page as well. The alternative ID prefix can be specified in the uploaded file or it can be mapped manually.
 |
| Upload page with Alternative IDs |
LnbRef and Lot Id settings
 |
| LnbRef and LotID settings |
| Setting |
Description |
| Validate LnbRef |
Controls if LnbRef should be validated against the regular expressions during the registration |
| LnbRef regular expressions |
List of regular expressions used to validate the submitted LnbRef |
| Autocomplete empty LnbRefs |
Registration is made even if no LnbRef is provided. After registration LnbRef field will be updated with the LN value. |
| Lot Id required |
Controls if the existence of Lot Id should be validated during the registration |
General settings
 |
| Setting the ID generator |
| Setting |
Description |
DefaultValue |
| Id Generator Class |
Class name of the corporate ID generator |
com.chemaxon.registry.identifier.DefaultSequenceGenerator |
| Id Generator Class |
Class name of the corporate ID generator |
com.chemaxon.registry.identifier.CustomSequenceGenerator |
| ID Sequence Generator |
Method |
DefaultValue |
| DefaultSequenceGenerator |
isTreeDependentLN() |
true |
| DefaultSequenceGenerator |
isTreeDependentCN() |
true |
| CustomSequenceGenerator |
isTreeDependentLN() |
false |
| CustomSequenceGenerator |
isTreeDependentCN() |
false |
Examples for Default ID generators
| ID |
ID composition |
Example |
| PCN |
pcn.cnst, pcn.increment |
CXN100 |
| CN |
pcn.cnst, pcn.increment, cn.increment |
CXN100A |
| LN |
pcn.cnst, pcn.increment, ln.separator, ln.increment |
CXN100-002 |
Examples for Custom ID generators
| ID |
ID composition |
Example |
| PCN |
pcn.cnst, pcn.increment |
CXN100 |
| CN |
pcn.cnst, pcn.increment, cn.separator,cn.str.field* |
CXN100-2 |
| LN |
ln.cnst, ln.increment |
112 |
*cn.str.field stands for a version descriptor and it is a salt/solvate ID
Links
 |
| The setting of the links to third party applications |