By passing an existing (already present in SImA) screen_UUID during the upload job submission, the uploaded data will be stored under the Screen with the matching UUID. (Refer to Signals Image Artist: How do I identify the Screen, Plate or Measurement UUID via the web interface? for details on how to locate the Screen UUID.)
Example syntax:
gemma-client upload --hostname <host> --username <user> <screen_UUID> "<data_format>" <path_to_import_data>
Where:
<host> is the IP or domain name of the SImA server.
<user> is the SImA user account into which the data is to be imported.
<screen_UUID> is the unique identifier for the Screen that the data will be imported into.
<data_format> is the file format being imported, e.g. “Columbus IDX/TIF”, “Harmony IDX/TIF”, etc.
<path_to_import_data> is the path to the dataset that will be imported.
Real-World Example:
gemma-client upload --hostname simaserver.com --username john 85dd7f6f-99e8-4d4a-a51e-32f22c40a7e2 "Harmony IDX/TIF" /mnt/import_data
Where "85dd7f6f-99e8-4d4a-a51e-32f22c40a7e2" is the Screen UUID taken from the SImA web interface.
Note: The password of the mentioned <user> will be requested interactively on job submission. Alternatively, the password can be passed as part of the gemma-client submission using the --password option.
Uploading on behalf of other users:
As of SImA v1.2 it is possible to use the admin user account to upload data on behalf of another user using the --owner-username parameter. In that case the syntax looks like this:
gemma-client upload --hostname <host> --username <admin_user> <screen_UUID> "<data_format>" <path_to_import_data> --owner-username <user>
Where the --owner-username parameter is used to pass the <user> account into which the data should be imported.
Real-World Example:
gemma-client upload --hostname simaserver.com --username admin 6ff75aee-a39a-11ec-8619-02420a000544
"Harmony IDX/TIF" /mnt/import_data --owner-username john
In the above example the admin user uploads the data on behalf of user john.