Difference between revisions of "Service onboarding team"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | Onboarding of a resource (service or repository) into the EOSC includes all practical activities taken to incorporate a research resource into the EOSC federation. These activities represent a wide range of support actions to be directly offered to the resource provider in the onboarding process. For example, for a particular resource, this could be the establishment of the support channel, integration with the existing EOSC services, data FAIRification, integration with monitoring, accounting, or authentication/ authorization frameworks, preparation of end-user tutorials, access policies, or terms of use, etc. Therefore, it is crucial to establish an onboarding team within the project with wide-ranging expertise and experience to cover all diverse aspects of the onboarding process. Furthermore, this team should produce a set of reusable guidelines, best practices, and other recommendations to reduce barriers the service providers face in the EOSC integration. | ||
| + | |||
| + | |||
{| class="wikitable" | {| class="wikitable" | ||
! Country | ! Country | ||
| Line 67: | Line 70: | ||
|- | |- | ||
|style="background:#f0f0f0;vertical-align:text-top;"| North Macedonia | |style="background:#f0f0f0;vertical-align:text-top;"| North Macedonia | ||
| − | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:boro.jakimovski-at-finki.ukim.mk Boro Jakimovski] (UKIM)<br/> [mailto: | + | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:boro.jakimovski-at-finki.ukim.mk Boro Jakimovski] (UKIM)<br/> [mailto:vojdan.kjorveziroski-at-finki.ukim.mk Vojdan Kjorveziroski] (UKIM) |
| − | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:anastas.mishev-at-finki.ukim.mk Anastas Mishev] (UKIM) | + | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:anastas.mishev-at-finki.ukim.mk Anastas Mishev] (UKIM)<br/> [mailto:vojdan.kjorveziroski-at-finki.ukim.mk Vojdan Kjorveziroski] (UKIM) |
| − | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:boro.jakimovski-at-finki.ukim.mk Boro Jakimovski] (UKIM) | + | |style="background:#f0f0f0;vertical-align:text-top;"| [mailto:boro.jakimovski-at-finki.ukim.mk Boro Jakimovski] (UKIM)<br/> [mailto:anastas.mishev@finki.ukim.mk Anastas Mishev] (UKIM) |
|- | |- | ||
Latest revision as of 19:44, 4 March 2020
Onboarding of a resource (service or repository) into the EOSC includes all practical activities taken to incorporate a research resource into the EOSC federation. These activities represent a wide range of support actions to be directly offered to the resource provider in the onboarding process. For example, for a particular resource, this could be the establishment of the support channel, integration with the existing EOSC services, data FAIRification, integration with monitoring, accounting, or authentication/ authorization frameworks, preparation of end-user tutorials, access policies, or terms of use, etc. Therefore, it is crucial to establish an onboarding team within the project with wide-ranging expertise and experience to cover all diverse aspects of the onboarding process. Furthermore, this team should produce a set of reusable guidelines, best practices, and other recommendations to reduce barriers the service providers face in the EOSC integration.