Date: Thu, 28 Mar 2024 17:41:30 +0100 (CET)
Message-ID: <1252053806.3079.1711644090671@confluencesrv1.awi.de>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_3078_593350714.1711644090671"
------=_Part_3078_593350714.1711644090671
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
We provide the O2A framework for AWI=
's research but also to the earth and environment community as long-term "s=
oftware 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 differen=
t integrated components and tools aligned with AWI's technical infrastructu=
re. Of course, technical implementation is based on this infrastructure.
This section describes aspects of collaborat=
ion in terms of metadata and data content, offered services as well as deta=
iled software development of O2A components.
O2A components have been designed to provide solutions for managing the =
following types of content:
- Metadata on platforms, devices and sensors are de=
scribed in sensor.awi.de (see further information). There is a =
chief editor concept, where experts for thematic topics or project=
s should care about metadata structure, quality and harmonization. Have a c=
loser 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 dif=
ferent sources using ingest.awi.de and stored in AWI's storage solution in the form of flat files or, i=
f 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<=
/a>. Three types of data ingestion a=
re supported:
- automatic data ingestion in near=
-real time mode
- automatic data ingestion&n=
bsp;in delayed-mode
- manual data ingestion
- Primary data and data pr=
oducts are derived from raw data. Scientific work can be self=
-managed in projects using cloud.awi.de (will be o=
pen end of 2020). Our cloud supports provides access to user-tailored virtu=
al machines and containers as well as a pre-configured Jupyter Notebook env=
ironment at jupyterhub.awi.de. For long-term archiving and data pub=
lication PANGAEA is used.
Responsibility
As the software development process is aligned to SCRUM, each O2A compon=
ent or product has it's own product owner. The product owner is responsible=
for vision, wishes and requirements and maximizing the value of the softwa=
re product for the community. This targeted view is merged and harmonized i=
n the O2A strategic leader group. The members of the leader group have deca=
des of experiences in natural science, research data management, informatio=
n technology and software development.
Contributing
Contributions to O2A are very welcome. We ma=
inly 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 imp=
rove 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 featur=
e in mind. On the other hand we are willing to integrate a developer for ef=
forts about at least 3 person months (including training period, developmen=
t, unit tests, review and integration tests).
- join the team - The preferred way is to join the devel=
opment team permanently! This option makes sense if you are willing to cont=
ribute at least 10-20% working time for at least one year. Focus is on cont=
ributions 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:
- Provide a draft for extensions or changes (max. 2 pages). The draft sho=
uld cover the contribution type, strategic impact, the value for the commun=
ity (also who is the community) and a rough effort estimate. It should be a=
s concrete as possible.
- Get in contact with us o2a-support@awi.de.
- We will decide if and how we can integrate your contribution. This cove=
rs also an estimation for the technical impact and effort for core function=
ality or extensions.
- We get in touch with you and discuss the approach.
------=_Part_3078_593350714.1711644090671--