gather.town registry workshop, Nov 3, 2021. pyvo and data discovery in the registry, working session on changes. Notes: Theresa Dower Main presentation: Tess Jaffe / Markus Demleitner Attendance: 14 Background: Tess Jaffe & NAVO workshop authors/runners for AAS have a series of use cases for registry search. The session is a mix of discussion and collaborative test on a jupiter hub. We are covering differences between existing registry search behavior and proposed data discovery, with the goal of hiding some registry complexity without removing existing functionality. Issue that spawned this: https://github.com/astropy/pyvo/issues/238 Markus' branch with changes: https://github.com/msdemlei/pyvo/tree/add-discoverdata NAVO's notebooks: https://github.com/nasa-navo/navo-workshop Major changes with the discover data branch: Returned columns are entirely changed; returns resources vs services. Change in approach/workflow: we're not looking for 'services' we're looking for resource info and can drill down to the same interface level. Challenges and obstacles :
Markus reviews suggested new workflow: "Searching for services was a mistake" (but much of the VO still relies on it). Change to search pattern to start searching for resources, then get_service, which will constrain the type (and allow service-specific functionality?) Tess: This doesn't help much for use case where we know we're looking for TAP for this data. (But we could construct a query for that in either of these workflows?) Takeaways:
|