...

Guide for trainers

Planning for

...

Training

According to EOSC-hub DoA, WP11 should provide training plan by M3, M12, and M24

WP11 uses a google sheet for internal management of planned training events. 

...

This training programme is supposed to be a “live document”. New events/contributions from different TSs, CCs and research communities can feed into this programme during the course of the project and contribute to the creation of a knowledge network.

Preparing for

...

Training

When you prepare for any trainings,

1. Please inform WP11 members about new upcoming training events:

   정보
   title HowTo
   Write to training@mailman.eosc-hub.eu specifying: The title of the event The date of the event The type of the event (e.g.: webinar, f2f, hackathon, workshop, tech talk, etc.); The organiser and a key contact for the event The target audience

2. When needed, get supports for
   • Training e-Infrastructure
   • Review and feedback on training materials and delivery
   • Promotion of the trainings
   • Financial supports
3. Register the upcoming event/materials in the Training Catalogue. (see HowTo: Training Catalogue)

Reporting for

...

Training

To facilitate the collection of feedback and statistics, WP11 has prepared the following document templates:

• EOSC-hub_Training_Evaluation_Form_v1

• This document is used to collect feedback about the training event. It has to be distributed to the participants for example at the beginning of the training session (people may leave before the end of the training, so it would be good to distributed it early).

• Participants to training events are kindly invited to fill in the evaluation form before to leave the training room and return it back to the trainers.

• Trainers are tasked to collect the evaluation form at the end of the event.

• EOSC-hub_Training_Event_Reporting_form

• After the event, the trainers are kindly invited to use this template to produce a report about the event. The report will be used to monitor the work plan and produce metrics.

• The report has to be sent to: giuseppe.larocca@egi.eu  

• Care should be taken for data protection issues, e.g., all personal information of participants should be removed if there are not permit from them.  

The training feedback forms are MANDATORY for each training event. It will be used for project reports. All the document templates are available at: https://documents.egi.eu/document/3296

After the event, WP11 members and/or organiser also need to populate:

1. The list of EOSC events, available at: https://wiki.eosc-hub.eu/display/EOSC/Events
2. The dissemination activities, available at: https://wiki.eosc-hub.eu/display/EOSC/Dissemination+Activities

Templates and tools

Communication toolkit, including project logo, word and Powerpoint templates are available at: https://wiki.eosc-hub.eu/display/EOSC/Communications+Toolkit

...

Here we consider the slide presentation type which is the basic request for EOSC-hub services training material.

We recommend an introduction level training material should cover the following aspects:

• Basic information: title, authors, contact of authors, date, versions

• Goal: stating the learning objective of the training material

• Target audience: type of people for who this training material is relevant for

• Context:   

• Where is the service located in the EOSC-hub architecture

• The service can be used to support which phases of a research (data) lifecycle -- this would be easily understood by users

• Service providers’ information

• Development backgrounds

• Introduction: short and clear describe what the service does

• Why should users choose to use the service

• What are the problems the service tries to resolve

• How good the service is comparing to existing technology

• What benefits can the service bring to the users

• Who have already been using the service -- existing user base

• What the service does -- provide information about:

• Service functionalities and features

• Architectures and components

• Related technologies

• Definitions and Terminologies should be provided (or included as notes)

• How can users use the service

• Access interfaces

• Different access options

• Usage modes -- provide examples and use cases

• Reference:

• User guides to get started

• Help desk information

• Quiz or exercise

...