Key

Scope of the call

The aim of the VESPA activity in the Europlanet 2020-RI programme is to make Planetary Science and Solar System data accessible and searchable through a system derived from the Astronomical Virtual Observatory. Up to 50 new databases are expected to be made available on-line during the 4-year Europlanet 2020-RI programme. To get a better idea of what this system is about, just take a look at the VESPA data query service.

...

Typical case: You have generated a dataset for a publication, you want to share it using an advanced query system

Secondary case: You're working with a lot of data subsets from one or several archives, and you want to enhance the access with advanced query capabilities (e.g., ground based telescopic support for Rosetta; several disconnected spectral databases of minerals, etc)

Any other situation is acceptable (e.g., historical datasets, pedagogic tools…), but interest to the Europlanet community must be demonstrated.

The last day of the workshop is planned to be dedicated to interested teams who want to discuss how to connect simulation codes in VESPA.

Post-workshop telecon, May 2019

Finalization review performed with the proposers, June 2019

Service delivery date: June 2019

FAQ

Who is eligible?

Research teams in Planetary Science or neighbouring fields. Primarliy support will be given to EU teams but collaboration with teams external to the EU will be considered by the VESPA management team. VESPA beneficiaries will implement services through other means.

What do I gain?

Visibility for your published work/observations.

Satisfaction of providing the community with high quality reference data.

A prompt answer to daily mails asking for your data!

If you already have a database, VESPA will provide high level search functions on its contents, on-line visu / analysis capacities, and cross-correlation with other datasets in neighbouring fields, with minimum efforts. Your data will be searchable from the VESPA interface.

What is the outcome?

At the end of the process, you will have a TAP server installed in your institute, with one data service connected to the Planetary Science Virtual Observatory and the know-how to implement additional services and to share more data. A single server can accommodate many services in Planetary Science, Heliophysics, and Astronomy.

Which data?

Derived / highly processed data are preferred, because their content can be of interest to other communities.

What type of data access / data status?

Data will be publicly open/accessible - you are responsible for checking the legal status of the data you wish to provide, and accept to share them publicly.

Which support?

VESPA provides support to design and install a data service through a preliminary telecon, workshop, and a post-workshop helpdesk. A finalization review will be performed with the proposer.

What do VESPA pay for?

We pay for a trip to the workshop venue, economy class + local expenses (for 2 persons per team).

What skills does this require?

You need a science expert of the field and a software engineer - at least someone not relectant to editing SQL routine templates and installing applications. The installation process has been optimized to remain as light as possible.

Where will the data be located?

Data services are installed in the proposing institutes, which have to set up and maintain a server and a database. Services may link to data stored in external repositories - European data repositories are available for this purpose (e.g., Zenodo). In case the service links to data existing in a Planetary Science repository already providing a service to the community (such as ESA's PSA), the added value must be clearly demonstrated.

Personnel available for setting up a service (2-3 telecons + workshop): at least 1 scientist + 1 engineer (FTE involved depend on lots of factors)

Sustainability (at least for 5 years), and estimated ability to maintain the service (e.g.: is there any data distribution system already installed?)

Additional databases that could be implemented in the future by the team

Consensus/agreement in the proposing team is important, in particular to ensure that local technical support will be available

Example

Proposals must address the following (in addition to above criteria), with reasonable details to allow the VESPA team to assess the level of maturity. These are mandatory fields in the submission form: