Page History

...

• Metadata about platforms, devices and sensors is 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 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 in web services (e.g., dashboard, data web service, spatial data infrastructure), O2A uses standardized defined directory structures, stanardized data formats (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.

...

In general our O2A software is open source, free of charge and may be re-used in other contexts. Our software lives is administrated in the gitlab.awi.de repository and you can find examples on github.com also. 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.

...