Figure 1
Logical structure layers of openBIS containing the Work- or Data space, Projects, Collections, Object Types (OBJs), and attached Datasets (red). This figure is adapted from Barillari et al. (2016).
Figure 2
The hierarchical structure of the parents-children relation in action. Every object type (for example Sample, Experimental Step, and Publication) is child and parent depending on its ancestry relation. In our example, Publication P is child of every other object type like Instrument I or Experimental Step X.
Figure 3
The current joint venture project within CRC 1411 involves collaboration between synthesis (project process related to the red arrow) and theoretical simulation (project process related to the red arrow). The ‘real’ scheme (hierarchy graph) in (a) provides a comprehensive representation of complete process workflows during this cooperative project. For better clarity and visibility, we have filtered and shortened (a), while (b) illustrates the proposed structure of our CRC in relation to the joint venture project between our synthetic (red arrow) and theory (violet arrow) research groups. Both the proposed (b) process structure, and the implemented (a) structure, exhibit similarities even though (a) is more complex overall.
Figure 4
The depicted view represents the graphical user interface of openBIS from the researcher’s perspective. The top-left section clearly displays the hierarchical folder structure shown in Figure 1, while the right side allows the researcher to fill in relevant metadata and to link it to the corresponding raw or processed data, as shown in the bottom-left part.