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: VESPA- WP6-2-007-TD-v 0.1
EPN-TAP Installation for VESPA Data Provider Tutorial — Part 2
Date: 2016-03-21
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 | VESPA-WP6-2-007-TD-v0.1(33) |
Delivery date |
|
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: This tutorial describes first how to register your newly installed DaCHS server into the IVOA registry. It then introduces the various type of databases and links to corresponding tutorials. |
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 | ................................................................................ | vo.paris@obspm.fr |
authority-ivoid (1) | ................................................................................ | ivo://vopdc.obspm |
creator_name | ................................................................................ | Pierre Le Sidaner |
logo_url | ................................................................................ | http://padc.obspm.fr/img/logo/padc.png |
authority_creationDate | ................................................................................ | 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 |
(1) This ivo-id is that of your naming authority. If your institution is not registered you should put ivo://<<authority_name>>/org (see Tutorial Part 1).
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 configuration file:
sudo pico /var/gavo/etc/defaultmeta.txt
publisher: <<my_datacenter>> publisherID: <<authority-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.managingOrg: <<my_datacenter-ivoid>> authority.referenceURL: <<authority_url>> authority.description: <<authority_description>> organization.title: <<organization_title>> organization.referenceURL: <<organization_url>> organization.description: <<organization_description>>
Then you have to update the userconfig.rd file in the same directory. This file does not exist yet on a fresh installation, so you have to create it. You first need to switch to the root user, and then create the file:
cd /var/gavo/etc/ su [root password is asked] gavo admin dumpDF //userconfig > userconfig.rd exit
Then open the registry-interfacerecords section of the userconfig.rd file for editing
sudo pico userconfig.rd
And in the file, remove the {UNCONFIGURED} text, so that the content is:
[...]
<!-- ================================ Registry Interface ============ -->
<STREAM id="registry-interfacerecords">
<doc>
These are services and registry records for the registry interface
of this service.
Even if together with defaultmeta, this will just work, keep
these elements in your etc/userconfig.rd.
The metaString macros in here generally point into defaultmeta.
Replace them with whatever actual text applies to your site; we
will work to do away with defaultmeta.txt.
</doc>
<resRec id="authority"> <!-- ivo id of the authority is overridden in
nonservice.NonServiceResource -->
<meta>
creationDate: \\metaString{authority.creationDate}
title: \\metaString{authority.title}
shortName: \\metaString{authority.shortName}
subject: Authority
managingOrg: \\metaString{authority.managingOrg}
referenceURL: \\metaString{authority.referenceURL}
identifier: ivo://\getConfig{ivoa}{authority}
sets: ivo_managed
</meta>
<meta name="description">
\\metaString{authority.description}
</meta>
</resRec>
<resRec id="manager"> <!-- the organisation running this registry -->
<meta>
resType: organization
creationDate: \\metaString{authority.creationDate}
title: \\metaString{organization.title}
subject: Organization
referenceURL: \\metaString{organization.referenceURL}
identifier: ivo://\getConfig{ivoa}{authority}/org
sets: ivo_managed
</meta>
<meta name="description">
\\metaString{organization.description}
</meta>
</resRec>
[...]
In case your organisation is already registered, you need to remove the <resRec id="manager"> ... </resRec> element.
Once this is done, we can publish your registry interface, by issuing the following command:
sudo gavo pub //services
Read http://docs.g-vo.org/DaCHS/opguide.html#defining-basic-metadata for more details
Assessing your dataset
Depending on your dataset (just a series of files, number for data processing levels, presence of metadata, format of data, existing relational database...) various processing may be required. In order to prepare the sharing with EPN-TAP, here is a check list of what you need:
- Public access to the data files you want to share: either on your server, or on a remote server with a publicly accessible URL (e.g., at NASA/PDS or ESA/PSA).
- Metadata (relevant for EPNcore) for each file
- Preview image for each file
Select a suitable data format if the current format is recommended by VESPA.
To be Continued...