<Insert here a brief introduction to this topic, e.g. as illustrated for General requirements below>

<Introduction to the questions asked pertaining to general / pervasive requirements and setting the context of topic-­specific requirements. Collation and integration of any pertinent properties and requirements that are consistent across all of the research infrastructures addressed by ENVRIplus requirements gathering.>

<insert here who is responsible for steering and editing this page. But they need to get their go-betweens to agree they have covered the points, e.g. for General requirements>

알 수 없는 사용자 (cristinaalexandru) and 알 수 없는 사용자 (rosafilgueira): draft and incrementally refine.

Overview and summary of <Topic> requirements

...

Introduction

Within their first discussion with the RI REPs or their delegates, the Go Betweens usually asked them a series of general questions, to set the scene for subsequent discussions. These general questions covered the following areas of interest:

• The basic purpose of their RI, here including some representative use cases, data typology and the data lifecycle, user/stakeholder responsibilities;
• High level questions spanning the ENVRIplus main topics:
  • Standards and software that they use
  • Optimization plans
  • Topics within their data management plan
  • Non-functional constraints
  • Data security and access
• What their RI can bring to ENVRIplus (in terms of data, software, computational resources, access to equipment, literature, etc.);
• What objectives and services their RI is expecting from ENVRIplus.

The full list of questions is available on ActiveCollab: https://envriplus.manageprojects.com/projects/requirements/notebooks/431/pages/82/attachments/529/download?force=1&disposition=attachment

At the end of their first discussion, the Go Betweens encouraged the RI REPs to decide on one or more particular topics that they would like to contribute to during subsequent discussions. They were also open to their suggestions about the right person from the RI (i.e. RI REP delegate) to contact in case more specialised information was needed. 

Authors: Image Added and Image Added.

Overview and summary of general requirements

<The overview and summary should be written (integrated and distilled) by the topic leader(s), highlighting commonalities and reporting significant variations. It should be refined and agreed by the go-betweens who contributed to this topic. In particular, they should check that critical points have not been missed and that a balance has been attained.>

Research Infrastructures

The following RIs contributed to developing <Topic> Requirements<Delete the general requirements:

<Delete from the following list any that were not able to contribute on this topic>topic>

<Add <Add an interest inducing sentence or two, to persuade readers to look at the contribution by a particular RI. Ee.Gg., What aspect of the summary forrequirementsof requirements, or the specil special cases, came from this RI. Check with RIs that they feel they are correctly presented.>

ACTRIS: <This <e.g., This RI ... and therefore has XYZ <Topic> general requirements, with a particular empahsis on ...>

AnaEE:

EISCAT-3D:

ELIXIR:

EMBRC:

EMSO:

EPOS:

Euro-ARGO:

EUROFLEETS2:

ESONET:

EUROGOOS:

FIXO3:

IAGOS:

ICOS:

INTERACT:

IS-ENES2:

JERICO:

LTER:

SEADATNETSEADATANET:

SIOS: