ESA Gaia Archive TAP Jess Salgado Juan Gonzlez

  • Slides: 20
Download presentation
ESA Gaia Archive TAP+ Jesús Salgado, Juan González, Raúl Gutiérrez, Juan Carlos Segovia, Javier

ESA Gaia Archive TAP+ Jesús Salgado, Juan González, Raúl Gutiérrez, Juan Carlos Segovia, Javier Durán, Elena Racero, Sara Nieto, Bruno Merín, Christophe Arviset Gaia Archive Development Team - ESAC Science Data Center (ESDC) Issue/Revision: 1. 0 Reference: Gaia Archive Status: Issued ESA UNCLASSIFIED - Releasable to the Public

Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 3 ESA UNCLASSIFIED

Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 3 ESA UNCLASSIFIED - Releasable to the Public

Working with my tables in TAP 1. Volatile upload of tables is supported by

Working with my tables in TAP 1. Volatile upload of tables is supported by TAP/ADQL: UPLOAD/QUERY/DELETE Service URL: http: //gaia. esac. esa. int/tapserver/tap/ SELECT * FROM hipparcos AS hip JOIN TAP_UPLOAD. t 1 AS my. Table ON 1=CONTAINS(POINT('ICRS', hip. ra, hip. dec), CIRCLE('ICRS', my. Table. ra, my. Table. dec, 5. /3600. )) Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 4 ESA UNCLASSIFIED - Releasable to the Public

Crossmatch for my objects: TAP approach archive USER White Dwarfs TAP Upload & Query

Crossmatch for my objects: TAP approach archive USER White Dwarfs TAP Upload & Query Results Repeat operation n-times User Disk Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 5 ESA UNCLASSIFIED - Releasable to the Public

Gaia archive requirements for TAP Private Data Gaia Data Model Users should have their

Gaia archive requirements for TAP Private Data Gaia Data Model Users should have their own data/catalogues close to the archive Login must be supported Gaia has its own DM that is propagated and used for all the software developed in the consortium Crossmatch between Gaia catalogue and user catalogues to be executed as a user ADQL function Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 6 ESA UNCLASSIFIED - Releasable to the Public Private Queries The queries should be only visible for the user that execute them (for logged users)

Crossmatch for my objects: TAP+ approach & VOSpace+ archive TAP Upload USER White Dwarfs

Crossmatch for my objects: TAP+ approach & VOSpace+ archive TAP Upload USER White Dwarfs n TAP Queries Results USER User Disk Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 7 ESA UNCLASSIFIED - Releasable to the Public

Crossmatch for my objects: TAP+ approach & VOSpace+ & Saa. S archive TAP Upload

Crossmatch for my objects: TAP+ approach & VOSpace+ & Saa. S archive TAP Upload USER White Dwarfs n TAP Queries Results USER User Disk Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 8 ESA UNCLASSIFIED - Releasable to the Public

Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 9 ESA UNCLASSIFIED

Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 9 ESA UNCLASSIFIED - Releasable to the Public

Gaia Archive: TAP+ Interface Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 |

Gaia Archive: TAP+ Interface Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 10 ESA UNCLASSIFIED - Releasable to the Public

TAP+: Private Data Jobs Visibility (TAP/UWS) • ADQL queries are a description of ongoing

TAP+: Private Data Jobs Visibility (TAP/UWS) • ADQL queries are a description of ongoing scientific work so they have to be hidden • Jobs should allow a “non anonymous” execution • ADQL queries inside the jobs under this mode should be only accessible by the owner Persistent upload (TAP) • Data-centric architecture impose users data close to the server • Tables uploaded by user should be maintained at the server in a persistent way • Login/Authorization/server capabilities/sharing (VOSpace) TAP Schema (TAP) • TAP_SCHEMA per user Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 11 ESA UNCLASSIFIED - Releasable to the Public

Gaia Archive: TAP+ Schema Persistent Upload Server Crossmatch Table sharing Jesús Salgado | TAP+|

Gaia Archive: TAP+ Schema Persistent Upload Server Crossmatch Table sharing Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 12 ESA UNCLASSIFIED - Releasable to the Public

Gaia Archive Security q Single Sign-on through CAS server (both GACS and VOSpace) q

Gaia Archive Security q Single Sign-on through CAS server (both GACS and VOSpace) q Authorization through CAS proxy tickets q SAMP simple authentication q Full support on SAMP https for Web profile still pending at protocol level SAMP Authenticated SAMP Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 13 ESA UNCLASSIFIED - Releasable to the Public

Same URL Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 15

Same URL Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 15 ESA UNCLASSIFIED - Releasable to the Public

Astroquery: Load tables Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide

Astroquery: Load tables Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 16 ESA UNCLASSIFIED - Releasable to the Public

Astroquery: Synchronous query on an ‘on-the-fly’ uploaded table Jesús Salgado | TAP+| IVOA @

Astroquery: Synchronous query on an ‘on-the-fly’ uploaded table Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 17 ESA UNCLASSIFIED - Releasable to the Public

Astroquery: auth methods through login 1. Login (several methods) 2. User shared tables Jesús

Astroquery: auth methods through login 1. Login (several methods) 2. User shared tables Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 18 ESA UNCLASSIFIED - Releasable to the Public

TAP+ is TAP compliant Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 |

TAP+ is TAP compliant Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 19 ESA UNCLASSIFIED - Releasable to the Public

Conclusions q Single URL for public and secure methods q TAP+ (authenticated methods) is

Conclusions q Single URL for public and secure methods q TAP+ (authenticated methods) is extending a normal TAP q Added functionality accessible after login q Cookies (and other authentication mechanisms) are used to handle credentials and system behaves differently q Some requirements were needed into the protocol to create an operational archive: q Security q user DB schema q persistent upload q sharing q Possible draft to standardize this? Jesús Salgado | TAP+| IVOA @ Washington | 09/11/2018 | Slide 20 ESA UNCLASSIFIED - Releasable to the Public