Manage Facility Users

Overview

This page describes how facility managers can manage users for NDTS, the application that automatically harvests data from NMR spectrometers into the NAN archive. NDTS includes a graphical interface (NDTS-GUI) that runs on each spectrometer workstation and allows users to view and change harvesting settings, including the selection of a NAN user to associate with each dataset.

User Mapping Overview

Each spectrometer workstation has its own set of local users (i.e., Linux/Windows accounts). For proper data attribution, NDTS provides a mechanism to map each local workstation user to a specific NAN user account. When such a mapping exists, NDTS will automatically select the appropriate NAN user in the NDTS-GUI.

Facility managers can control whether users are allowed to:

• Change the NAN user associated with an experiment.
• Change whether data from their account is harvested.

User behavior can be configured individually or by email domain to simplify administration.

Managing the User Table

User mappings and behavior settings are defined in a user management table accessible through the Manage Spectrometer Users page.

The table includes the following columns:

Column	Description
Workstation User	The local user account on the spectrometer workstation. Optional if only a NAN user is being defined.
NAN User	The account on the NAN portal to which the data will be attributed. Optional if behavior is being defined for an unmapped workstation user.
Transport Default	Whether NDTS should Capture or Exclude data by default for this user.
Can Change Collection Settings	Yes allows the user to enable/disable data harvesting from NDTS-GUI; No locks the setting.
Can Change Username	Yes allows the user to change the selected NAN user in NDTS-GUI; No disables this option.

• Each row can be deleted using the trash icon.
• New users can be added using the Add User button.
• The table supports sorting by any column.
• A Search Users field allows quick filtering.
• Pagination is available for large user lists.

Email Domain Auto-Discovery

To simplify management, administrators may specify one or more email domains (e.g., university.edu). Any user with a verified NAN account matching that domain will automatically appear in the user list within NDTS-GUI. This avoids the need to enter each user individually.

However, for finer control (e.g., setting behavior flags or mappings), users should be added explicitly to the table.

Unknown Users

Administrators can configure NDTS behavior when a user not in the table launches an acquisition:

• Harvesting may be enabled or disabled by default.
• The NDTS-GUI will display limited options depending on the global policy and facility preference.

Usage Examples

Scenario	Configuration
Exclude a user from harvesting	Workstation User: pfizer NAN User: (leave blank) Transport Default: Exclude Can Change Collection Settings: No Can Change Username: No	used for scenarios where a user should never have their data harvested, such as a commercial entity
Force harvesting	Workstation User: mark NAN User: mmaciejewski Transport Default: Capture Can Change Collection Settings: No Can Change Username: No	used for scenarios where there is a 1:1 correspondence between the local workstation user and the NAN user and when the PI wants harvesting to always be on.
Standard user with flexibility	Workstation User: irina-lab NAN User: iborya Transport Default: Capture Can Change Collection Settings: Yes Can Change Username: Yes	used for a scenario where a shared account is used on the NMR spectrometer workstation. There is a default NAN user associated with the workstation user, but users are allowed to change the NAN user to whomever in the lab is running the experiments.
unspecified user	Workstation User: (leave blank) NAN User: (leave blank) Transport Default: Capture Can Change Collection Settings: Yes Can Change Username: Yes	with both the workstation user and NAN User being left blank, this tells NDTS how to handle cases where the user is completely unspecified. Best practices would be to try and avoid that scenario by always having the local workstation users defined, but defining how to handle unspecified users is a good practice to ensure you have the harvesting behavior you want in this event. In this example

Summary

This user management system allows flexible yet precise control over who can use NDTS, how data is harvested, and which NAN user identities are associated with datasets. It balances convenience (via domain-based auto-discovery) with granular configuration (via explicit mappings and permissions).