BioReg users might be interested in updating a lot record and changing the value of an identifying attribute, e.g., update a siRNA lot and change the value for the identifying attribute “Oligo Modified Sequence”. The new value for the identifying attribute might sometimes match with the value for the same attribute of an existing record. In such cases, this update process will move the lot from the old concept to another existing concept. After successful update, users will see the expected Moniker ID in BioReg web client, but if they use the Retrieve Entity component to look at the data for this updated record, they will notice that the Moniker ID is not correctly reassigned, i.e., it will still show the previous Moniker ID. 

BioReg Developers looked into this issue and explained the observation as follows: “The property /GemsDocument/Gems/moniker is not stored in the GEMS schema, it is an artifact of the GEMS caching. It was generated by the legacy product and should not be used. More recent versions of registration have been generating it for legacy support, but this is no longer supported in the current product.”

BioReg users are advised to make a note of this change and not to use or rely on Moniker ID in recent versions of the application.

BioReg product team is also currently in the process of reviewing and removing references to Moniker from the BioReg Configuration and Developer guides.