Skip to content

Cite Qserv and ObsTAP #23

Cite Qserv and ObsTAP

Cite Qserv and ObsTAP #23

Workflow file for this run

name: CI
"on": [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # full history for metadata
submodules: true
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.10"
- name: Python install
run: |
python -m pip install --upgrade pip
python -m pip install "lander<2.0.0"
- name: Login to Docker Hub
uses: docker/login-action@v1
with:
username: sqrereadonly
password: ${{ secrets.DOCKERHUB_SQREREADONLY_TOKEN }}
- name: TeX build
run: |
docker run --rm -v `pwd`:/workspace -w /workspace lsstsqre/lsst-texmf:latest sh -c 'make'
- name: Landing page upload
if: ${{ github.event_name == 'push' }}
env:
LTD_PASSWORD: ${{ secrets.LTD_PASSWORD }}
LTD_USERNAME: ${{ secrets.LTD_USERNAME }}
run: |
lander --upload --pdf P920.pdf --ltd-product dmtn-300 --lsstdoc "P920.tex" --author "Tim Jenness" --author "Stelios Voutsinas" --author "Gregory Dubois-Felsmann" --author "Andrei Salnikov" --abstract "The IVOA Simple Image Access version 2 protocol defines an easy way to provide community access to a collection of data. At the Vera C. Rubin Observatory we currently enable ObsTAP access to our data holdings via an ObsCore export or view of our Data Butler repositories. This approach does come with some deployment constraints, such as requiring pgsphere and compatibility with our CADC TAP implementation, so recently we decided to see whether we could instead provide an SIAv2 service that talks directly to our Data Butler. Here we describe our motivation, implementation strategies, and current deployment status, as well as discussing some metadata mismatches between the Butler data models and SIAv2."