...
- VizieR has a TAP interface but relies on the Vollt server, which is not the reference server in VESPA (DaCHS). As Vollt has different support of ADQL than is different from DaCHS', this requires adaptations adapting both on the portal and on the server.
- VizieR also handles a different directory tree. Although the VizieR TAP server presents a specific page for the EPN-TAP service (B/planets/epn_core), this also needs be supported in the VESPA portal.
- Ingestion of new catalogues in VizieR relies on parsing associated README files provided by authors.
- Level of description of the catalogues of interest is non-uniform and variable. In some cases, they only contain observation tables; at best the data listed in such tables are available as text files in a sub-directory, sometimes but not always with a fits-formatting script. Of course there is no fixed RA-DEC location, except for exoplanets.
...
- Fixes on VizieR side, in particular equivalent of DaCHS' lower function (cds_lower)
- Related adaptations on the portal: cds_lower syntax
- support for value lists in this case (eg, target_class), on portal side
- Support for column ordering in portal
- Check consistency with EPN-TAP2 doc, in particular UCDs for VOTable output (PR document, July 2021)
- Declare in local VESPA registry
- Register VizieR_planets in IVOA registry
- Improve catalogue description according to EPNCore rules - target_class at least should be identified for publication.
...