Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Who is eligible?
    • Research teams in Planetary Science or neighbouring fields. Primarily 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 reluctant 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. 
  • How many proposals are selected?
    • The baseline is to select 4 to 5 proposals for this call.
  • Who is evaluating?
    • VESPA VA-task3 members (IRAP/Toulouse, IWF/Graz, IAP/Prague, IAPS/Rome, Observatoire de Paris)
  • Are non-European teams also eligible?
    • Yes - although travelling refund must be reviewed first. 
  • When will the next call take place:
    • This is the last call.
  • What does VESPA mean by the way?
    • VESPA stands for Virtual European Solar and Planetary Access. This time, it will lead you to Prague, capital city of the Czech republicRome, Italy.

Evaluation criteria

  • Scientific merit:
    • Existing publications
    • Data quality (used for publication? + data quality assessment plan)
    • Size of the community
    • Added value of proposed database/service, compared to existing databases/archives
  • Status of the data is of course a major issue (reserved services sharing proprietary data are currently studied only internally to VESPA).
  • Science domain balance in VESPA. Pre-selection may occur if the subject matter is not mature enough in VESPA - in which case VESPA will be happy to study the problem together with the proposing team.
  • Readiness level of data products and database:
    • Data readily available at time of proposal/workshop
    • Finalized, directly usable data products are expected/preferred
    • Standard format and available metadata (or plan to derive them from the data products/documentation)
  • Team capabilities:
    • Scientific assessment of data quality, possible update of dataset, recalibration, extension...
    • 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

...