| Literature DB >> 35130839 |
Luis Kuhn Cuellar1, Andreas Friedrich1, Gisela Gabernet1, Luis de la Garza1, Sven Fillinger1, Adrian Seyboldt1, Tobias Koch1, Sven Zur Oven-Krockhaus2, Friederike Wanke2, Sandra Richter2, Wolfgang M Thaiss3, Marius Horger4, Nisar Malek4, Klaus Harter2, Michael Bitzer4, Sven Nahnsen5,6.
Abstract
BACKGROUND: As technical developments in omics and biomedical imaging increase the throughput of data generation in life sciences, the need for information systems capable of managing heterogeneous digital assets is increasing. In particular, systems supporting the findability, accessibility, interoperability, and reusability (FAIR) principles of scientific data management.Entities:
Keywords: Data integration; Data management infrastructure; Distributed systems; Imaging; Metadata models; Omics; Service oriented architecture
Mesh:
Year: 2022 PMID: 35130839 PMCID: PMC8822871 DOI: 10.1186/s12859-022-04584-3
Source DB: PubMed Journal: BMC Bioinformatics ISSN: 1471-2105 Impact factor: 3.169
Fig. 1Activity diagram of the ETL process for imaging data. The diagram indicates which tasks are executed on each of the system components involved in the image registration process. A The openBIS sample code in this step was previously generated by the Project Wizard. B Image files are parsed by Bio-formats, providing compatibility with a large collection of imaging file formats. C Bio-formats extracts metadata from image files and maps it to the OMERO metadata model. D Save tabular metadata as key-value pairs associated with the previously registered images
Fig. 3The Image Viewer application while accessing the previously uploaded confocal images. A View of the Image Viewer application. B The 5D image viewer of the OMERO.web server provides a web-based imaging interface with functionality to visualize 5D images and allows easy navigation in the spatial, temporal and channel dimensions (red boxes). C The OMERO.iviewer application allows web-based annotation of ROIs, which can be easily stored in the OMERO database
Fig. 2Registration of the Arabidopsis RUP experiment. A Colocalization experiment of RUP1-GFP and RUP2-GFP and CO-RFP using confocal microscopy data, adapted from [18]. B The Project Wizard application during project creation. C Summary of the project metadata in the Project Browser
Fig. 4Schematics of the data transfer procedure from the data acquisition facilities. Data and metadata import was achieved via data transfer systems: a Datamover instance in the imaging and medical genetics facilities (openBIS, https://wiki-bsse.ethz.ch/display/DMV/Home), or via the in-house developed dync command line tool (https://github.com/qbicsoftware/dync). The data was then handled on an incoming server in an ETL process and registered in the openBIS and OMERO platforms
Fig. 5Data availability for the HCC clinical study use case. A Schematics of the datasets collected for the clinical trial. Radiological imaging data (CT-perfusion (CT), CT-guided biopsy (CTP), MRI-PET (MP) with FDG and Choline tracers) and multi-omics data (metabolomics, genomics and transcriptomics) are integrated into the openBIS metadata model. All data is available to the project partners through our portal. The graph representation allows a quick visualization of the experimental design [22, 23]. B The image viewer portlet offers an overview of the available imaging data for the project, and provides access to selected metadata. The user is also provided with a link to a full image viewer for the reconstructed tomograms. C Sample images of MRI (left) and CT (right) of the abdomen for one of the patients. If tumor annotations by the radiologists are available, they can be displayed as an extra channel (here in red). D Summary of the tumor genomics findings for all patients with available genomics data (N = 16), selected mutated genes are displayed
Fig. 6Component diagram of the proposed data management infrastructure for omics and imaging data, indicating the interaction of all major software components. A Users can perform a set of data management operations, including uploading new imaging data into a previously created project, by copying it into a dropbox folder. B The qPortal platform as a frontend, containing portlet applications that connect to the backend via connector components (openBIS and OMERO clients). C The backend of the proposed system comprises two major components, the openBIS and OMERO servers