InterOpJune2025Registry < IVOA

---+ Registry Sessions at the [[InterOpJune2025][IVOA June 2025 Interoperability Meeting]]

[ [[InterOpJune2025][back to main programme page]] ]

---++ *DRAFT* Schedule
| *Registry Session #1: Tuesday June 3, 2025 @11:00-12:30 ET (Session #3) Room 1309* ||||
| *Speaker* | *Title and Abstract* | *Materials* | *Time* |
| Renaud Savalle (PADC) (remote) | *Intro and Documents Status* <br />Review of current WG work | | 5 |
| Tess Jaffe (NAVO)<br />(in person) | <b>The new Registry !GitHub Project board and Spring Cleaning hackathon objectives<br /></b>Presentation of Registry Session #2: Spring Cleaning Hackathon | | 5 |
| Hendrick Heinl (INAF) <br />(remote) | *Update about the plans for a 2026 Registry good practices event for data providers* <br />TBC | | 10+5 |
| Renaud Savalle (PADC)(remote) | *StandardRegExt and !OpenAPI* <br />I will give a short summary of the [[StandardsRegExt11RFC][StandardRegExt-1.1 RFC]] status and propose a way to embed !OpenAPI specifications to describe input/input parameters of a standard. | | 5+5 |
| Gilles Landais (CDS)<br />(remote) | *Use of !VODataService for !VizieR records* <br />TBC | | 10+5 |
| Markus Demleitner (Univ. Heidelberg/GAVO)<br />(in person) | *Metadata for continually updated resources* <br />The Virtual Observatory contains quite a few resources that are continuously updated (observatory archives, VOEvent streams, etc). One question this raises is: what would be a useful temporal coverage specification for these? Perhaps more importantly: Can we come up with some metadata that lets clients decide for which resources a later re-visit will likely yield different results? | | 15+5 |
| All | *Discussion* <br />topics TBC | | 20 |

| *Registry Session #2: Spring Cleaning Hackathon: Thursday June 5, 2025 @14:00-15:30 ET (Session #12) Room 1309* ||||
| *Speaker* | *Title and Abstract* | *Materials* | *Time* |
| Tess Jaffe (NAVO)<br />(in person)  | The Registry Working Group has begun to keep a project board on !GitHub where we can track and discuss issues with the metadata in the Registry that will make services and/or data harder to find. Please come to our very first hackathon at the Interop if you are interested in getting hands-on with how to fix issues in your own services' metadata or if you are interested in contributing to the (currently very simple) scripts that do the checks. | [[https://github.com/ivoa/registry-housekeeping][GitHub repo]] | 90 |

---++ Relevant Links and Information

   * Moderator: IVOA.RenaudSavalle
   * Note Taker: IVOA.TessJaffe
   * Collaborative Notes: TBC

<!--
      * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup
-->
This topic: IVOA > WebHome > IvoaEvents > InterOpJune2025 > InterOpJune2025Registry
Topic revision: r1 - 2025-05-27 - RenaudSavalle