Before installing one or both of these registration applications, users need to assess their security requirements and determine which security model will best fit their needs.

Security is provided in the schema and it can be applied to any required attribute or not at all. When security is configured, that attribute is selected as the assessment point to make a record available or not. The value of the attribute is used to determine which groups of users can see which records.

The available security options are:

No Security - users can access all records (unless prevented by permissions).

Single-cardinality - only a single value can be provided for the security attribute. (e.g., a lot or concept can only ever be assigned to a single ‘project’)

Multi-cardinality - Multiple values are permitted for the security attribute (e.g., lots and concepts can be assigned to multiple ‘projects’)

More details about these settings and security configuration can be found in the installation guide of these applications.

After completing the installation, users can confirm the security setting that they have chosen during the installation as follows: Log in to the GEMS Metadata Editor > Admin > Parameters > select the proper Data Source, and look at the value of the install:security parameter. This will show a value of 0 for No Security, 1 for Single Cardinality, and 2 for Multiple Cardinality.

Note that the following permissions should be assigned to the user group in the Foundation Hub Admin and Settings page to control access to some functionality of the GEMS Metadata Editor:
Platform/GEMS/MetadataEditor
Platform/GEMS/DataViewer/View
Platform/GEMS/DataViewer/Edit