EOSC Portal - A gateway to information and resources in EOSC

Press [ esc ] or close+

The following criteria are currently used to validate Providers and Resources to be onboarded within the EOSC Service Portfolio. The criteria are still under development by a joint team consisting of members of EOSC Future and EOSC Enhance (and formerly EOSC-hub). The EOSC AISBL may define broader criteria, therefore the criteria are subject to change in the future. 

  • What groups can onboard to EOSC as a provider?
    • Any group can onboard to EOSC as a Provider, as long as it fills the necessary information in the EOSC Provider Profile. 
    • Those onboarding as a provider should either be a legal entity or connect to the registration of a hosting legal entity already onboarded as a provider under their own profile. 
  • Who can onboard resources to EOSC
    • Providers onboarding a resource must assert that they are able to ensure the resource is delivered by them or their collaborators and agree to remove resources that are no longer operational or available. 
    • Resources should be onboarded by the coordinating or lead provider in case of a federates or jointly provided resource (they are the 'Resource Organisation). Other onboarded providers may be added as supporting or supplementary providers ('Resource providers). 
  • What resources may be connected to EOSC?
    • Services. At present only services are being onboarded.
      • It must be a specific service offered ‘live’ to customers [1]. This may be an IT service, or a human service (e.g. training, consultancy).. 
      • It may not be a research product, for instance, a document, a dataset or a piece of software [2].
      • The Service must be discrete. It must be available and offer value on its own. It may not be only a feature of a larger service available while already using that service. 
      • The Service must by of a reasonable maturity, Technology Readiness 7 or above in order to be listed in the catalogue (and TRL8 or above to allow for integration of ordering) 
      • Services must meet  at least one of:
        • The service must be targeted to EOSC and EOSC communities [3]. 
        • The service must build on or leverage EOSC capabilities to serve some other community.[4]   
    • Other resources, such as research products (data sets, publications, software and other types) will be able to be onboarded at a later date. 
      • NOTE: while research products are not being directly onboarded, services that contain them such as data, software or publication repositories can be onboarded as services. 
  • A provider profile and resource profiles for each resource must be filled, including at a minimum all required fields. 
    • URLs must be Fully Qualified Domain Names (FQDN)
    • Key information must be in English due to the limitations of current project resources (thought this may change in future) 
      • The provider and resource profiles must be in English
      • The basic information in the User Interface for the service must be available in English
      • Privacy statements, terms of use and Service Level Agreements, Specifications and Descriptions must be available in English. Other documentation may be in the native language only. 
      • The Helpdesk or support function must be able to answer queries in English at a minimum.
  • Resources must be both available in Europe and available in a European language [5]. 
  • The provider must agree to periodically update data on themselves and their resources to keep it current (to be covered in an EOSC Provider agreement, under devlopment) 

[1] Filling e.g. the definition according to FitSM-0 - Service: Way to provide value to customers through bringing about results that they want to achieve. Note: In the context of the FitSM standard series, when referring to services, usually IT services are meant. From https://www.fitsm.eu/download/280/ It should not be a generic menu of services from a provider, but the specific services themselves. 

[2] A data repository service providing some annotation, tools over the data sets, enhanced features is likely a service. A simple link to a data file is not. 

[3] For instance, could be a service from the research community for researchers, or if a commercial service, includes a clear offer targeted at EOSC and research customers which addresses them, rather than be a generic commercial service. One example of the latter is a joint procurement framework targeting EOSC. 

[4] For instance, services through the Digital Innovation Hubs which build on EOSC expertise, resources and capabilities to create new, innovative commercial services

[5] See https://europa.eu/european-union/about-eu/eu-languages_en

These criteria are managed by the EOSC Portal Onboarding Team:A collaboration of EOSC Future and EOSC Enhance (Formely also including EOSC-hub, OpenAIRE Advance and eInfraCentral).  They are developed in light of the evolving EOSC Rules of Participation, which provide higher-level guidance. If you have an enquiry or concern about these criteria please contact onboarding@eosc-portal.eu