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-hub and EOSC Enhance. The EOSC AISBL may define broader criteria, therefore the criteria are subject to change in the future.
- Who can onboard resources to EOSC
- Resources must be onboarded by a legal entity (although the legal entity may do so on behalf of a project or consortium in which they participate, with the agreement of those groups)
- 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 which are no longer operational or available.
- What resources may be connected to EOSC?
- Services. At present only services are being onboarded.
- It must be an actual service
- It must be a specific service offered ‘live’ to customers . 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 .
- 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.
- Services must meet at least one of:
- The service must be targeted to EOSC and EOSC communities .
- The service must build on or leverage EOSC capabilities to serve some other community.
- Other research products (Rules and onboarding process pending)
- A provider profile and resource profiles for each resource must be filled, including 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
- The Helpdesk must be able to answer queries in English at a minimum.
- Resources must be both available in Europe and available in a European language .
- The provider must agree to periodically update data on themselves and their resources to keep it current (to be covered in Provider agreement, TBD)
 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.
 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.
 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.
 For instance, services through the Digital Innovation Hubs which build on EOSC expertise, resources and capabilities to create new, innovative commercial services
 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 Enhance, OpenAIRE Advance and EOSC-hub) 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 firstname.lastname@example.org.