Commit a1d3ae9a authored by Timm Schoening's avatar Timm Schoening
Browse files

Update MareHub_AGVI_SOP_image-curation.md

parent a81d2fe0
......@@ -51,5 +51,5 @@ Curation of the image data is split in two parts here. The goal of the process i
### Image data curation (step 5/5)
for one single deployment - a close-up of the image data management workflow
![Image curation SOP image curation 2 by the MareHub AG Videos/Images](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/standard-operating-procedures/-/raw/master/SOPs/graphics/AGVI_SOP-documentation-image-workflow-details-6-image-curation.jpeg "Image curation SOP image curation 2 by the MareHub AG Videos/Images")
![Image curation SOP image curation 2 by the MareHub AG Videos/Images](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/standard-operating-procedures/-/raw/master/SOPs/graphics/AGVI_SOP-documentation-image-workflow-details-6-image-curation.png "Image curation SOP image curation 2 by the MareHub AG Videos/Images")
Once the curated image data is ready, two additional processes can create the remaining required information for the iFDO and pFDO: i) scale determination provides the resolution of the images (i.e. the size of one pixel in SI units) and ii) file hashing provides a value to check the file integrity later on. All the data and process documentation entities can now be bundled into the iFDO and pFDO. During this process provenance information on the processing itself is recorded and published alongside the image metadata. iFDOs enable FAIRness of images and have a use of their own (thus should be shared through OSIS) as well as facilitate using the image data (thus should be shared through Elements).
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment