Merge remote-tracking branch 'refs/remotes/origin/develop' into feature/release-notes-1.62

# Conflicts:
#	docs/user-guide/doc-odm-user-guide/doc-odm-user-guide/images/data-model.png

Author: MikhailAf

docs/assets/data_model.svg

@@ -75,7 +75,7 @@ Additional optional parameters:
 ## Data model
 
 The script supports several data models:
-![Data Model](uploading-study/data-model.png)
+![Data Model](../../../../assets/data_model.svg)
 
 - Study - Samples - Omics data:
     - the script uses this data model if no parameters are specified for libraries or preparations loading;

docs/tools/odm-sdk/terminal/study/uploading-study.md

@@ -41,6 +41,17 @@ GET `transformations/images`. Endpoint response example:
     "output_formats": [
       "samples"
     ]
+  },
+    {
+    "name": "metadata-basic",
+    "version": "0.0.3",
+    "description": "Basic converter from attachment to metadata",
+    "input_formats": [
+      "csv"
+    ],
+    "output_formats": [
+      "samples"
+    ]
   },
   {
     "name": "metadata-basic",
@@ -81,7 +92,7 @@ Let’s create configuration that allows image to place transformed `CSV` file t
   "data": {
     "source": "csv",
     "destination": "samples"
-    },
+  },
   "description": "Configuration which allows you to transform csv file into Sample group",
   "name": "csv to samples"
 }
@@ -136,26 +147,28 @@ Initial request body:
 
 ```json
 {
-  "attachment_accession": "string",
+  "input_accessions": ["string"],
   "configuration_id": 1,
   "image_reference": {
     "name": "string",
     "version": "string"
   },
-  "volume_size": 30
+  "volume_size": 30,
+  "dry_run": false
 }
 ```
 Fill in information about attachment genestack accession, configuration, image name and version:
 
 ```json
 {
-  "attachment_accession": "GSF016786",
+  "input_accessions": ["GSF016786"],
   "configuration_id": 294862386,
   "image_reference": {
     "name": "metadata-basic",
-    "version": "0.0.2"
+    "version": "0.0.3"
   },
-  "volume_size": 30
+  "volume_size": 30,
+  "dry_run": false
 }
 ```
 
@@ -175,14 +188,15 @@ To check the status of the Job use GET `transformations/jobs/{id}` endpoint:
   "$schema": "https://odm-processors-controller:8080/schemas/TransformationJobFields.json",
   "image_reference": {
     "name": "metadata-basic",
-    "version": "0.0.2"
+    "version": "0.0.3"
   },
-  "attachment_accession": "GSF016786",
+  "input_accessions": ["GSF016786"],
   "configuration_id": 294862386,
   "volume_size": 30,
+  "dry_run": false,
   "create_time": "2025-10-31T12:28:57Z",
   "status": {
-    "state": "TERMINATED"
+    "state": "DONE"
   }
 }
 ```

docs/tools/odm-sdk/terminal/study/uploading-study/data-model.png

@@ -47,7 +47,7 @@ The correct order of linking follows the system logic and available endpoints:
 - **Attached files** are linked directly to a **Study**
 
 
-![image](doc-odm-user-guide/images/data-model.png)
+![image](../../assets/data_model.svg)
 ## Data Loading via APIs
 To load the data via APIs each entity is created via a separate endpoint specific for
 this data type. Then they are sequentially linked in the Integration layer.

docs/user-guide/doc-odm-user-guide/attachment-transformation.md

@@ -1,4 +1,4 @@
-mkdocs-material==9.7.1
+mkdocs-material==9.7.3
 mike==2.1.3
 
 # https://github.com/squidfunk/mkdocs-material/issues/3085#issuecomment-933373590