Commit 83cca5a6 authored by Timm Schoening's avatar Timm Schoening
Browse files

Update README.md

parent b1a486a1
......@@ -27,3 +27,7 @@ Processes and entities can be accompanied by one or many documentation entities.
### Status information
![MareHub AG Videos/Images SOP documentation: project workflow with status information](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/standard-operating-procedures/-/raw/master/SOPs/graphics/AGVI_SOP-documentation-5-project-status.jpeg "MareHub AG Videos/Images SOP documentation: project workflow with status information")
Of course, all SOPs should represent the best-case scenario and of course all their components should be in place and work as described. But as the marine imaging community is still developing their best-practices, some of the elements of SOPs are still under development. In that case, this is color-coded in the workflow figures: either there is no solution for the entire concept (of a process, entity, infrastructure or documentation) or there is one but it is not commonly supported, operated, executed or maintained.
# Cheatsheet of the graphical elements
![MareHub AG Videos/Images SOP documentation: cheatsheet of the graphical elements](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/standard-operating-procedures/-/blob/master/SOPs/graphics/MareHubSOP_graphics_cheatsheet.png "MareHub AG Videos/Images SOP documentation: cheatsheet of the graphical 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