# Definition of requirements for the proposed design for the IRISCC Catalogue of Services

Klaus Steenberg Larsen, Alex Vermeulen, Markus Fiebig, Rosa Maria

Petracca Altieri, Sabine Philippin, Davide Di Cioccio, Stephan Kindermann, Damien Boulanger

► To cite this version:

Klaus Steenberg Larsen, Alex Vermeulen, Markus Fiebig, Rosa Maria Petracca Altieri, Sabine Philippin, et al.. Definition of requirements for the proposed design for the IRISCC Catalogue of Services. University of Copenhagen. 2024. hal-04713676

HAL Id: hal-04713676

https://uca.hal.science/hal-04713676v1

Submitted on 29 Sep 2024

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
<figure><img src="image_2.png" /></figure>

IRISCC

D7.1

**Definition of
requirements for the
proposed design for the
IRISCC Catalogue of
Services**

<figure><img src="image_3.png" /></figure>

Funded by
the European Union

Disclaimer: Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union. Neither the European Union nor the granting authority can be held responsible for them.
**Abstract**

Key words

Metadata schema, vocabulary, search filters, service description

This report provides an overview of the primary, technical requirements for the design of the first release of the IRISCC Catalogue of Services. The catalogue will be built on the existing ISIA platform that also hosts service catalogues of other projects including the AgroServ EU-INFRASERV project. As AgroServ is also a project giving access to services across multiple RIs, the requirements for the IRISCC Catalogue of Services are defined with the AgroServ Catalogue of Services as the reference model. The report I) gives an overview of existing vocabularies used across the different RIs in IRISCC that should be used as much as possible in building the specific IRISCC metadata schema, II) it highlights the changes needed for the IRISCC Catalogue of Services in comparison to the AgroServ Catalogue of Services, and finally III) it summarises the steps forward from this early stage of the IRISCC project.

**Revision History**

<table><thead><tr><td>Version</td><td>Date</td><td>Description</td><td>Author/Reviewer</td></tr></thead><tbody><tr><td>V 0.1</td><td>25/06/2024</td><td>First Draft</td><td>Klaus Steenberg Larsen, University of Copenhagen (UCPH)</td></tr><tr><td>V 0.2</td><td>01/07/2024</td><td>First Draft Revision</td><td>Klaus Steenberg Larsen, University of Copenhagen (UCPH)</td></tr><tr><td>V 0.3a</td><td>09/07/2024</td><td>Review</td><td>Magdalena Brus, EGI Foundation (EGI.eu)</td></tr><tr><td>V 0.3b</td><td>16/07/2024</td><td>Review</td><td>Dick Schaap, Mariene Informatie Service (MARIS)</td></tr><tr><td>V 1.0</td><td>19/08/2024</td><td>Submitted version</td><td>Klaus Steenberg Larsen, University of Copenhagen (UCPH)</td></tr></tbody></table>
<table><thead><tr><th colspan="4">Document Description</th></tr></thead><tbody><tr><td colspan="4">D7.1 Definition of requirements for proposed design for IRISCC Catalogue of services</td></tr><tr><td colspan="4">Work Package Number 7</td></tr><tr><td>Document Type</td><td colspan="3">Report</td></tr><tr><td>Document Status</td><td>Under EC Review</td><td>Version 1.0</td><td></td></tr><tr><td>Dissemination Level</td><td colspan="3">Public</td></tr><tr><td>Copyright Status</td><td colspan="3">This material by Parties of the IRISCC Consortium is licensed under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License.</a></td></tr><tr><td>Lead partner</td><td colspan="3">UCPH</td></tr><tr><td>Document Link</td><td colspan="3"></td></tr><tr><td>DOI</td><td colspan="3">https://doi.org/10.5281/zenodo.13354103</td></tr><tr><td>Main Author(s)</td><td colspan="3"><ul><li>Klaus Steenberg Larsen (University of Copenhagen, UCPH)</li></ul></td></tr><tr><td>Contributing Authors</td><td colspan="3"><ul><li>Alex Vermeulen, Lund University (ULUND)</li><li>Markus Fiebig, Norwegian Institute for Air Research (NILU)</li><li>Rosa Maria Petracca Altieri, National Research Council of Italy, Institute of Methodologies for Environmental Analysis (CNR)</li><li>Sabine Philippin, French National Centre for Scientific Research (CNRS)</li><li>Davide Di Cioccio, European Marine Biological Resource Centre (EMBRC)</li><li>Stephan Kindermann, Deutsches Klimarechenzentrum (DKRZ)</li><li>Damien Boulanger, French National Centre for Scientific Research (CNRS)</li></ul></td></tr><tr><td>Reviewers</td><td colspan="3"><ul><li>Magdalena Brus, EGI Foundation (EGI.eu)</li></ul></td></tr></tbody></table>
<table><tr><td></td><td><ul><li>Dick Schaap, Mariene Informatie Service (MARIS)</li></ul></td></tr><tr><td>Approved by:</td><td><ul><li>Päivi Haapanala, Natural Resources Institute Finland (Luke)</li></ul></td></tr><tr><td>Estimated Delivery date</td><td>June 2024 (M3)</td></tr><tr><td>Actual Delivery date</td><td>21/08/2024</td></tr></table>

## Terminology / Acronyms

<table><thead><tr><td>Term/Acronym</td><td>Definition</td></tr></thead><tbody><tr><td>AAT</td><td>Art & Architecture Thesaurus.</td></tr><tr><td>AgroServ</td><td>Integrated services supporting a sustainable Agroecological transition (AgroServ). EU-INFRASERV project (2022-2026).</td></tr><tr><td>Analytical facility</td><td>Facility that offers advanced biological, physical and chemical analyses for a deeper insight into processes.</td></tr><tr><td>API</td><td>Application Programming Interface. API is a way for two or more computer programs or components to communicate with each other.</td></tr><tr><td>ISIA</td><td>Platform hosted at CNRS to share data, information and resources such as service catalogues of various research infrastructures.</td></tr><tr><td>Metadata schema</td><td>The metadata schema lists the data elements with their definitions. In addition, it states the rules that govern the use of each specific data elements to describe a resource.</td></tr><tr><td>PASS</td><td>Platform for managing user Access to ACTRIS Services (PASS), an online, centralized access management platform operated by the ACTRIS Service and Access Management Unit and made available to IRISCC to manage physical, remote and hybrid access to the research facilities.</td></tr><tr><td>RI</td><td>Research Infrastructure.</td></tr></tbody></table>
<table><tr><td>4.2.3 Location and country</td><td>28</td></tr><tr><td>4.2.4 Experimental Installation</td><td>28</td></tr><tr><td>4.2.5 Analytical Installation</td><td>29</td></tr><tr><td>4.3 EOSC model - services</td><td>31</td></tr><tr><td>4.3.1 Basic Information</td><td>32</td></tr><tr><td>4.3.2 Marketing Information</td><td>34</td></tr><tr><td>4.3.3 Classification information</td><td>38</td></tr><tr><td>4.3.4 Geographical and language availability information</td><td>40</td></tr><tr><td>4.3.5 Resource location information</td><td>40</td></tr><tr><td>4.3.6 Contact information</td><td>41</td></tr><tr><td>4.3.7 Maturity information</td><td>43</td></tr><tr><td>4.3.8 Dependencies information</td><td>44</td></tr><tr><td>4.3.9 Attribution information</td><td>45</td></tr><tr><td>4.3.10 Management Information</td><td>46</td></tr><tr><td>4.3.11 Access and order information</td><td>49</td></tr><tr><td>4.3.12 Financial information</td><td>49</td></tr><tr><td>4.4 Metadata fields for additional Information - services</td><td>50</td></tr><tr><td>4.4.1 Marketing information</td><td>51</td></tr><tr><td>4.4.2 Location and country</td><td>55</td></tr><tr><td>4.4.3 Dependencies information</td><td>56</td></tr><tr><td>5. Adaptations and changes compared to the AgroServ service catalogue (AgroServ test version, June 2024)</td><td>57</td></tr><tr><td>6. Adapting the PASS access management tool and integration with ISIA</td><td>67</td></tr><tr><td>7. Metadata collection</td><td>69</td></tr><tr><td>8. Conclusions and next steps</td><td>71</td></tr></table>
# Executive summary

The overall objective of IRISCC WP7 is to design, establish and maintain the IRISCC Catalogue of Services. The IRISCC Catalogue of Services is the main reference for the users and the single source of consistent information on all operational services on climate change-related risks and vulnerabilities made available to users in the IRISCC project via transnational and virtual access. The early deliverable D7.1 aims to define the technical requirements for the proposed design of the IRISCC Catalogue of Services. As such, this report forms the starting point for the technical development done by the developers of the IRISCC Services catalogue and the IRISCC homepage.

The development of the IRISCC Catalogue of Services will build on the already existing service catalogues established by the IRISCC consortium members. Specifically, the IRISCC Catalogue of Services will be hosted on the ISIA platform, developed and maintained at CNRS, France (https://test.isia.cnrs.fr/). The ISIA platform currently also hosts service catalogues of AnaEE France, AnaEE ERIC and the EU INFRASERV project AgroServ. As the AgroServ project already is a service catalogue giving access to services across multiple RIs, the newest test version of this catalogue (https://test.isia.cnrs.fr/catalog/2/services) will serve as the reference model for the IRISCC Catalogue of Services. A new development for IRISCC is the Integration of the IRISCC Service Catalogue hosted on ISIA with the PASS platform for managing user access to services. PASS is an online, centralized access management platform operated by the ACTRIS Service and Access Management Unit and made available to IRISCC to manage physical, remote and hybrid access to the research facilities. This report identifies changes needed for the upcoming IRISCC Catalogue of Services to optimise user access and discovery of the IRISCC services.

During the project, the development of the IRISCC Catalogue of Services will be an iterative process between IRISCC work package activities and service developments and the web interface developers. This report is therefore not exhaustive, but does state the primary, technical requirements for the design of the first release version of the IRISCC Catalogue of Services.

Summary of technical requirements:

* In building the metadata schema for the additional information needed in IRISCC, the existing vocabularies within the IRISCC consortium should always be used if possible (section 2).

* The IRISCC Catalogue of Services must be able to handle all the different types of access identified for IRISCC (section 3).

* The existing metadata schemas from AgroServ to describe additional information on facilities and services need to be adapted to the needed description of facilities and individual services in IRISCC (section 4).
* Search filters need to be adapted for IRISCC. In particular, for the first release of the Catalogue of Services, the two core search filters should be "System" and "Risk". Other improvements of the current handling of search filters for AgroServ are also requested for IRISCC (section 5).

* A technical solution allowing integration of the PASS access management tool and ISIA is needed (section 6).

* An online web interface for service providers to allow updating required information is requested. In addition, preferably the web interface should provide the opportunity to fill out and upload a .csv template or similar with all mandatory data fields from the service providers (section 7).

Based on these technical requirements, the next steps are to first define the mandatory metadata fields for IRISCC service providers from the EOSC-based model and then to define the additional information required for the descriptions of facilities and individual services in IRISCC. Then developers can make the necessary adaptations of ISIA and service providers can start filling out either the online form or a simple .csv template (if possible) to populate the online web Catalogue of Services. Concurrent with this development, the development of a technical solution for the integration of the PASS access management tool and ISIA should be initiated.
# 1. Objective of this report

The overall objective of IRISCC WP7 is to design, establish and maintain the IRISCC Catalogue of Services, as the IRISCC Catalogue of Services is the main entry-point for the users to find and explore integrated information, digital services and transnational access services on climate change related risks and vulnerabilities.

In meeting this overall objective, the first deliverable D7.1 set already for month 3 of the IRISCC project aims to define the requirements for the proposed design of the IRISCC Catalogue of Services. As such, this report will form the starting point for the technical development done by the developers of the IRISCC Services catalogue and the IRISCC website.

The development of the IRISCC Catalogue of Services will build on already existing service catalogues established among the IRISCC beneficiaries, which will form the basis for further development within the context of IRISCC. The IRISCC Catalogue of Services will be hosted on the ISIA platform, developed and maintained at CNRS, France (https://test.isia.cnrs.fr/). The ISIA platform currently also hosts service catalogues of AnaEE France (https://test.isia.cnrs.fr/catalog/3/services), AnaEE ERIC (https://test.isia.cnrs.fr/catalog/1/services) and the EU INFRA-SERV project AgroServ (https://test.isia.cnrs.fr/catalog/2/services). As the AgroServ project already is a service catalogue giving access to services across multiple Research Infrastructures (RIs), the newest test version of this catalogue will serve as the reference model for the IRISCC Catalogue of Services. This report therefore aims to identify which specific improvements are needed for the upcoming IRISCC Catalogue of Services to provide users an easy overview of and access to the IRISCC services.

# 2. Using existing vocabularies across IRISCC

A controlled vocabulary derived from thesauri is essential to ensure interoperability between tools, disciplines and users. It guarantees an unambiguous understanding of the content expressed and allows a unique identifier (URI) to be associated with it, enabling machines to read it. Table 2.1 lists the current vocabularies used across IRISCC RIs.
It is a technical requirement of the IRISCC Catalogue of Services to use existing vocabularies whenever possible and only create new data fields – and associated vocabularies – when required. Priority should be given to vocabularies already used across multiple RIs in IRISCC.

Among the IRISCC partners, D4Science provides a vocabulary matching tool. This tool, developed as part of the ARIADNE H2020 project, assists in mapping locally used terms and concepts to the Getty Art & Architecture Thesaurus (AAT). The goal of this mapping process is to identify subject mappings from source terms and concepts to AAT concepts, facilitating improved browsing and searching of the data. (Link to vocabulary matching tool: https://vmt.ariadne.d4science.org/vmt/vmt-app.html). As IRISCC has a stronger focus on environmental data, data products, models, and socio-economic impacts, an even more relevant adaptation for IRISCC vocabularies is that a Semantic Analyser for wider environmental terms is currently being developed as part of the HE FAIR-EASE project (https://zenodo.org/records/10606930), which includes SeaDataNet vocabularies, hosted by National Oceanography Centre (NOC) - British Oceanographic Data Centre (BODC).

<table><caption>Table 2.1. Overview of existing vocabularies used by IRISCC partners</caption><thead><tr><td>RI</td><td>Link</td></tr></thead><tbody><tr><td>ACTRIS</td><td>https://vocabulary.actris-nilu.no/actris_vocab/<br>https://vocabulary.actris-nilu.no/actris_controlled_lists/<br>https://www.actris.eu/sites/default/files/Documents/ACTRIS%20IMP/Deliverables/ACTRIS_D6_5_Access_Management_Plan.pdf<br>https://www.actris.eu/sites/default/files/inline-files/ACTRIS_glossary_April2022_0.pdf</td></tr><tr><td>AnaEE</td><td>https://www.anaee.eu/resources/acronyms-glossary/glossary<br>https://www.anaee.eu/resources/acronyms-glossary/acronyms<br>https://www.vocabularyserver.com/anaeethes/</td></tr><tr><td>D4SCIENCE</td><td>https://catalogue.d4science.org/dataset?systemtype=GlossaryTerm</td></tr><tr><td>ECMWF</td><td>https://vocab.nerc.ac.uk/standard_name/<br>https://www.ecmwf.int/en/forecasts/datasets/open-data</td></tr><tr><td>EGI</td><td>https://confluence.egi.eu/display/EGIG/</td></tr><tr><td>EIRENE RI</td><td>https://zenodo.org/records/11219301</td></tr><tr><td>eLTER</td><td>https://vocabs.iter-europe.net/elter_cl/en/</td></tr></tbody></table>
<table><tr><td>EMBRC</td><td>A glossary of terms and definitions is defined in the internal document "Guidelines for access to EMBRC" (ver. 2.2, pages 15-16)</td></tr><tr><td>EOSC (NOT RI but used by many RIs)</td><td>https://vocabs.sshopencloud.eu/vocabularies/eosc-resource-category/eoscResourceCategoryScheme</td></tr><tr><td>GESIS</td><td>https://lod.gesis.org/en/<br>https://lod.gesis.org/thesoz/en/page/?uri=http%3A%2F%2Flod.gesis.org%2Fthesoz%2Fconcept_10042069</td></tr><tr><td>IAGOS</td><td>Using AERIS vocabulary for variables:<br>https://skosmos.aeris-data.fr/aeris_param/en/<br>mapped with GCMD keywords for discoverability and CF Standard Names (cfconventions.org) for description in data files (in NetCDF format)</td></tr><tr><td>ICOS</td><td>https://lov.linkeddata.es/dataset/lov/vocabs/cpmeta<br>tabular datasets: https://meta.icos-cp.eu/ontologies/cpmeta/TabularDatasetSpec<br>other datasets: https://meta.icos-cp.eu/ontologies/cpmeta/DatasetSpec<br>dataset variables: https://meta.icos-cp.eu/ontologies/cpmeta/DatasetVariable</td></tr><tr><td>IS-ENES</td><td>In progress but uses:<br>CF Standard Names: https://cfconventions.org/Data/cf-standard-names/78/build/cf-standard-name-table.html<br>(cfconventions.org)<br>CMIP6 controlled vocabularies:<br>https://wcrp-cmip.github.io/CMIP6_CVs/<br>IS-ENES data service "catalog":<br>https://is.enes.org/sdm-access-use-data/</td></tr><tr><td>SeaDataNet</td><td>https://www.seadatanet.org/Standards/Common-Vocabularies<br>(links to multiple used vocabularies)<br>https://vocab.seadatanet.org/search<br>(gathers data from more than 110 data centres)</td></tr><tr><td>OPTED</td><td>In progress (part of WP8 in OPTED Horizon project No. 951832)</td></tr></table>
## 3. Access types in IRISCC

The IRISCC Catalogue of Services should be able to handle different types of access including virtual access (VA) and transnational access (TA; Physical, Remote) or Hybrid access (Table 3.1). Some harmonization work regarding the vocabulary specific for access types and modes for access will be needed and done during the IRISCC project as the meaning is differently used between RIs. For example, in AnaEE, access mode is about paid/free access, while in ACTRIS it is about the conditions and evaluation of the access. (excellence-driven, market-driven, technical need-driven, etc., in line with the European charter of access to RIs).

<table><caption>Table 3.1 Types of access in IRISCC</caption><thead><tr><td>Type of Access</td><td>Definition</td></tr></thead><tbody><tr><td>Virtual access (VA)</td><td>Virtual access (VA) is free access to users provided by a facility or infrastructure through communication networks; an unlimited number of users can simultaneously use the available services or resources and the users are not selected. Virtual access within IRISCC concerns access to scientific data, digital tools and/or integrated online services related to climate change risks.</td></tr><tr><td>Transnational access (TA)<br/>Physical access</td><td>Physical access is "hands-on" access when users physically visit an infrastructure/facility/equipment/installation. Physical access means access to services offered by IRISCC through an installation of the participating RIs. The available services or resources are not unlimited, and a competitive, peer-reviewed process is required following a defined procedure with well-defined criteria and call conditions for the selection of users.</td></tr><tr><td>Transnational access (TA)<br/>Remote access</td><td>Remote access is access to resources and services offered by IRISCC through a participating RIs without users physically visiting the infrastructure/facility/equipment/installation. Similar to physical access, the services or resources are not unlimited, and a competitive, peer-reviewed process is required following a defined procedure with well-defined criteria and call conditions for the selection of users.</td></tr><tr><td>Hybrid access (TA / VA)</td><td>Hybrid access combines multiple types of access to IRISCC resources and services, including virtual, physical and remote access. As hybrid involves resources for which the IRISCC facilities have limited capacity, a competitive selection of users similar to that described above for physical and remote access is required.</td></tr></tbody></table>
## 4. The IRISCC metadata schema

The IRISCC metadata schema will be adapted from the existing AgroServ metadata schemas (Figure 4.1, 4.2, 4.3 and 4.4). While all data fields in the EOSC model from the AgroServ project (Figure 4.1 and 4.3) can be accepted in the context of IRISCC, only a subset of these will be categorised as mandatory while others will be categorised as optional. There are two existing schemas in AgroServ, one for the facilities (Figures 4.1 and 4.2) and one for the services (Figures 4.3 and 4.4). The tables following each figure provide the description of each metadata field.

The metadata schema used for describing services in IRISCC should at least be compatible with the corresponding metadata schemas used in EOSC and related projects and activities. It is currently unclear whether the IRISCC service metadata schema is based on any such EOSC related schemas, especially since there does not seem to be consensus about an EOSC service metadata schema. As first attempt, an "EOSC resource profile" has been defined. However, the EOSC Future project deprecated this profile in favour of a service profile dedicated to digital services. It seems that some alignment is needed between **EOSC Beyond** (successor of EOSC Future), **ENVRI-Hub NEXT** (https://envri.eu/envri-hub-next/), and other projects to arrive at a conclusion, which could be in place for the 2nd or 3rd release of the IRISCC Catalogue of Services. Until such a conclusion is reached, IRISCC should work with the existing metadata schema of AgroServ.

The starting point for IRISCC is therefore to define the mandatory metadata fields in Figures 4.1 and 4.3, and to adapt the additional information needed in Figures 4.2 and 4.4 to the purpose of IRISCC. For physical or remote access this still needs to be defined, for virtual access services the following metadata is needed as a minimum:

* Service URL

* Access requirements (free text, not same as access policy)

* Helpdesk URL (not email)

* If relevant: account request URL

In the metadata fields in general, it would be good to be able to enter more than one contact person.
## 4.1 EOSC model - facilities

<figure><img src="image_4.png" /><figcaption>Figure 4.1 EOSC model used by the ISIA platform for the Groser Catalogue of Services to describe the *facilities* that provide services.</figcaption></figure>
### 4.1.1 Basic Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>ID</td><td>A persistent identifier, a unique reference to the Provider</td><td>String (max 30)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>No</td><td>Delivered by EOSC Catalogue</td></tr><tr><td>Abbreviation</td><td>An abbreviation of the Provider Name as assigned by the Provider</td><td>String (max 30)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>AnaEE - Central Hub</td></tr><tr><td>Name</td><td>Full Name of the Provider/Organisation offering the resource and acting as the main contact point.</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Analysis and Experimentations on Ecosystems</td></tr><tr><td>Website</td><td>The website with information about the Provider.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://www.anaee.eu/</td></tr><tr><td>Legal Entity</td><td>A Y/N question to define whether the Provider is a Legal Entity or not.</td><td>Boolean</td><td>One</td><td>Mandatory</td><td>Yes</td><td>No</td><td>Yes</td></tr></tbody></table>
<table><tr><td>Legal Status</td><td>The legal status of the Provider. The legal status is usually noted in the registration act/statutes. For independent legal entities (1) - legal status of the Provider. For embedded providers (2) - legal status of the hosting legal entity. It is also possible to select Not a legal entity.</td><td>List of controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>European Research Infrastructure Consortium (ERIC)</td></tr><tr><td>Hosting Legal Entity</td><td>Name of the organisation/institution legally hosting (housing) the provider/research infrastructure or its coordinating centre. A distinction is made between: (1) research infrastructures that are self-standing and have a defined and distinct legal entity, (2) research infrastructures that are embedded into another institution which is a legal entity (such as a university, a research organisation, etc.). If (1) - name of the research infrastructure, If (2) - name of the hosting organisation.</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>No</td><td>Research infrastructures that is self-standing and have a defined and distinct legal entity</td></tr></table>
## 4.1.2 Marketing Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Description</td><td>A high-level description of the Provider in fairly non-technical terms, with the vision, mission, objectives, background, experience.</td><td>String (max 1000)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>AnaEE (Analysis and Experimentation on Ecosystems) will pave the way for understanding the complex impact of today's multiple, interacting global change drivers on terrestrial and aquatic continental ecosystems across Europe. It will forge evidence-based adaptation and mitigation strategies that assure plant, soil, water, biodiversity and ecosystem health today and in the future. Characteristic of AnaEE, its versatile facilities that can simulate environmental drivers from land-use change, pollution, biological invasions, rising atmospheric greenhouse gases concentrations, and increasing extreme events such as droughts and heatwaves. AnaEE will link its facilities with an array of user communities, including scientists, land managers, the bio-economy industry and policy makers, to minimise human environmental impact and maximise societal benefits in a dynamic world. Specificity of AnaEE is to integrate, in a single, distributed RI, experimental methods, modelling and experimentation.</td></tr></tbody></table>
<table><tr><td>Logo</td><td>Link to the logo/visual identity of the Provider.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://i.postimg.cc/FHcsQ5WY/logo-anaee-web.png</td></tr><tr><td>Multimedia</td><td>Link to video, slideshow, photos, screenshots with details of the Provider.</td><td>URL</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://www.anaee.eu/</td></tr><tr><td>Multimedia Name</td><td>Short description of the Multimedia content</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>AnaEE Website</td></tr></table>

### 4.1.3 Classification Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Scientific Domain</td><td>A named group of providers that offer access to the same type of resource or capabilities.</td><td>Set of controlled values (see Table 1)</td><td>Multiple</td><td>Mandatory</td><td>Yes</td><td></td><td>Agricultural Sciences, Natural Sciences, Social Sciences</td></tr></tbody></table>
<table><tr><td>Scientific Sub-domain</td><td>A named group of providers that offer access to the same type of resource or capabilities, within the defined domain.</td><td>List of controlled values (see Table 1)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Agricultural Biotechnology, Agriculture, Forestry &amp; Fisheries, Animal &amp; Dairy Sciences, Other Agricultural Sciences, Veterinary Sciences, Earth &amp; Related Environmental Sciences, Environmental Engineering, Biological Sciences, Chemical Sciences</td></tr><tr><td>Tags</td><td>Keywords associated with the Provider to simplify search by relevant keywords.</td><td>String (max 20)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Analysis, Experimentation, Ecosystem, terrestrial, aquatic, ...</td></tr><tr><td>Structure Type</td><td>Defines the Provider structure type (single-sited, distributed, mobile, virtual, etc.)</td><td>List of controlled values (See Table 2)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Distributed, physical, virtual, mobile</td></tr></table>
### 4.1.4 Location Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Street Name and Number</td><td>Street and Number of in-corporation or Physical location of the Provider or its coordinating centre in the case of distributed, virtual, and mobile providers.</td><td>String (max 50)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Campus CNRS 1 avenue de la terrasse</td></tr><tr><td>Postal Code</td><td>Postal code of in-corporation or Physical location of the Provider or its coordinating centre in the case of distributed, virtual, and mobile providers.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>91190</td></tr><tr><td>City</td><td>City of incorporation or Physical location of the Provider or its coordinating centre in the case of distributed, virtual, and mobile providers.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Gif-sur-Yvette</td></tr><tr><td>Region</td><td>Region of in-corporation or Physical location of the Provider or its coordinating centre in the case of distributed, virtual, and mobile providers.</td><td>String (max 50)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Ile de France</td></tr><tr><td>Country</td><td>Country of in-corporation or Physical location of the Provider or its coordinating centre in the case of distributed, virtual, and mobile providers.</td><td>List of controlled values (See Table 3)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>France</td></tr></tbody></table>
### 4.1.5 Contact Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Main contact/Provider Manager -First Name</td><td>First Name of the Provider's main contact person/Provider Manager.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>Michel</td></tr><tr><td>Main contact/Provider Manager -Last Name</td><td>Last Name of the Provider's main contact person/Provider Manager.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>No</td><td>No</td><td>Boer</td></tr><tr><td>Main contact/Provider Manager -Email</td><td>Email of the Provider's main contact person/Provider Manager.</td><td>Email</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>michel.boer@anaee.eu</td></tr><tr><td>Main contact/Provider Manager -Phone</td><td>Phone of the Provider's main contact person/Provider Manager.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>No</td><td>No</td><td>+33(0)677020295</td></tr><tr><td>Main contact/Provider Manager -Position</td><td>Position of the Provider's main contact person/Provider Manager.</td><td>String (max 50)</td><td>One</td><td>Optional</td><td>No</td><td>No</td><td>Director General</td></tr><tr><td>Public contact-First Name</td><td>First Name of the Provider's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Michel</td></tr><tr><td>Public contact-Last Name</td><td>Last Name of the Provider's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Boer</td></tr></tbody></table>
<table><tr><td>Public contact-Email</td><td>Email of the Provider's contact person to be displayed at the portal or general email to contact Provider.</td><td>Email</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>michel.boer@anaee.eu</td></tr><tr><td>Public contact-Phone</td><td>Phone of the provider's contact person to be displayed at the portal or general phone to contact the Provider.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>+33(0)677020295</td></tr><tr><td>Public contact-Position</td><td>Position of the Provider's contact person to be displayed at the portal.</td><td>String (max 50)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Director General</td></tr></table>

### 4.1.6 Maturity information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Life Cycle Status</td><td>Current status of the Provider/Research infrastructure life-cycle.</td><td>List of controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>No</td><td>Operation</td></tr><tr><td>Certifications</td><td>List of certifications obtained for the Provider (including the certification body and any certificate number).</td><td>String (max 250)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>AGROSERV: HORIZON-INFRA-2021-SERV-01, ENVRI FAIR, EHRIITC</td></tr></tbody></table>
### 4.1.7 Dependencies Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Participating Countries</td><td>Providers/Research Infrastructures that are funded by several countries should list here all supporting countries (including the Coordinating country).</td><td>List of controlled values (See Table 3)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Belgium, Bulgaria, Czech Republic, Denmark, Finland, France, Italy</td></tr><tr><td>Affiliations</td><td>Providers that are members or affiliated or associated with other organisations should list those organisations here</td><td>String (max 30)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>https://www.anaee.eu/about/national-nodes</td></tr><tr><td>Networks</td><td>Providers that are members of networks should list those networks here.</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>AgroServ, ENVRI</td></tr><tr><td>Catalogue</td><td>The Catalogue this Provider is originally registered at.</td><td>Catalogue ID</td><td>1</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://isia.cnrs.fr/catalog/platform/list/agroserv</td></tr></tbody></table>
4.1.8 Other information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>ESFRI Domain</td><td>ESFRI domain classification.</td><td>List of controlled values (See Table 4)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Environment</td></tr><tr><td>ESFRI Type</td><td>If the research infrastructure is (part of) an ESFRI project indicate how the RI participates: a) is a node of an ESFRI project, b) is an ESFRI project, c) is an ESFRI landmark, d) is not an ESFRI project or landmark.</td><td>List of controlled values (See Table 5)</td><td>One</td><td>Optional</td><td>Yes</td><td>No</td><td>Landmark</td></tr><tr><td>MERIL Scientific Domain</td><td>MERIL scientific domain classification</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Earth &amp; Environmental Sciences</td></tr><tr><td>MERIL Scientific Subdomain</td><td>MERIL scientific subdomain classification</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Agronomy, Forestry, Plant Breeding Centres, Analytical Facilities, In Situ Earth Observatories, Conceptual Models</td></tr><tr><td>Areas of Activity</td><td>Basic research, Applied research or Technological development</td><td>List of controlled values (See Table 6)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Applied Research, Basic Research, Technological Development, Other</td></tr></tbody></table>
<table><tr><td>Societal Grand Challenges</td><td>Provider's participation in the grand societal challenges as defined by the European Commission</td><td>List of controlled values (See Table 7)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Environment, Europe in a changing world, Natural Resources</td></tr><tr><td>Sustainable Development Goals</td><td>Provider's contribute to the sustainable development goals as defined by European Commission</td><td>List of controlled values (See Table 9)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Zero hunger, Clean water and sanitation, Sustainable cities and communities, Responsible consumption and production, Climate action, Life below water, Life on land</td></tr><tr><td>National Roadmaps</td><td>Provider's participation in a national roadmap.</td><td>String (max 80)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>https://op.europa.eu/en/publication-detail/-/publication/c6647f05-874e-4cdd-af70-22ade4759930/language-en</td></tr></table>
## 4.2 Metadata fields for additional Information – facilities

<table><thead><tr><th colspan="5">Additional Information</th></tr><tr><th>Basic & Marketing Information</th><th>Keywords</th><th>Experimental platform Information</th><th>Analytical platform Information</th><th>Modelling platform Information</th></tr></thead><tbody><tr><td>Main Image<br>Submission project link<br>Affiliation laboratory<br>Research Institution<br>Platform capacity<br>Accommodation capacity<br>Electricity<br>Wifi<br>HighSpeed Wifi<br>Shower</td><td>List of keywords</td><td>Experimental platform type<br>Climate Zones<br>Ecosystems<br>Environmental Controlled Factors<br>Environmental Manipulated Factors<br>Replication capacity<br>HighSpeed Wifi<br>Shower</td><td>Analytical platform type<br>Analysis categories<br>Analysed parameters<br>Instruments used<br>Precision and sensitivity<br>Analytical capacity</td><td></td></tr><tr><td></td><td>Location Information</td><td></td><td></td><td></td></tr><tr><td></td><td>Latitude<br>Longitude<br>Country<br>abbreviation</td><td></td><td></td><td></td></tr></tbody></table>

Figure 4.2 The AgroServ metadata fields for additional information on *facilities* that provide services. This table, in particular, needs to be adapted to the needs of IRISCC.
## 4.2.1 Basic and marketing Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Main image for the descriptive sheet</td><td>This image will appear at the top of the description sheet and will be representative of the installation.</td><td>String (max 30)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://i.postimg.cc/BbT9V4Q3/le-chateau-de-button-a-gif-sur-yvette-le-31-juillet-2015-1.jpg</td></tr><tr><td>Submission project link</td><td>Link to your network's project submission form with the selected installation.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://isia.cnrs.fr/ppa/agroserv/agroservpreproposal</td></tr><tr><td>Affiliation laboratory</td><td>Name of your affiliate laboratory</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://www.anaee.eu/abou/national-nodes</td></tr><tr><td>Research institution</td><td>Name of your Research institution</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://www.anaee.eu/abou/national-nodes</td></tr><tr><td>Installation capacity</td><td>Number and designation of available experimental units</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>0</td></tr></tbody></table>
<table><tr><td>Accommodation capacity</td><td>Number of accommodations available</td><td>String (max 100)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>0</td></tr><tr><td>Electricity</td><td>Power supply available on the installation</td><td>Boolean</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Wifi</td><td>Wifi available on the installation</td><td>Boolean</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Highspeed Wifi</td><td>High-speed Wi-Fi available on the installation</td><td>Boolean</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Shower</td><td>Shower available on the installation</td><td>Boolean</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>No</td></tr></table>

### 4.2.2 Keywords

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Keywords</td><td>Keywords about your installation</td><td>String (max 1000)</td><td>Multiple</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Analysis, Experimentation, Ecosystems, terrestrial, aquatic, ...</td></tr></tbody></table>
### 4.2.3 Location and country

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Latitude</td><td>Latitude coordinate of the installation (in decimals: 60.924530 for 6055'8.3"N)</td><td>String (7)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>48.704754</td></tr><tr><td>Longitude</td><td>Longitude coordinate of the installation (in decimals: 11.451259 for 1127'04.5"E)</td><td>String (7)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>2.135254</td></tr><tr><td>Country Code</td><td>Country name abbreviation (France: FR)</td><td>Controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>FR</td></tr></tbody></table>

### 4.2.4 Experimental Installation

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Experimental Installation Type</td><td>Enclosed, Open air or Observation</td><td>Controlled values</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Open air</td></tr><tr><td>Climate Zones</td><td>Climates that can be found on the installation</td><td>Controlled values</td><td>Multiple</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Mediterranean</td></tr><tr><td>Ecosystems</td><td>Ecosystems that can be found on the installation</td><td></td><td>Multiple</td><td></td><td></td><td>Yes</td><td>Grassland</td></tr></tbody></table>
<table><tr><td></td><td></td><td>Controlled values</td><td></td><td>Mandator y</td><td>Yes</td><td></td><td></td></tr><tr><td>Environmental Controlled Factors</td><td>Environmental parameters measured on the installation</td><td>Controlled values</td><td>Multiple</td><td>Mandator y</td><td>Yes</td><td>Yes</td><td>atmospheric temperature, humidity, soil water content, soil temperature, ...</td></tr><tr><td>Environmental Manipulated Factors</td><td>Environmental parameters that can be manipulated on the installation</td><td>Controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>precipitation, nutrients, ...</td></tr><tr><td>Replication Capacity</td><td>Number of experimental units available</td><td>String (max 100)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>16</td></tr></table>

### 4.2.5 Analytical Installation

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Analytical Installation Type</td><td>Stable or Mobile</td><td>Controlled values</td><td>One</td><td>Mandator y</td><td>Yes</td><td>Yes</td><td>Mobile</td></tr><tr><td>Categories</td><td>Analysis categories that can be found on the installation</td><td>Controlled values</td><td>One</td><td>Mandator y</td><td>Yes</td><td>Yes</td><td>Isotopes</td></tr><tr><td>Analysed Parameters</td><td>Parameters that can be analysed on the installation</td><td>Controlled values</td><td></td><td></td><td>Yes</td><td>Yes</td><td>13CO2</td></tr></tbody></table>
<table><tr><td>Instrument Used</td><td>Instruments used to analyse this parameter on the installation</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Picarro G2401</td></tr><tr><td>Precision and Sensitivity</td><td>Instrument precision and sensitivity</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>10 to 50 ppb</td></tr><tr><td>Analytical Capacity</td><td>Number of analysis you can realise (ex : 1000 per day)</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Max sampling frequency: 5s 4 analyzers</td></tr></table>
## 4.3 EOSC model - services

<figure><img src="image_5.png" /><figcaption>Figure 4.3 EOSC model used by the ISIA platform for the AgroServ Catalogue of Services to describe the services provided.</figcaption></figure>
### 4.3.1 Basic Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>ID</td><td>A persistent identifier, a unique reference to the Service/Resource in the context of the EOSC Portal.</td><td>String (max 30)</td><td>One</td><td>Mandatory</td><td>Yes</td><td></td><td>Delivered by EOSC Catalogue</td></tr><tr><td>Abbreviation</td><td>An abbreviation of the Service/Resource Name as assigned by the Provider</td><td>String (Max 20)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>AE - VRE</td></tr><tr><td>Name</td><td>Service/Resource Full Name as assigned by the Provider.</td><td>String (max 80)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Agroecology Virtual Research Environment</td></tr><tr><td>Service/ Resource Organisation</td><td>The name (or abbreviation) of the organisation that manages or delivers the service/resource, or that coordinates</td><td>Provide r ID</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>LifeWatch ERIC</td></tr></tbody></table>
<table><tr><td></td><td>resource delivery in a federated scenario.</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Service/ Resources<br/>Provider(s)</td><td>The name(s) (or abbreviation(s)) of Provider(s) that manage or deliver the Service/Resource in federated scenarios.</td><td>Provide r IDs</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>LifeWatch ERIC</td></tr><tr><td>Webpage</td><td>Webpage with information about the Service/Resource usually hosted and maintained by the Provider.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://www.lifewatch.eu</td></tr></table>
### 4.3.2 Marketing Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multipl icity</td><td>Required</td><td>Public</td><td>Descriptiv e sheet</td><td>Example</td></tr></thead><tbody><tr><td>Description</td><td>A high-level description in fairly non- technical terms of a) what the Service/Reso urce does, the functionality it provides and Service/Reso urces it enables to access, b) the benefit to a user/custome r delivered by a Resource; benefits are usually related to alleviating</td><td>String (max 1000)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Lifewatch ERIC is a European Research Infrastructure that provides e-Science research facilities to scientists, with a thematic focus on biodiversity, ecosystem functions and services research, including agroecology. Lifewatch ERIC achieves this by providing access to a multitude of resources and services that enable researchers to conduct their work and drive innovation.<br/><br/>One of these services is the design and implementation of a Virtual Research Environment (VRE). A VRE is a web-based workspace that provides data users with a comprehensive suite of services and tools to support their data-related work. These tools include centralised access to data, data processing, visualisation of data, sharing of results, and other e-services. By using a VRE, data-users can work more efficiently with data, collaborate more effectively with other data-users stakeholders, and generate new knowledge in their field.<br/><br/>In agroecology, a VRE provides data users with a platform for networking, data gathering and integration, data analysis and visualisation and artificial intelligence (AI) deep learning. The VRE allows data-users to identify and engage with their community while gathering and integrating data from various sources. The VRE offers computing power through high data analysis</td></tr></tbody></table>
<table><tr><td></td><td>pains (e.g., eliminate undesired outcomes, obstacles or risks) or producing gains (e.g. increased performance, social gains, positive emotions or cost saving), c) list of customers, communities, users, etc. using the Resource.</td><td></td><td></td><td></td><td></td><td>capacities such as the Picasso supercomputing centre, as well as storage capacity and data maintenance. Data users can also replicate and share the processes of data analysis, including workflows, models, and algorithms. Additionally, the VRE supports the use of Artificial intelligence (AI), deep learning and digital twins for more advanced research. The VRE in agroecology could also offer training and capacity building opportunities and facilitate dissemination and communication of research findings to relevant stakeholders.<br/><br/>Using a VRE provides many benefits to the agroecology community. These <strong>benefits</strong> include improved efficiency and collaboration, access to advanced computing resources, the ability to analyse and visualise data in new and innovative ways, and the potential for increased research productivity and impact.</td></tr><tr><td>Tagline</td><td>Short catch-phrase for marketing and advertising purposes. It will be usually displayed</td><td>String (max 100)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Unleashing the data-users potential with Lifewatch ERIC's Virtual Research Environments - the ultimate tool for seamless collaboration and data-driven innovation in Agroecology</td></tr></table>
<table><tr><td></td><td>close to the Resource name and should refer to the main value or purpose of the Resource.</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Logo</td><td>Link to the logo/visual identity of the Resource. The logo will be visible at the Portal. If there is no specific logo for the Resource the logo of the Provider may be used.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td></tr><tr><td>Multimedia</td><td>Link to video, screenshots or slides showing details of the Resource.</td><td>URL</td><td>Multipl e</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://www.lifewatch.eu/photo-video-gallery/</td></tr></table>

<figure><img src="image_6.png" /></figure>
<table><tr><td>Multimedia Name</td><td>Short description of the Multimedia content</td><td>String (Max 100)</td><td>Multipl e</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Website Videos and photos</td></tr><tr><td>Use Cases</td><td>Link to use cases supported by this Resource.</td><td>URL</td><td>Multipl e</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://community.lifewatch.eu/working-groups/biodt/</td></tr><tr><td>Use Cases Name</td><td>Short description of the Use Case content</td><td>String (Max 100)</td><td>Multipl e</td><td>Optional</td><td>Yes</td><td>Yes</td><td>BIODT: Biodiversity Digital Twin</td></tr></table>
### 4.3.3 Classification information

<table><thead><tr><th></th><th>Definition</th><th>Type</th><th>Multiplicity</th><th>Required</th><th>Public</th><th>Descriptive sheet</th><th>Example</th></tr></thead><tbody><tr><td>Scientific Domain</td><td>The branch of science, a scientific discipline that is related to the Service/ Resource.</td><td>List of controlled values (See Table 9)</td><td>Multiple</td><td>Mandatoriy</td><td>Yes</td><td>Yes</td><td>Agricultural Sciences Natural Sciences Social Sciences</td></tr><tr><td>Scientific Sub-domain</td><td>The sub branch of science, the scientific subdiscipline that is related to the Service/Resource.</td><td>List of controlled values (See Table 9)</td><td>Multiple</td><td>Mandatoriy</td><td>Yes</td><td>Yes</td><td>Agricultural Biotechnology Agriculture, Forestry & Fisheries Biological Sciences Computer & Information Sciences Earth & Related Environmental Sciences Economics & Business Environmental Biotechnology Environmental Engineering Political Sciences Social & Economic Geography Veterinary Sciences</td></tr><tr><td>Category</td><td>A named group of Resources that offer access to the same type of Service/Resource or capabilities.</td><td>List of controlled values</td><td>Multiple</td><td>Mandatoriy</td><td>Yes</td><td>Yes</td><td>Aggregators & Integrators Applications Compute Consulting & Support Data Data Analysis Data Management Data Storage Development Resources Education & Training Instrument & Equipment Network Operations & Infrastructure Management Services Software</td></tr><tr><td>Sub-category</td><td>A named group of Service/Resources that offer access to the same type of Service/Resource or capabilities, within the defined Resource category</td><td>List of controlled values</td><td>Multiple</td><td>Mandatoriy</td><td>Yes</td><td>Yes</td><td>Orchestration</td></tr></tbody></table>
<table><tr><td>Target Users</td><td>Type of users/customers that commissions a Provider to deliver a Service/Resource.</td><td>List of controlled values</td><td>Multiple</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td></td></tr><tr><td>Access Type</td><td>The way a user can access the Service/Resource (Remote, Physical, Virtual, etc.)</td><td>List of controlled values (See Table 10)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Virtual</td></tr><tr><td>Access Mode</td><td>Eligibility/criteria for granting access to users (excellence-based, free- conditionally, free etc.)</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Free Conditionally</td></tr><tr><td>Tags</td><td>Keywords associated to the Service/Resource to simplify search by relevant keywords.</td><td>String (max 50)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Blockchain, Data analysis, Data gathering, Data visualisation, Modelling, Simulation tools, Tokenization, Virtual Research Environment</td></tr></table>

<figure><img src="image_7.png" /></figure>
### 4.3.4 Geographical and language availability information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Geographical Availability</td><td>Locations where the Service/Resource is offered.</td><td>List of controlled values (See Table 3)</td><td>Multiple</td><td>Mandatary</td><td>Yes</td><td>Yes</td><td></td></tr><tr><td>Language Availability</td><td>Languages of the (user interface of the) Service/Resource.</td><td>List of controlled values</td><td>Multiple</td><td>Mandatary</td><td>Yes</td><td>Yes</td><td>United Kingdom of Great Britain and Northern Ireland</td></tr></tbody></table>

### 4.3.5 Resource location information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Resource Geographical Location</td><td>List of geographic locations where data, samples, etc. are stored and processed</td><td>List of controlled values (See Table 3)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Spain</td></tr></tbody></table>
### 4.3.6 Contact information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Main Contact/Resource Owner -First Name</td><td>First Name of the Service/Resource's main contact person/manager.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>José Manuel</td></tr><tr><td>Main Contact/Resource Owner -Last Name</td><td>Last Name of the Service/Resource's main contact person/manager.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>Ávila Castuera</td></tr><tr><td>Main Contact/Resource Owner - Email</td><td>Email of the Service/Resource's main contact person/manager.</td><td>Email</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>josem.avila@lifewatch.eu</td></tr><tr><td>Main Contact/Resource Owner - Phone</td><td>Telephone of the Service/Resource's main contact person/manager.</td><td>String (max 20)</td><td>One</td><td>Mandatory</td><td>No</td><td>No</td><td>0034609788444</td></tr><tr><td>Main Contact/Resource Owner - Position</td><td>Position of the Service/Resource's main contact person/manager.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>No</td><td>No</td><td>Agroecology Coordinator</td></tr></tbody></table>
<table><tr><td>Main Contact/Resource Owner - Organisation</td><td>The organisation to which the contact is affiliated</td><td>String (max 50)</td><td>One</td><td>Optional</td><td>No</td><td>No</td><td>LifeWatch ERIC</td></tr><tr><td>Public Contact -First Name</td><td>First Name of the Resource's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Iria</td></tr><tr><td>Public Contact -Last Name</td><td>Last Name of the Resource's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Soto - Embodas</td></tr><tr><td>Public Contact -Email</td><td>Email of the Resource's contact person or a generic email of the Provider to be displayed at the portal.</td><td>Email</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>iria.soto@lifewatch.eu</td></tr><tr><td>Public Contact - Phone</td><td>Telephone of the Resource's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>0034616812551</td></tr><tr><td>Public Contact - Position</td><td>Position of the Resource's contact person to be displayed at the portal.</td><td>String (max 20)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Agroecology Project Manager</td></tr><tr><td>Public Contact - Organisation</td><td>The organisation to which the contact is affiliated</td><td>String (max 50)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>LifeWatch ERIC</td></tr></table>
<table><tr><td>Other Contact - Helpdesk email</td><td>The email to ask more information from the Provider about this Resource.</td><td>Email</td><td>One</td><td>Mandato ry</td><td>Yes</td><td>Yes</td><td>iria.soto@lifewatch.eu</td></tr><tr><td>Other Contact - Security Contact Email</td><td>The email to contact the Provider for critical security issues about this Resource.</td><td>Email</td><td>One</td><td>Mandato ry</td><td>No</td><td>Yes</td><td>securas@lifewatch.eu</td></tr></table>

### 4.3.7 Maturity information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Technology Readiness Level</td><td>The Technology Readiness Level of the Resource (to be further updated in the context of the EOSC).</td><td>List of controlled values</td><td>One</td><td>Mandato ry</td><td>Yes</td><td>Yes</td><td>7 - system prototype demonstration in operational environment</td></tr><tr><td>Life Cycle Status</td><td>Phase of the Resource life-cycle.</td><td>List of controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Beta</td></tr><tr><td>Certifications</td><td>List of certifications obtained for the Resource (including the certification body).</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Standards</td><td>List of standards supported by the Resource.</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Darwin Core, Ecological Metadata Language, INSPIRE, Others</td></tr></tbody></table>
<table><tr><td>Open Source Technologies</td><td>List of open-source technologies supported by the Resource.</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Blockchain, DRAMA, GIS, Keycloak, Kubernetes, Minio, NodeJS, Openstack</td></tr><tr><td>Version</td><td>Version of the Resource that is in force.</td><td>String (max 10)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td></td></tr><tr><td>Last Update</td><td>Date of the latest update of the Resource.</td><td>Date (dd/mm/yy) (10)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>11/05/2023</td></tr><tr><td>Change Log</td><td>Summary of the Resource features updated from the previous version.</td><td>String (max 1000)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>https://tesseract.lifewatch.dev/</td></tr></table>

### 4.3.8 Dependencies information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Required Resources</td><td>List of other Resources required to use this Resource.</td><td>Resource IDs</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Related Resources</td><td>List of other Resources that are commonly used with this Resource.</td><td>Resource IDs</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://metadatacatalogue.lifewatch.eu</td></tr></tbody></table>
<table><tr><td>Related Installations</td><td>List of suites or thematic installation in which the Resource is engaged or Providers (Provider groups) contributing to this Resource.</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Copernicus Climate Change Service</td></tr><tr><td>Catalogue</td><td>The Catalogue this Resource is originally registered at.</td><td>Catalogue ID</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>No</td></tr></table>

### 4.3.9 Attribution information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Funding Body</td><td>Name of the funding body that supported the development and/or operation of the Resource.</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>European Commission (EC)</td></tr><tr><td>Funding Program</td><td>Name of the funding program that supported the development and/or operation of the Resource.</td><td>List of controlled values</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>Other</td></tr><tr><td>Grant/Project Name</td><td>Name of the project that supported the development and/or operation of the Resource.</td><td>String (max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>No</td><td>101058020 - AgroServ - HORIZON-INFRA-2021-SERV-01</td></tr></tbody></table>
### 4.3.10 Management Information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Helpdesk Page</td><td>The URL to a webpage to ask for more information from the Provider about this Resource.</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://www.lifewatch.eu/help-desk/</td></tr><tr><td>User information</td><td>Link to the Resource user manual and documentation.</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://training.lifewatch.eu/</td></tr><tr><td>Terms of Use</td><td>Webpage describing the rules, Resource conditions and usage policy which one must</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://workdrive.lifewatch.eu/external/1e06f91acf1d951698c67502238fdafc28de83caf61f2f4db6a52ca7b5849ed0</td></tr></tbody></table>
<table><tr><td></td><td>agree to abide by to use the Resource.</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Privacy Policy</td><td>Link to the privacy policy applicable to the Resource.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>https://workdrive.lifewatch.eu/external/1e06f91acf1d951698c67502238fdafc28de83caf61f2f4db6a52ca7b5849ed0</td></tr><tr><td>Access Policy</td><td>Information about the access policies that apply</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://workdrive.lifewatch.eu/external/1e06f91acf1d951698c67502238fdafc28de83caf61f2f4db6a52ca7b5849ed0</td></tr><tr><td>Resource Level</td><td>Web Page with information about the levels of performance that a Provider is expected to deliver.</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td></td><td>No</td></tr></table>
<table><tr><td>Training Information</td><td>Webpage to training information on the Resource.</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://training.lifewatch.eu/</td></tr><tr><td>Status Monitoring</td><td>Webpage with monitoring information about this Resource</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td></td><td>https://status.lifewatch.dev</td></tr><tr><td>Maintenance</td><td>Webpage with information about planned maintenance windows for this Resource</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td></td><td>https://status.lifewatch.dev</td></tr></table>
### 4.3.11 Access and order information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Order Type</td><td>Information on the order type (requires an ordering procedure, or no ordering and if fully open or requires authentication)</td><td>List of controlled values</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>Order required</td></tr><tr><td>Order</td><td>Webpage through which an order for the Resource can be placed</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>securas@lifewatch.eu</td></tr></tbody></table>

### 4.3.12 Financial information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Payment Model</td><td>Webpage with the supported payment models and restrictions that apply to each of them</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>-</td></tr><tr><td>Pricing</td><td>Webpage with the information on the price scheme for this Resource in case the customer is charged for it.</td><td>URL</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>-</td></tr></tbody></table>
## 4.4 Metadata fields for additional Information – services

<figure><img src="image_8.png" /><figcaption>Figure 4.4 The AgroServ metadata fields for additional information on services provided. This table, in particular, needs to be adapted to the needs of IRISCC.</figcaption></figure>
### 4.4.1 Marketing information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Main image for the descriptive sheet</td><td>This image will appear at the top of the description sheet and will be representative of the service.</td><td>URL</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td><img src="https://i.imgur.com/123456.png" alt="VREs & VLAB LifeWatch ERIC"></td></tr><tr><td>General description</td><td>What the service does. Short description.</td><td>String (Max 1000)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>A Virtual Research Environment (VRE) is a versatile web-based workspace that allows data users to conduct data-related work more efficiently and fosters collaboration among diverse users, with the goal of generating new knowledge. A VRE typically encompasses centralised data access, processing, visualisation, result sharing, and other e-services. The VRE can be utilised to address both scientific and managerial inquiries and</td></tr></tbody></table>
<table><tr><td></td><td></td><td></td><td></td><td></td><td>has applications across various fields, including agroecology.<br/><br/>In agroecology, the VRE is a web-based workspace that provides data-users with a platform for networking, data gathering and integration, data analysis and visualisation, and artificial intelligence (AI) deep learning. The VRE allows researchers to identify and engage with their community while gathering and integrating data from various sources. It offers computing power through high data analysis capacities such as the Picasso supercomputing centre, storage capacity, and data maintenance.<br/><br/>Additionally, researchers can share their data analysis processes, including workflows, models, and algorithms. The VRE also supports the use of AI-deep learning and digital twins for more advanced research.<br/><br/>Moreover, the VRE in agroecology could offer training and capacity building opportunities and facilitate the dissemination and communication of research findings to relevant stakeholders.</td></tr></table>
<table><tr><td></td><td></td><td></td><td></td><td></td><td></td><td>By providing a collaborative workspace and access to essential services, the VRE in agroecology enables data-users to conduct data-related work more efficiently and effectively, leading to the generation of new knowledge and advancements in the field of agroecology.</td></tr><tr><td>Functionaliti es it provides</td><td>Details of the regular and optional features provided by the service</td><td>String (Max 1000)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>A Virtual Research Environment (VRE) is a versatile web-based workspace that allows data users to conduct data-related work more efficiently and fosters collaboration among diverse users, with the goal of generating new knowledge. A VRE typically encompasses centralized data access, processing, visualization, result sharing, and other e-services. The VRE can be utilized to address both scientific and managerial inquiries and has applications across various fields, including agroecology.</td></tr><tr><td>Users benefits</td><td>Eliminate undesired outcomes, obstacles or risks</td><td>URL</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>In agroecology, the VRE is a web-based workspace that provides data-users with a platform for networking, data gathering and integration, data analysis and</td></tr></table>
<table><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>visualization, and artificial intelligence (AI) deep learning. The VRE allows researchers to identify and engage with their community while gathering and integrating data from various sources. It offers computing power through high data analysis capacities such as the Picasso supercomputing center, storage capacity, and data maintenance. Additionally, researchers can share their data analysis processes, including workflows, models, and algorithms. The VRE also supports the use of AI-deep learning and digital twins for more advanced research.</td></tr><tr><td>Users producing gains</td><td>Increase performance, social gains, positive emotions or cost saving</td><td>String (Max 100)</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Moreover, the VRE in agroecology could offer training and capacity building opportunities and facilitates the dissemination and communication of research findings to relevant stakeholders. By providing a collaborative workspace and access to essential services, the VRE in agroecology enables data-users to conduct data-related work more efficiently and effectively, leading to the generation of new knowledge and advancements in the field of agroecology.</td></tr></table>
<table><tr><td>References</td><td>Customers, Communities, Publications</td><td>URL</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>https://community.lifewatch.eu/</td></tr><tr><td>Use cases</td><td>Short description of the Use Case content</td><td>URL</td><td>Multiple</td><td>Optional</td><td>Yes</td><td>Yes</td><td>-</td></tr></table>

### 4.4.2 Location and country

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Latitude</td><td>Latitude coordinate of the installation (in decimals: 60.924530 for 6055'8.3"N)</td><td>String (7)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>virtual access</td></tr><tr><td>Longitude</td><td>Longitude coordinate of the installation (in decimals: 11.451259 for 1127'04.5"E)</td><td>String (7)</td><td>One</td><td>Mandatory</td><td>Yes</td><td>Yes</td><td>virtual access</td></tr><tr><td>Country Code</td><td>Country name abbreviation (France: FR)</td><td>Controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>virtual access</td></tr></tbody></table>
### 4.4.3 Dependencies information

<table><thead><tr><td>Field Name</td><td>Definition</td><td>Type</td><td>Multiplicity</td><td>Required</td><td>Public</td><td>Descriptive sheet</td><td>Example</td></tr></thead><tbody><tr><td>Required / Related Resource</td><td>Is the resource is required to use the service or only a related resource?</td><td>List of controlled values</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Required</td></tr><tr><td>Required or Related Resource</td><td>Resource name</td><td>String (Max 100)</td><td>One</td><td></td><td></td><td></td><td>N2 gaz for Picarro Oven</td></tr><tr><td>Measured parameter</td><td>Measured parameters by the required/Related Resource</td><td>String (Max 100)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>-</td></tr><tr><td>Precision / Sensitivity</td><td>Measuring range and precision</td><td>String (Max 100)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>-</td></tr><tr><td>Analytical Capacity</td><td>Resource measurement capacity (sampling frequency for continuous measurements, samples processed per day or per hour, ...)</td><td>String (Max 100)</td><td>One</td><td>Optional</td><td>Yes</td><td>Yes</td><td>Sampling frequency: 5 mins</td></tr></tbody></table>
## 5. Adaptations and changes compared to the AgroServ service catalogue (AgroServ test version, June 2024)

The original IRISCC proposal included an overview of all existing services related to climate change risks (Table 5.1). The first release of the IRISCC catalogue of existing services should first and foremost give easy access to more information about these specific services based on which system(s) and risk(s) the user is interested in. Overall, 'System' and 'Risk' are therefore the two core search filters of the online IRISCC service catalogue.

The structure of the current search terms in the AgroServ Catalogue of Services (Figures 5.1 - 5.6) therefore needs to be adapted accordingly, i.e. after "Free text" and "Keywords" search filters, should be "System" and "Risk" according to Table 5.1. In testing the current test version of the AgroServ Catalogue of Services we note that:

* Filters (and state of the app) are not persistent when you select a service and go back. This should be resolved.

* For the services that result from the filter, the catalogue sometimes provides only a picture (most of them are not informative at all), the responsible org, and a short(ened) title, which is not enough to make an informed choice. Vertical scrolling list of services with a small thumbnail and then a full title, short abstract (3-4 lines) would be preferred.

* The current setting of the filters is clumsy, the dialogue could be replaced with a simple dropdown box of options that could be checked/unchecked and react to search by typing. All filters except free text could be shown in one horizontal line (or in a column left of the service list).

* The IRISCC-defined services from each service provider should be clearly described in a few lines of text, e.g. similar to the current style of the ACTRIS Catalogue of Services (Figure 5.7 and 5.8).

* To improve the usability of the IRISCC Service Catalogue, the target group and their needs for information discovery should be considered in all steps of the catalogue development (i.e., refer to stakeholder mapping and analysis report, IRISCC D1.1).

* In general, UI (User Interface) design should focus on intuitive navigation, clear search functionalities, and visually appealing presentation.
<table><caption>Table 5.1. The original table 1.1 from the IRISCC proposal, highlighting number of existing services across IRISCC beneficiaries and affiliated entities for each System / Risk combination.</caption><thead><tr><th>System / Risk</th><th>Climate warming</th><th>Desertification</th><th>Cryo / snow</th><th>Sea level rise</th><th>Ocean acidification</th><th>Heat waves</th><th>Drought</th><th>Floods</th><th>Storm surges</th><th>Fires</th><th>Landslides</th><th>Disease vectors, pests</th><th>Air and water pollution</th></tr></thead><tbody><tr><td>Urban areas</td><td>9</td><td>5</td><td>1</td><td>1</td><td></td><td>12</td><td>8</td><td>5</td><td>2</td><td>10</td><td>1</td><td>9</td><td>12</td></tr><tr><td>Rural areas</td><td>15</td><td>8</td><td>2</td><td>1</td><td></td><td>16</td><td>11</td><td>6</td><td>2</td><td>13</td><td>1</td><td>7</td><td>11</td></tr><tr><td>Mountain communities</td><td>7</td><td>1</td><td>4</td><td>1</td><td></td><td>4</td><td>5</td><td>2</td><td>2</td><td>4</td><td>3</td><td>3</td><td>9</td></tr><tr><td>Coastal communities</td><td>4</td><td>4</td><td>1</td><td>2</td><td>1</td><td>3</td><td>3</td><td>2</td><td>3</td><td>7</td><td>1</td><td>2</td><td>5</td></tr><tr><td>Managed forests</td><td>16</td><td>4</td><td>3</td><td>1</td><td></td><td>15</td><td>16</td><td>4</td><td>1</td><td>10</td><td>1</td><td>6</td><td>10</td></tr><tr><td>Agro ecosystems</td><td>16</td><td>8</td><td>2</td><td>1</td><td></td><td>14</td><td>16</td><td>7</td><td>2</td><td>10</td><td>1</td><td>8</td><td>15</td></tr><tr><td>Aquaculture/ fisheries</td><td>8</td><td></td><td>1</td><td>1</td><td>6</td><td>5</td><td>3</td><td>1</td><td>1</td><td>3</td><td>1</td><td>7</td><td>7</td></tr><tr><td>Forests</td><td>24</td><td>7</td><td>3</td><td>1</td><td></td><td>19</td><td>17</td><td>6</td><td>3</td><td>15</td><td>1</td><td>8</td><td>14</td></tr><tr><td>Grasslands / shrublands</td><td>15</td><td>7</td><td>3</td><td>1</td><td></td><td>12</td><td>17</td><td>8</td><td>2</td><td>7</td><td>1</td><td>6</td><td>10</td></tr><tr><td>Coastal</td><td>15</td><td>3</td><td>1</td><td>6</td><td>11</td><td>14</td><td>4</td><td>4</td><td>5</td><td>6</td><td>1</td><td>8</td><td>17</td></tr><tr><td>Wetlands</td><td>13</td><td></td><td>1</td><td>4</td><td></td><td>12</td><td>8</td><td>4</td><td>2</td><td>5</td><td>1</td><td>5</td><td>7</td></tr><tr><td>Freshwater</td><td>10</td><td></td><td>1</td><td>3</td><td></td><td>10</td><td>7</td><td>3</td><td>1</td><td>3</td><td>1</td><td>4</td><td>7</td></tr><tr><td>Marine</td><td>15</td><td></td><td>1</td><td>6</td><td>11</td><td>12</td><td></td><td>3</td><td>3</td><td></td><td>1</td><td>7</td><td>13</td></tr></tbody></table>
<figure><img src="image_9.png" /><figcaption>Figure 5.1 Overview of the search terms in the test version of the AgroServ service catalogue.</figcaption></figure>
<figure><img src="image_10.png" /><figcaption>Figure 5.2 Example of how the “Keywords” search filter is shown in the AgroServ Catalogue of Services.</figcaption></figure>
<figure><img src="image_11.png" /><figcaption>Figure 5.3 Example of how the “Scientific domains” search filter is shown in the AgroServ Catalogue of Services.</figcaption></figure>
<figure><img src="image_12.png" /><figcaption>Figure 5.4 Example of how the “Scientific subdomains” search filter is shown in the AgroServ Catalogue of Services.</figcaption></figure>
<figure><img src="image_13.png" /><figcaption>Figure 5.5 Example of how the "Research Infrastructures" search filter is shown in the AgroServ Catalogue of Services.</figcaption></figure>
<figure><img src="image_14.png" /><figcaption>Figure 5.6 Example of how the “Country” search filter is shown in the AgroServ Catalogue of Services.</figcaption></figure>
<figure><img src="image_15.png" /><figcaption>Figure 5.7 Example of how individual services are shown to the user in the ACTRIS Catalogue of Services (overview page).</figcaption></figure>
<figure><img src="image_16.png" /><figcaption>Figure 5.8 Example of how individual services are shown to the user in the ACTRIS Catalogue of Services (detailed page).</figcaption></figure>
# 6. Adapting the PASS access management tool and integration with ISIA

Transnational Access (TA; physical, remote or hybrid) to services in the IRISCC Catalogue is likely to be requested by users in three ways, based on the specifics of the access programme defined in T.7.3:

* anytime by placing a service request through the IRISCC Catalogue to the PASS TA management platform;

* in response to an annual call for access or a rolling call with no fixed end date on the PASS. Links to the annual/rolling call will also be provided on the IRISCC Catalogue of Services and the IRISCC webpage;

* in response to a dedicated call for access on the PASS, launched to promote specific research that is of interest to the scientific community to tackle particular science or societal challenges related to climate change risks. Links to the dedicated/topical calls will also be provided on the IRISCC Catalogue of Services and the IRISCC webpage.

All requests for TA to the IRISCC services will be handled by the WP8 Team with the support of the PASS web tool. PASS enables the central management of access and helps to automatize as much as possible the workflows established for the access process with the control of each step. A technical solution is needed to ensure the integration of the PASS access management tool with the IRISCC Catalogue of Services in ISIA. This solution will be studied in parallel with the development of the Catalogue and the access programme. Taking into account the particular details of the yet-to-be-defined access programme, as well as the metadata model and tags for the services in the IRISCC catalogue, the integration with PASS will ensure that service requests placed through the Catalogue (for instance, by clicking on a 'request the resource' button) will guide the users/requests in one of the following ways, depending on the available technical solutions:

* Users will be directed to the specific application form of the relevant call under which TA to the requested service is offered. The form will retrieve service information and enable users to directly fill in all the needed information to consent to proper evaluation based on the relevant access mode for selection.
* Option 2: Users will be prompted for the compilation of a pre-application form on the PASS platform to add basic preliminary information (eligibility issues) on top of the service requested. The WP8 Team will screen the request and convert it into the full application form of the relevant call for the user to fill in all the needed information to consent to proper evaluation.

<figure><img src="image_17.png" /><figcaption>Figure 6.1. The PASS platform is used e.g. by ACTRIS to manage the transnational access (TA) calls.</figcaption></figure>
# 7. Metadata collection

Similar to the other existing service catalogues currently available on ISIA, IRISCC service providers must have an interface in ISIA dedicated to their own facility and the services they provide, to which only invited users will have access. They must be able to update information about facilities and services via dedicated forms (Figures 7.1, 7.2, and 7.3). These forms are the single-entry points for entering facility and service information and allow automatic dissemination to the various catalogues, for example AgroServ, CatRIs and any other catalogue with an API to automatically update the data. With single-point entry, service providers only have to register information once, while the information can be retrieved for multiple catalogues of services. The information can then be updated automatically and periodically according to the needs of IRISCC.

The IRISCC Catalogue of Services should preferably provide the opportunity to fill out and upload a .csv template with all mandatory data fields to avoid the need for a lot of copy-pasting from each service provider into the online form.

<figure><img src="image_18.png" /><figcaption>Figure 7.1 Screenshot from existing AgroServ Catalogue of Services. Note that a new version will be released during summer 2024 with a different and more user-friendly design.</figcaption></figure>
<figure><img src="image_19.png" /><figcaption>Figure 7.2 Screen shot from existing AgroServ Catalogue of Services showing the types of metadata to be provided from each service provider.</figcaption></figure>

<figure><img src="image_20.png" /><figcaption>Figure 7.3 Screen shot from existing AgroServ Catalogue of Services showing metadata fields for “basic information” to be provided from each service provider.</figcaption></figure>
## 8. Conclusions and next steps

As outlined in section 1 of this report, the IRISCC Catalogue of Services will be built using existing technologies and expertise within the IRISCC consortium, i.e. it will be hosted on the ISIA platform by CNRS, France, which already hosts service catalogues of AnaEE France, AnaEE ERIC and the EU-INFRASERV project AgroServ. Access to services will be managed using the PASS platform currently used by the ACTRIS ERIC. This requires the development of a technical integration between ISIA and PASS.

As AgroServ has already been built to provide access to service across multiple RIs, this report focuses on which requirements for the IRISCC Catalogue of Services may need to be adapted to the specific needs of IRISCC. The requirements for the design of the IRISCC Catalogue of Services will evolve over the course of IRISCC for the 2nd and 3rd releases but at this early stage of the IRISCC project this report lists the technical requirements for the 1st release (M12 - March 2025) in details within each section of the report. In summary:

* In building the metadata schema for the additional information needed in IRISCC, existing vocabularies within the IRISCC consortium should always be used if possible (section 2).

* The IRISCC Catalogue of Services must be able to handle all the different types of access identified for IRISCC (section 3).

* The existing metadata schemas from AgroServ to describe additional information on facilities and services need to be adapted to the necessary description of facilities and individual services in IRISCC (section 4).

* Search filters need to be adapted for IRISCC. In particular for the first release of the Catalogue of Services, the two core search filters should be "System" and "Risk". Other improvements of the current handling of search filters for AgroServ are also requested for IRISCC (section 5).

* A technical solution allowing integration of the PASS access management tool and ISIA is needed (section 6).

* An online web interface for service providers to allow updating required information is requested. In addition, preferably the web interface should provide the opportunity to fill out and upload a .csv template with all mandatory data fields for service providers (section 7).

Based on these technical requirements, the next steps are to: first define the mandatory metadata fields for IRISCC service providers from the EOSC-based model and second, to
define the additional information required for the descriptions of facilities and individual
services in IRISCC. Then developers can make the necessary adaptations of ISIA and
services providers can start filling out either online form or a simple .csv template (if
possible) to populate the online web Catalogue of Services. Concurrent with this
development, the study and implementation of a technical solution for the integration of
the PASS access management tool and ISIA should be initiated.

Further, a more detailed technical requirements for the design of the IRISCC Catalogue of
Services will arise as the planned work and developments of new and integrated services
in IRISCC progresses. This report therefore cannot represent a final list of technical
requirements for the design of the IRISCC Catalogue of Services but merely a starting
point for the development at the earliest stage of the IRISCC project. The technical
requirements and the development of the Catalogue of Services will be a continuous,
iterative process throughout the IRISCC project period among the work package activities
in IRISCC and the developers of the web interface. This report will therefore be used as a
starting point of a "living" document that is continuously updated over the course of
IRISCC to reflect the different stages of the development of the IRISCC Catalogue of
Services.