See also VESPA Data provider on-boarding process
| Service | Institute name (for gitlab) | Server name (host) | Service name | Status (Feb2022) | Contact (name, email) |
|---|---|---|---|---|---|
SPHERE asteroid images and shape models (LAM, Marseille) | LAM | Pierre Vernazza, | |||
MOVIS asteroids NIR colors (AIRA, Bucarest) | AIRA | aira_dachs (TBC) | movis | Marcel Popescu, | |
PDS PPI (UCLA + Iowa Univ) | PDS-PPI | https://vo-pds-ppi.igpp.ucla.edu/tap | ppi (test service) | • Many services installed on server (65 as of end of April) - any reason to keep PDS datasets separated? Try and group if possible • Only one service on gitlab | Steve Joy, In Sook Moon, |
Sunspots and coronal holes catalogues (ROB, Brussels) | ORB | https://sidc.be/VESPA/DaCHS/tap | user_sunspot_group | • service installed on server | |
| https://sidc.be/VESPA/DaCHS/tap | user_sunspot_drawing | • service installed on server • Initial version on gitlab | |||
Asteroid data catalogues - MP3C (OCA, Nice) | OCA | mp3c_best | • service installed on server | Marco Delbo, | |
Europlanet VESPA: Various services at IRAP (GSO, Toulouse) | OMP | cdpp-epntap.irap.omp.eu | transplanet | • published, to be upgraded | Jean-Michel Glorian, |
| cdpp-epntap.irap.omp.eu | illu67p | • published, to be upgraded | |||
| cdpp-epntap.irap.omp.eu | amdadb | • published, to be upgraded | |||
| climso.irap.omp.eu | climso-db | • published, to be upgraded | |||
| http://polarbase.irap.omp.eu (Not yet Dachs) | polarbase_planets | ||||
Europlanet TA: data from lab and field studies | VU-Amsterdam | vespa.labs.vu.nl | ta_test | Gareth Davies, | |
| Europlanet ML (IWF, Graz) | IWF | epn-tap.oeaw.ac.at | mercury_mag_boundaries | • Initial version on gitlab | Ute Amerstorfer, |
| epn-tap.oeaw.ac.at | impex_epn20 | • published, to be upgraded + change service name? | |||
| epn-tap.oeaw.ac.at | vexmag_epn20 | • published, to be upgraded + change service name? | |||
| Europlanet VESPA: OATS (INAF, Trieste) | OATS | vespa.ia2 | artecs | Marco Giardino, | |
| _ | ndcs |
Notes:
1) Find a handy and explicit title for your VO service - this is also used as a directory name under Unix, so keep it simple: this is an acronym rather than a name. You will also define a long name in another place.
No particular syntax rule applies, but special characters (. # - , " ' etc) can't be included. This also has political exposure, so don't call it Apollo13 if you were not the PI 
(you should append your project / institute name at least).
See the list of services for inspiration: http://vespa.obspm.fr (in green boxes, presented as: title - long name)
(service_title is used in several situations: this is the service name in queries; the directory name where your service is located on your server; a namespace in the gitlab; and it appears in the table itself to be used in call back mechanisms, if needed).
2) The same rules apply to your server name. You also want to keep it general (it may host other services in the future) and referring to the hosting institute - please identify if this refers to team/institute/University or Observatory/local data center (in particular in France (institute vs CER) but not only). Same thing for Institute name on voparis-gitlab.
In addition, some teams include "epntap" in the server name, other include "tap". But the server has the capacity to host other types of services, so including "dachs" is probably a better choice.