We provide O2A for our own 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 software development of O2A components.

Content

The content in O2A can be distinct in metadata and data.

• Metadata about platforms, devices and sensors is 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 with ingest.awi.de and is stored in AWI's technical infrastructure as flat files or optional in databases (see further information). To allow automatic data processing, archiving, publication and provision of web services (e.g., dashboard, data web service, spatial data infrastructure), O2A uses standardized directory structures, simple data formats, spatial data formats and basic quality flagging. Three types of data ingestion are distinguished:
  • automatic near real-time data ingestion
  • automatic and central delayed-mode data ingestion
  • manual data ingestion
• Primary data is derived from raw data. Scientific work can be self-managed in projects with cloud.awi.de (will be open end of 2020). Our cloud supports custom virtual machines and containers as well as a prepared Jupyter Notebook environment at jupyterhub.awi.de. For long-term archiving and data publication of primary data go directly to PANGAEA.

Do 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

Software development

In general our O2A software is open source, free of charge and may be re-used in other contexts. Our software lives in gitlab.awi.de and you can find examples on github.com. To foster and streamline software development we want to have one central managed code basis. All splitted branches for new features and bug fixes shall be finally merged into the central master branch aligned with Gitflow. The agile software development process for each O2A component is managed in 2-weekly sprints with jira-software.awi.de following SCRUM-based principles.

Licenses

Our O2A software is licensed under BSD-3-Clause, if no other definition is given. To foster community value, we encourage you to use also BSD-2-Clause, BSD-3-Clause or MIT licences for your derived works. We will only integrate your work into our managed code basis, if it is licensed the way described before. 3rd-party libraries keep their licences and must be compatible with named licenses.

Copyright 2010-2020- Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this 
   list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.

3. Neither the name of the copyright holder nor the names of its
   contributors may be used to endorse or promote products derived from 
   this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Responsibility

As the software development process is aligned to SCRUM, each O2A component or product has it's own product owner. The product owner is responsible for vision, wishes and requirements and maximizing the value of the software product for the community. This targeted view is merged and harmonized in the O2A strategic leader group. The members of the leader group have decades of experiences in natural science, research data management, information technology and software development.

Do you have ideas improving an O2A component? We are happy if you contact us by o2a-support@awi.de.

Contributing

Contributions to are welcome. We mainly distinguish three types of contributions:

• feedback - We heartily invite you to give us feedback and describe what you like to have and makes your life easier. Our product owner will check your feedback, map and prioritize it into our goals to improve the software continuously.
• significant contributions - You are missing some major part in O2A and want to contribute within a project-context? One way is to negotiate a project-membership with financed effort for the desired feature in mind. On the other hand we are willing to integrate a developer for efforts about at least 3 person months (including training period, development, unit tests, review and integration tests).
• join the team - The preferred way is to join the development team permanently! This option makes sense if you are willing to contribute at least 10-20% working time for at least one year. Focus is on contributions for the community as defined by the product owner. The developer gets a thematic training period, attends and contributes to SCRUM meetings and feels responsible for the product.

Beitragen:

• Offene APIs stehen dokumentiert zur Verfügung und können von Externen Systemen verwendet werden → O2A Space, z.B. https://spaces.awi.de/x/DxEUEg
• Code liegt im aus dem Internet erreichbarem gitlab.awi.de (Account nötig, DFN AAI)
• signifikante Beiträge können integriert werden
  
  • Entwicklungskompetenz besteht
  • Einarbeitungszeit < 2 W 
  • Entwicklungsaufwand > 3 PM
  • Code Reviews durch AWI < 1 W
  • Testaufwand 20%
  • sonst ggf. Aufnahme ins Backlog
• dauerhafte Mitarbeit eines Entwicklers
  • Entwicklungskompetenz besteht
  • Einarbeitungszeit < 2 W 
  • Entwicklungsaufwand > 10% - 20% (> 4h / Woche)
  • Code Reviews durch AWI < 1 W
  • Testaufwand 20%
  • Themenspezifisch

1. Vorschlag für Erweiterung bzw. Änderungen skizzieren, Strategie und Aufwand darstellen (Extern, Anforderungsdefinition)
2. Kontakt zu AWI Product Owner + Entwicklung
3. Technische Abschätzung zu Kernfunktionen bzw. Erweiterungen (AWI)
4. Entscheidung zur Integration und Mitarbeit in O2A-Komponenten (Kosten/Nutzen) (AWI)
5. Lizenzen sind kompatibel mit O2A Lizenzmodell TBD (AWI)

• Roland Koppe: Doku "how to get involved"

-------------------------------------------------------------------

→ im DataHUB brauchen wir Aufstellung, welche Systeme (zu Sensor/Obsdaten) gibt es wo, mit Links zum Reinschauen und zusammenarbeiten

• Peter Gerchowkontaktiert Jan Bumberger für deren Link zu deren Sensor Registry

neues MOSES-DM-Portal (GFZ) holt keine AWI-MOSES-Daten vom AWI-Sensor ab https://moses-data.gfz-potsdam.de/onestop/#/

• Peter Gerchow delegiert an Norbert einen Termin für O2A und MOSES für einen Mini-2h-WS mit GFZ (Doris u Hannes Fuchs GFZ) (Pilipp Fischer, Peter, Roland, Norbert, Ana, Angela: Hannes Fuchs, Doris +)

• Permafrost https://moses-data.gfz-potsdam.de/onestop/#/collections/details/AXHul1vN7ADFoZuVvEZF?m=eventChain:Permafrost%20Thaw;metadataType:Campaign

-------------------------------------------------------------------

Gilt auch für Ingest von Delayed Mode und NRT Data:

• Als Dienstleistung/Service? → siehe DAM Underway Daten
  Frank Oliver Glöckner Ist Speicher für DAM durch Systems beschafft worden. Kostenstelle für eCloud?
• In der Software Entwicklung
• In der Speicherung (isilon oder hssrv1) → Kostenstelle, Speicher-beschaffung durch Systems.