We provide the O2A framework for AWI's research but also to the earth and environment community as long-term "software as a service". You can use the O2A services as they are, especially in project-contexts where AWI is involved. O2A is an ecosystem of different integrated components and tools aligned with AWI's technical infrastructure. Of course, technical implementation is based on this infrastructure.

This page describes aspects of collaboration in terms of metadata and data content, offered services as well as detailed software development of O2A components.

overview

• which components exists, what is the focus of a component
• how each component is integrated with others
• what I have to do, what does the system by itself
• links to sub-chapters
• → check information and clearness of component descriptions

Different models

• scientific requirements / feedback
• extensions

Formal contracts for contributions vs. terms of service

• merges with other existing contracts?
• merges with project contracts
• responsiblity for content → chief editor concept, proxy per project/institution - content standards

c) usage of components

b) software as a service - SLA

a) software development

→ RK: ask Antonia for MOSAiC

Content

O2A components have been designed to provide solutions for managing the following types of content:

• Metadata on platforms, devices and sensors are described in sensor.awi.de (see further information).  There is a chief editor concept, where experts for thematic topics or projects should care about metadata structure, quality and harmonization. Have a closer look to the description of the chief editor concept and / or write o2a-support@awi.de for help and feedback.
• Raw data  can be automatically collected from different sources using ingest.awi.de and stored in AWI's storage solution in the form of flat files or, if wished, in databases (see further information).  To allow automatic data processing, archiving, publication and provision in web services (e.g., dashboard, data web service, spatial data infrastructure), O2A uses adopts a pre-defined directory structures, standard data formats (simple data formats, spatial data formats) and basic quality flagging. Three types of data ingestion are supported:
  • automatic data ingestion in near-real time mode
  • automatic data ingestion in delayed-mode 
  • manual data ingestion
• Primary data and data products are derived from raw data. Scientific work can be self-managed in projects using cloud.awi.de (will be open end of 2020). Our cloud supports provides access to user-tailored virtual machines and containers as well as a pre-configured Jupyter Notebook environment at jupyterhub.awi.de. For long-term archiving and data publication PANGAEA is used.

Would you like to manage your data flows with O2A? We are happy if you contact us by o2a-support@awi.de.

Software as a service

SaaS

SLA

Betreiben:

• Software: AWI, kein Support für extern laufende Systeme, kein Community-SW-Entwicklungs-Support
• Inhalt: verteilt, Chief Editor Konzept.
• Is our chief editor concept really working????