On the Administration page the user, depending on his assigned roles, might import salts/solvates, add salts/solvates, manage dictionaries, undelete compounds, control the user access or manage the database.
When accessing the Administration menu, we are automatically redirected to the first tab: Import salts or solvates.
Add salt or solvate
This section is dedicated for creating and managing the salt/solvate dictionary that is also applied when using the analyze salt/solvate functionality during registration.
In the dictionary each entry contains a name, the adherent chemical structure and a unique ID (salt/solvate ID) which is automatically assigned sequentially to each salt/solvate when adding to the dictionary.
Add Salt or Solvate Tab
Clicking the Administration page of the client application opens up a set of tabs, where the Add salt or solvate tab can be used to manually add salts or solvates to the salt/solvate dictionary. A name field, a radio button for selecting the type (salt or solvate) and a structure drawing area is provided, the salt/solvate ID is automatically generated.
Register a New Salt or Solvate
Once the structure is drawn, the name field is filled and the appropriate type is selected click Add item and a salt/solvate registration dialog with message "<name> has been successfully registered with id <number>" confirms the procedure.
If the given name was already entered into the dictionary then a warning window containing "The name <name> already is present in the database." message is returned. If the name does not exist yet but the provided structure can be found in the salt/solvate dictionary then "The structure is already registered as <name>." message appears. However, clicking [Continue with registration] button, it is allowed to register a structure and/or name already present in the database (i.e. you can register a structure both as salt and solvate as well).
Multiple dictionaries ( figure Admin 5 ) 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 plus sign, type the item, then click on [Add] button. The item will be automatically added to the list below. 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).
By default, the Compound Registration includes five dictionaries: Chem. Sig. Text (empty), Double bond panel, Geometric Isomerism, Stereocenter panel and Stereochemistry, which contain some sample 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.
Figure Admin 5. The Dictionary manager page
Using this menu the access of the users on the Registration system can be controlled. Users belong to group(s). Predefined groups can be used or new ones can be created by adding or removing different roles. When projects are created, user(s) with permission(s) should be added to it.
In the Access control menu three tabs: Users, Groups and Projects are available where users, groups and projects can be added, removed or updated.
Role based access of functionalities
Groups, regardless if they are present in a predefined list or they were just created, can have different roles. Example of roles: autoregister; view, list, modify submissions in the staging area; ability to register from the staging area; ability to read the amendment page, to amend etc. E.g. a user who belongs to the Read only group, by default, will have the role to list and view submissions in the staging area, assign and unassign submissions in staging, read the amendment page, search for salts and solvates, view the audit, search for structures, export search results and self administration. The user who belongs to the Read only group will not be able to modify already registered compounds. For a more detailed role description check the Groups section.
Project based access of data
User(s) can have different permission(s) within projects. Currently four types of permissions are available: write, write own, read and read own. The write permission includes the write own (which contains the read own) and the read permission. Therefore a user having write permission within a project is automatically having all the permissions, so there is no need to set the other permissions too. A user having read / write own permission is automatically having also the read own permission.
If project based access control is set, registration, amendment and search actions can be performed based on projects considering the user permission(s). E.g project A16 is created having two users as members: reg1 user having write permission and chemist4 having read own permission. Logged in as chemist4 cannot register lots within project A16. As reg1 user registrations are allowed within project A16: a lot having reg1 as submitter and another lot having chemist4 as submitter are registered under the same PCN. Then, as chemist4 on the Amendment page and Search pages only one lot of the tree should be visible where previously two lots were registered. As chemist4 (who belongs to "Registrar no restriction" group) on the Amendment page the amendment of the owned lot should not be possible, since the chemist4 is having only read own permission. As reg1 (who belongs to "Registrar" group), it should be possible to amend both lots, since this user is having all the roles.
List of the Existing Users
The Users tab contains a list of the existing users. The list of users is displayed along with the groups where they belong to. The associated roles are also listed. E.g. "admin" user is part of a group called "super" and has all the available roles. The different roles for each group are listed below. You can filter the Users list by selecting a group or a role in the Filter drop-down list.
Add a new user
It is also possible to add new users by clicking on the [Add new user] button. In this case you need to provide a username and password and need to select at least one group where the new user should belong to, then first click on the Add user to group then [Create user] buttons.
A set of predefined groups are available immediately after the deployment, but certainly new groups can also be defined. The default groups with the default roles are:
This group has the role to perform autoregistration and self administration.
This group has the role to perform bulkload, to register with a specific ID, allocate specific PCNs, to search structures and export the search results, to export the regsys DB content to a downstream DB and self administration.
This group has the role to list and view submissions in the staging area, assign and unassign his own submissions in staging, read the amendment page with the audit, search for structures and salts/solvates, view the audit, export search results and self administration.
This group has the role to autoregister, list, view and modify submissions in staging, register from the staging, bulk register (register all) from the staging, assign and unassign submissions in staging, read the amendment page, amending a structure, lot, version and parent level amendment, view the audit, manual version correction, amending the molecular weight, delete and undelete ID's, rename and swap LnbRef, move lot, amend restriction level, update the layout of the structure, bulk restriction change, search for structures and salts/solvates, export search results, modify the dictionaries, modify the switchers and self administration.
Registrar - No Amendment
This group has the role to autoregister, list, view and modify submissions in staging, register from the staging, bulk register (register all) from the staging, assign and unassign submissions in staging, read the amendment page, view the audit, manual version correction, search for structures and salts/solvates, export search results and self administration.
Registrar - No Restriction Change
This group has the role to autoregister, list, view and modify submissions in staging, register from the staging, bulk register (register all) from the staging, assign and unassign submissions in staging, read the amendment page, amending a structure, lot, version and parent level amendment, manual version correction, amending the molecular weight, delete and undelete ID's, rename and swap LnbRef, move lot, update the layout of the structure, view the audit, search for structures and salts/ solvates, export search results and self administration.
This group has the role to list, view and delete submissions from the staging, assign and unassign submissions in staging, add salts and solvates to the DB, view the audit, bulkload, bulk restriction change, clear the DB, modify the dictionaries, export the regsys DB content to a downstream DB and self administration.
This group has all the available roles.
This group has user and self administration role and is able to modify the dictionary roles, furthermore, he has the ability to set the project based access control (read projects, if he has permission, and to modify projects with the user permissions).
Projects can be specified either during autoregistration or when registering the submission from the staging area. Projects can be also created also from the Administration page, Access control menu, Projects tab. Here, while creating the project, the users who can have access to it (with different permissions), can be added. The user's permissions are: read, write, read_own and write_own. For more details about the permissions please consult the Project based access of data section.
Projects can be filtered and searched or all projects can be displayed.
Available in test version only, not available in production use!
The content of the database can be cleared using the [Clear database] button. The operation cannot be restored!
After using the Clear option you will loose all compounds from your registry DB, all the additionally stored data and also the salts/solvates from the salt/solvate DB. After using this option, all user names and groups will be kept. After deleting the DB, the new registrations will receive their PCN's according to the predefined rules starting again from the first available value of the counters (e.g. CXN1/CXN1A).
The content of the database can be cleared and re-deployed with the [Deploy database] button. The operation cannot be restored!
After using this option, all user names and groups will be lost, even the one who initiated the deployment, except for the "admin" user and the predefined groups. E.g. you can deploy the database if you are logged in as a user, who belongs to the registry administrator group, but after the deployment the only remaining user will be the "admin" which belongs to the super group.