Manage Facility Users - Revision history

Mmaciejewski: /* Unknown Users */

2025-06-23T15:23:16Z

Unknown Users

← Older revision		Revision as of 15:23, 23 June 2025
Line 46:		Line 46:
	However, for finer control (e.g., setting behavior flags or mappings), users should be added explicitly to the table.		However, for finer control (e.g., setting behavior flags or mappings), users should be added explicitly to the table.

	== Unknown Users ==		== Unknown (unspecified) Users ==

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

Mmaciejewski at 16:41, 10 June 2025

2025-06-10T16:41:01Z

← Older revision		Revision as of 16:41, 10 June 2025
Line 1:		Line 1:
			{{FacilityDashboardNavigation}}

	== Overview ==		== 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.		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.

Mmaciejewski: /* Usage Examples */

2025-06-10T13:51:00Z

Usage Examples

← Older revision		Revision as of 13:51, 10 June 2025
Line 85:		Line 85:
	* Can Change Collection Settings: '''Yes'''		* Can Change Collection Settings: '''Yes'''
	* Can Change Username: '''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
	\|}		\|}

Mmaciejewski: /* Usage Examples */

2025-06-10T13:02:46Z

Usage Examples

Mmaciejewski: /* Usage Examples */

2025-06-10T12:55:04Z

Usage Examples

← Older revision		Revision as of 12:55, 10 June 2025
Line 54:		Line 54:
	{\| class="wikitable"		{\| class="wikitable"
	! Scenario !! Configuration		! Scenario !! Configuration
			!
	\|-		\|-
	\| '''Exclude a ~~commercial~~ user from harvesting''' \|\|		\| '''Exclude a user from harvesting''' \|\|
	* Workstation User: <code>~~com_user~~</code>		* Workstation User: <code>pfizer</code>
	* NAN User: (leave blank)		* NAN User: (leave blank)
	* Transport Default: '''Exclude'''		* Transport Default: '''Exclude'''
	* Can Change Collection Settings: '''No'''		* Can Change Collection Settings: '''No'''
	* Can Change Username: '''No'''		* Can Change Username: '''No'''
	~~→ NDTS will~~ never ~~harvest~~ data ~~from this user.~~		\|used for scenarios where a user should never have their data harvested, such as a commercial entity
	\|-		\|-
	\| '''Force harvesting''' \|\|		\| '''Force harvesting''' \|\|
	* Workstation User: <code>~~trainee1~~</code>		* Workstation User: <code>mark</code>
	* NAN User: <code>~~pi_user~~</code>		* NAN User: <code>mmaciejewski</code>
	* Transport Default: '''Capture'''		* Transport Default: '''Capture'''
	* Can Change Collection Settings: '''No'''		* Can Change Collection Settings: '''No'''
	* Can Change Username: '''No'''		* Can Change Username: '''No'''
	~~→ Data will always be harvested~~ and ~~attributed to~~ the PI.		\|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 one.
	\|-		\|-
	\| '''Standard user with flexibility''' \|\|		\| '''Standard user with flexibility''' \|\|
	* Workstation User: <code>~~user123~~</code>		* Workstation User: <code>irina-lab</code>
	* NAN User: <code>~~user123@university.edu~~</code>		* NAN User: <code>iborya</code>
	* Transport Default: '''Capture'''		* Transport Default: '''Capture'''
	* Can Change Collection Settings: '''Yes'''		* Can Change Collection Settings: '''Yes'''
	* Can Change Username: '''Yes'''		* Can Change Username: '''Yes'''
	~~→ Default harvesting~~ is ~~enabled~~, but the user ~~can turn it off or switch identity if permitted~~.		\|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'''
			\|
	\|}		\|}

Mmaciejewski: /* Usage Examples */

2025-06-09T20:38:29Z

Usage Examples

← Older revision		Revision as of 20:38, 9 June 2025
Line 63:		Line 63:
	→ NDTS will never harvest data from this user.		→ NDTS will never harvest data from this user.
	\|-		\|-
	\| '''Force harvesting ~~for a PI’s trainee~~''' \|\|		\| '''Force harvesting''' \|\|
	* Workstation User: <code>trainee1</code>		* Workstation User: <code>trainee1</code>
	* NAN User: <code>pi_user</code>		* NAN User: <code>pi_user</code>

Mmaciejewski: /* User Mapping Overview */

2025-06-09T20:36:55Z

User Mapping Overview

← Older revision		Revision as of 20:36, 9 June 2025
Line 4:		Line 4:
	== User Mapping Overview ==		== User Mapping Overview ==

	Each spectrometer workstation has its own set of '''local users''' (i.e., ~~UNIX~~ 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.		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:		Facility managers can control whether users are allowed to:

Mmaciejewski: /* Overview */

2025-06-09T20:36:13Z

Overview

← Older revision		Revision as of 20:36, 9 June 2025
Line 1:		Line 1:
	== Overview ==		== 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 ~~'''[[User Roles and Permissions\|~~NAN user~~]]'''~~ to associate with each dataset.		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 ==		== User Mapping Overview ==

Mmaciejewski: /* Summary */

2025-06-09T20:35:24Z

Summary

← Older revision		Revision as of 20:35, 9 June 2025
Line 1:		Line 1:
	= ~~Managing Spectrometer 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 '''[[User Roles and Permissions\|NAN user]]''' to associate with each dataset.
	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 ==		== User Mapping Overview ==
Line 84:		Line 83:

	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).		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).

	~~For details on installing and launching the NDTS-GUI, refer to the [[NDTS-GUI\|NDTS GUI documentation]].~~

Mmaciejewski: Created page with "= Managing Spectrometer Users = 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 wo..."

2025-06-09T20:32:41Z

Created page with "= Managing Spectrometer Users = 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 wo..."

New page

= Managing Spectrometer Users =

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., UNIX 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:

{| class="wikitable"
! 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., <code>university.edu</code>). 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 ==

{| class="wikitable"
! Scenario !! Configuration
|-
| '''Exclude a commercial user from harvesting''' ||
* Workstation User: <code>com_user</code>
* NAN User: (leave blank)
* Transport Default: '''Exclude'''
* Can Change Collection Settings: '''No'''
* Can Change Username: '''No'''
→ NDTS will never harvest data from this user.
|-
| '''Force harvesting for a PI’s trainee''' ||
* Workstation User: <code>trainee1</code>
* NAN User: <code>pi_user</code>
* Transport Default: '''Capture'''
* Can Change Collection Settings: '''No'''
* Can Change Username: '''No'''
→ Data will always be harvested and attributed to the PI.
|-
| '''Standard user with flexibility''' ||
* Workstation User: <code>user123</code>
* NAN User: <code>user123@university.edu</code>
* Transport Default: '''Capture'''
* Can Change Collection Settings: '''Yes'''
* Can Change Username: '''Yes'''
→ Default harvesting is enabled, but the user can turn it off or switch identity if permitted.
|}

== 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).

For details on installing and launching the NDTS-GUI, refer to the [[NDTS-GUI|NDTS GUI documentation]].

← Older revision		Revision as of 13:02, 10 June 2025
Line 53:		Line 53:

	{\| class="wikitable"		{\| class="wikitable"
	! Scenario !! Configuration		! style="white-space: nowrap;" \| Scenario !! style="white-space: nowrap;" \| Configuration !! style="white-space: normal;" \|
	!
	\|-		\|-
	\| '''Exclude a user from harvesting''' \|\|		\| style="white-space: nowrap;" \| '''Exclude a user from harvesting''' \|\| style="white-space: nowrap;" \|
	* Workstation User: <code>pfizer</code>		* Workstation User: <code>pfizer</code>
	* NAN User: (leave blank)		* NAN User: (leave blank)
	* Transport Default: '''Exclude'''		* Transport Default: '''Exclude'''
	* Can Change Collection Settings: '''No'''		* Can Change Collection Settings: '''No'''
	* Can Change Username: '''No'''		* Can Change Username: '''No'''
	\|used for scenarios where a user should never have their data harvested, such as a commercial entity		\| used for scenarios where a user should never have their data harvested, such as a commercial entity
	\|-		\|-
	\| '''Force harvesting''' \|\|		\| style="white-space: nowrap;" \| '''Force harvesting''' \|\| style="white-space: nowrap;" \|
	* Workstation User: <code>mark</code>		* Workstation User: <code>mark</code>
	* NAN User: <code>mmaciejewski</code>		* NAN User: <code>mmaciejewski</code>
	* Transport Default: '''Capture'''		* Transport Default: '''Capture'''
	* Can Change Collection Settings: '''No'''		* Can Change Collection Settings: '''No'''
	* Can Change Username: '''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 ~~one~~.		\| 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''' \|\|		\| style="white-space: nowrap;" \| '''Standard user with flexibility''' \|\| style="white-space: nowrap;" \|
	* Workstation User: <code>irina-lab</code>		* Workstation User: <code>irina-lab</code>
	* NAN User: <code>iborya</code>		* NAN User: <code>iborya</code>
	* Transport Default: '''Capture'''		* Transport Default: '''Capture'''
	* Can Change Collection Settings: '''Yes'''		* Can Change Collection Settings: '''Yes'''
	* Can Change Username: '''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.		\| 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.
	\|-		\|-
	\|		\| style="white-space: nowrap;" \| '''unspecified user''' \|\| style="white-space: nowrap;" \|
	\|		* Workstation User: (leave blank)
	\|		* NAN User: (leave blank)
	\|-
	\|'''unspecified user'''
	\|
	* Workstation User: (leave blank)
	* NAN User: (leave blank)
	* Transport Default: '''Capture'''		* Transport Default: '''Capture'''
	* Can Change Collection Settings: '''Yes'''		* Can Change Collection Settings: '''Yes'''
	* Can Change Username: '''Yes'''		* Can Change Username: '''Yes'''
	\|		\|
	\|}		\|}