Contacts: Marina Adomeit (NORDUnet/Sunet) and Janos Mohacsi (GÉANT/KIIFU)

Start: M1 - End M12

The objective of this work package is to collect the Research Infrastructure’s requirements and use cases and to produce a landscape analysis of AAI services (and gaps) to provide input for the technical (WP1) and policy (WP2) work in Y2, as well as for WP5. The main objectives of this WP are as follows:

  • Work with the ESFRI cluster representatives and the RIs in AARC TREE to gather their requirements and use-cases;

  • Engage with existing relevant RI forums to further expand and validate the initial list of requirements;

  • Collect information for a landscape analysis about the adoption of AARC guidelines;

  • Produce a draft report containing requirements and use cases description;

  • Develop and execute a plan for consultation with the research infrastructures at large;

  • Conduct the consultation process and finalise the report.

Tasks

Task 1 Landscape analysis of AARC BPA adoption (M1-M12)

This task will leverage the information maintained by AEGIS to analyse and describe the current landscape with regards to the deployment of AARC BPA compliant AAIs as well as the adoption of AARC guidelines within. The resulting work, in the form of a description of this landscape at the start of the AARC TREE project (available at M10), will be further elaborated by WP5 and will be part of the compendium.

Task 2 Use-cases requirements and consultation (M1-M12)

This work will use as the starting point the FIM4Rv2 paper together with requirements that AARC TREE partners may have collected via other activities. In addition, it will engage with relevant forums and stakeholders (such as FIM4R, AEGIS, EOSC AAI Task Force, National RIs and European initiatives such as the EU dataspaces) to gather the initial set of requirements and use cases. Based on this, an initial set of the requirements and use cases will be captured, to drive further work. In parallel, collaboration with ESFRI representatives will be established in order to set the expectations and establish a shared understanding of the requirements and use case gathering that is to follow.

  • No labels