We provde O2A 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 service services as the they are, especially in project-contexts where AWI is alignedinvolved. 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 section describes aspects of collaboration in terms of metadata and data content, offered services as well as detailed software development of O2A components.

Index

• Content

...

The content in O2A can be distinct in a) metadata and b) data.

• in O2A
• Responsibility
• Contributing
• Software development

Anchor
content content

Content

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

• Metadata on Metadata about platforms, devices and sensors is mainly 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 qualityharmonization. Have a closer look to the description of the chief editor concept and / or write o2a-support@awi.de for help and feedback.
• Data Raw data  can be automatically collected from different sources with using ingest.awi.de and is  and stored in AWI's technical infrastructure as storage solution in the form of flat files or optional , if wished, in databases (see further information).  To allow automatic data processing, archiving, publication and provision of in web services O2A uses standardized (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.

Software development

In general our O2A software is open source and can be re-used in other contexts.

Code-Lizenzen:

•  Roland Koppe prüft Modelle für Frontend, voraussichtlich BSD-3 oder MIT
•  Roland Koppe Middleware / Backend Lizenzen müssen intensiver geprüft werden

Verantwortung:

• Ausrichtung: AWI, Product Owner
• Inhalt: AWI, Chief Editor Konzept
• Code: AWI

Betreiben:

• Software: AWI, kein Support für extern laufende Systeme, kein Community-SW-Entwicklungs-Support
• Inhalt: verteilt, Chief Editor Konzept

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:

...

• 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.

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

Anchor
responsibility responsibility

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.

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

Anchor
contributing contributing

Contributing

Contributions to O2A are very 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.

The contribution process should look like this:

1. Provide a draft for extensions or changes (max. 2 pages). The draft should cover the contribution type, strategic impact, the value for the community (also who is the community) and a rough effort estimate. It should be as concrete as possible.
2. Get in contact with us o2a-support@awi.de.
3. We will decide if and how we can integrate your contribution. This covers also an estimation for the technical impact and effort for core functionality or extensions.
4. We get in touch with you and discuss the approach.

Info
icon false
Do you like to contribute? Send us a mail o2a-support@awi.de and describe how you like to contribute.

Info
icon false
You don't like to contribute but use O2A? Have a look to our public available application programming interfaces (API) here https://spaces.awi.de/x/_F2VEg

...