You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »


Day 1,  , 15:00-18:00 CET - Introduction


  • 15:00 - 15:10 - Welcome and introduction

  • 16:00 - 18:00 - Participants data presentations - all participants (see template below)

  • SPHERE asteroid images and shape models (OCA, Nice)

  • MOVIS asteroids NIR colors (AIRA, Bucarest)

  • PDS PPI (UCLA + Iowa Univ)

  • Sunspots and coronal holes catalogues (ROB, Brussels)

  • Asteroid data catalogues (MP3C)

  • Various services at IRAP (Toulouse)

  • Europlanet TA: lab and field studies 

Day 2,  , 15:00-18:00 CET - Discussion

Round table (group discussions)

  •  15:00 - 17:00 - Participants Data/EPN-TAP modelling - all participants
  •  17:00 - 18:00 - Summary of discussions - all participants

Day 3,   15:00-18:00 CET - Tutorial

Tutorial (interactive)

  • 16:30 - 17:15 - Importing data from CSV / SQL - Chloé Azria  

Day 4,  , 15:00-18:00 - CET - Hands-on & implementation


  • 15:00 - 17:00 - Participants implementation - all participants
  • 17:00 - 18:00 - Running / testing / optimising workflow - all participants

Connection info

Please register on: 

The same tools can be used for follow up activities in the forthcoming weeks. If you have any issue, please reach out to Angelo Pio Rossi or Carlos Henrique Brandt 

Software requirements

The workshop will use DaCHS on Docker container as it is meant to be simpler and to have it setup. For that, we need all the participants to have Docker (and, optionally, docker-compose) pre-installed.
Please, follow the instructions for your operating system as per Docker official documentation:

Since the workshop will be hosted on Zoom + asynchronous chat on Discord, we highly recommend using the Desktop app (instead of the web-app).
Please refer to Discord official documentation for install instructions:

We will use VOParis Gitlab instance to exercise in hosting DaCHS/data resources, it is recommended to have Git installed on your system:

See also VESPA Data provider on-boarding process

The workflow with Gitlab for VESPA is outlined below:

  • STEP 1: Data provider team sends request for VESPA support (this is done with the call) 
  • STEP 2:VESPA teams invites an external user to EduTEAMS
  • STEP 3: External user to accept the invitation
  • STEP 4: VESPA to approve the new user and to setup groups memberships on EduTEAMS
  • STEP 5:External user connects to (using the EduTEAMS connection method). This action creates the gitlab account
  • STEP 6: VESPA to setup repositories, membership and groups on voparis-gitlab: External users can now access to their repositories

Documents & templates

Participant presentation template. Please feel free to use your own slides/templates, this is just to loosely guide the structure/content. 


  • No labels