Work in Progress
Please don't use this Tutorial for now, we are currently updating it.
EPN2020-RI
EUROPLANET2020 Research Infrastructure
H2020-INFRAIA-2014-2015
Grant agreement no: 654208
Document: WP6-task2-002-v0.1(17)
EPN-TAP Installation for VESPA Data Provider Tutorial — Part 2
Date: $action.dateFormatter.formatGivenString("yyyy-MM-dd",$content.getLastModificationDate())
Start date of project: 01 September 2015
Duration: 48 Months
Responsible WP Leader: OBSPARIS / Stéphane Erard
Project co-funded by the European Union's Horizon 2020 research and innovation programme | ||
Dissemination level | ||
PU | Public | |
PP | Restricted to other programme participants (including the Commission Service) | |
RE | Restricted to a group specified by the consortium (including the Commission Services) | |
CO | Confidential, only for members of the consortium (excluding the Commission Services) | |
Project Number | 654208 |
Project Title | EPN2020 - RI |
Project Duration | 48 months: 01 September 2015 – 30 August 2019 |
Document Number | WP6-task2-002-v0.1(17) |
Delivery date | 2015.11.21 |
Title of Document | EPN-TAP Installation for VESPA Data Provider Tutorial — Part 2 |
Contributing Work package (s) | WP6 |
Dissemination level | PU |
Author (s) | Baptiste Cecconi, Pierre Le Sidaner, Stéphane Erard, Renaud Savalle, Markus Deimletner, Paul Sladen |
Abstract: |
Document history (to be deleted before submission to Commission) | ||||
Date | Version | Editor | Change | Status |
21 Jan 2016 | 0.1 | First issue | draft | |
| ||||
Table of Contents
1. Introduction
This document presents the configuration procedure of the VESPA service installed during the first art of the tutorial. We propose here to set up the Registry configuration (Section 2), as well as a test TAP service (Section 3).
In all this document, you will have to replace all text between <<...>> with the value that you have selected for your installation.
In order to prepare the installation, here is a table to be filled with the parameters of you installation:
| Parameter Name | Your Value | Example Value for tutorial |
|---|---|---|
my_servername | voparis-test | |
my_domain | obspm.fr | |
maintainer_email (1) | vo.paris@obspm.fr | |
my_datacenter-ivoid (2) | ivo://vopdc.obspm | |
creator_name (3) | Pierre Le Sidaner | |
logo_url (4) | http://padc.obspm.fr/img/logo/padc.png | |
authority_creationDate (5) | 2014-06-03T08:59:09.697573Z | |
authority_title | Paris Astronomical Data Centre | |
authority_shortname | PADC | |
authority_description |
| |
authority_url | http://padc.obspm.fr | |
organization_title | Observatoire de Paris | |
organization_description | Founded in 1667, the Observatoire de Paris is the largest national research center for astronomy. About 30% of all French astronomers are working in its five laboratories and its institute. Situated on the Paris, Meudon and Nançay campuses, they are all associated with the CNRS and, in many cases, with the major scientific universities in the Paris area. The research done at the Paris observatory covers all the fields of contemporary astronomy and astrophysics. | |
organization_url | http://www.obspm.fr |
2. DaCHS Registry Configuration
The Registry is the Information System of the Virtual Observatory (the yellow pages where all the services are registered). We describe a way to register your "authority ID" (description of the authority managing your resources) and the services provided by DaCHS. This operation shall be done only once. New services will be registered automatically.
First you need to create an identifier for your naming authority ID (ivo://my_datacenter)
The following lines have to be placed into the file /var/gavo/etc/defaultmeta.txt
publisher: <<my_datacenter>> publisherID: <<my_datacenter-ivoid>> contact.name: <<contact_name>> contact.address: <<contact_address>> contact.email: <<contact_email>> contact.telephone: <<contact_telephone>> creator.name: <<creator_name>> creator.logo: <<logo_url>> authority.creationDate: <<authority_creationDate>> authority.title: <<authority_title>> authority.shortName: <<authority_shortname>> authority.description: <<authority_description>> authority.referenceURL: <<authority_url>> authority.managingOrg: <<my_datacenter-ivoid>> organization.title: <<organization_title>> organization.description: <<organization_description>> organization.referenceURL: <<organization_url>>
Read http://docs.g-vo.org/DaCHS/opguide.html#defining-basic-metadata for more details
To be Continued...