Scan widget expose sample name metadata and saving directory

Feature Summary

From the scan control widget, it would be beneficial to be able to directly provide metadata such as sample name and/or experiment details and the sub directory where the data should be saved to.

Problem Description

At present the scan control widget only gives the scan type name, but this information is too limited in real experiments where being able to provide directly metadata is needed for better documentation of what the data pertains to. Metadata of the beamline config is scrapped automatically, but we need to be able to provide experimental details such as sample and conditions exposed to.

Use Case

User fields to give metadata such as sample name and/or experiment details that give important information on what the scan is.

Proposed Solution

On the scan control widget add a field for inputting metadata (potentially structured). The metadata required for different experimental methods will vary. I am not sure what the best way is to be able to provide a flexible input as necessitated. But a field for a 'name' is a current minimal requirement. This name would be also beneficial to propagate into the scan queue widget as then it is easier to identify different experimental steps with nominally the same scan type.

Benefits

Metadata on experimental details is required from a FAIR point of view, therefore clear benefit to being able to input that metadata during collection when it is the clearest known. A name for a scan being done allows for easier tracking of experimental steps and when propagated into the scan queue makes it easy to understand the current step being measured (and if the scan types are the same how one might have reorganized the queue)

Alternatives Considered

Impact on Existing Functionality

Adds more visual information to the scan queue, with the drawback of needing more fields exposed on the scan control widget

Priority

Medium but should be there before operation

Attachments

Additional Information

[Provide any additional information that might be relevant to the feature request, such as user feedback, market trends, or similar features in other products]