Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-2887

Deploy a TAP service to extract IVOA metadata in Rucio

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      An externally accessible service that queries Rucio metadata & returns an IVOA compliant response.

      Show
      An externally accessible service that queries Rucio metadata & returns an IVOA compliant response.
    • 1
    • 1
    • 0
    • Team_MAGENTA
    • Sprint 5
    • Hide

      Git repository with dockerised sandbox: https://gitlab.com/ska-telescope/src/ska-rucio-ivoa-integration

      Demo illustrating sandbox usage: https://confluence.skatelescope.org/display/SRCSC/2022-11-17+SRC+ART+System+Demo+16.5

      Example of external TAP service with minimal dummy data: https://srcdev.skatelescope.org/ivoa/tapserver/tap (change output to HTML and e.g. query: "select * from ivoa.obscore")

      Show
      Git repository with dockerised sandbox: https://gitlab.com/ska-telescope/src/ska-rucio-ivoa-integration Demo illustrating sandbox usage:  https://confluence.skatelescope.org/display/SRCSC/2022-11-17+SRC+ART+System+Demo+16.5 Example of external TAP service with minimal dummy data: https://srcdev.skatelescope.org/ivoa/tapserver/tap  (change output to HTML and e.g. query: "select * from ivoa.obscore")
    • 20.4
    • Stories Completed, Outcomes Reviewed, Demonstrated, Accepted by FO
    • PI24 - UNCOVERED

    • SRC-DM SRC-DataAccess

    Description

      A fundamental requirement for SRCs will be the ability to expose externally accessible search and retrieve interfaces to data ingested into the distributed data management (DDM) ecosystem. For this purpose, there already exists a standardised set of astronomical interfaces and protocols under the umbrella of the International Virtual Observatory Alliance (IVOA). As such, any DDM solution being considered should ideally be capable of supplying metadata conforming to standards set out by the IVOA.

      Through development recently undertaken by Cyan team, Rucio is now capable of storing metadata in standalone, external resources via plugins for e.g. postgresql, mongo. This functionality should enable a service to be deployed that formats and serves this metadata in a way that is compatible with IVOA standards.

      As a step towards this goal, an example TAP service (provided by the Tap Library) has been deployed to query mock data. Following on from SP-2825, this now needs to be extended to query a "production" database, connected to the SKAO Rucio prototype. This requires deploying the TAP service into a "production" environment.

      As a stretch goal, it would be prudent to consider how the IVOA ObsCore data model can best represent Rucio managed data. Of particular importance is how best to handle replicas - the ObsCore DM defines only a single `access_url`, but a Rucio DID can have many.

      Attachments

        Issue Links

          Structure

            Activity

              People

                Y.Grange Grange, Yan
                Y.Grange Grange, Yan
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete24.0
                  Total24.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel