IVOANov3RegistryEtherpad < IVOA

<div id="magicdomid2"> *gather.town registry workshop, Nov 3, 2021.* </div> <div id="magicdomid3"> *pyvo and data discovery in the registry, working session on changes.* </div> <div id="magicdomid5">Notes: Theresa Dower</div> <div id="magicdomid6">Main presentation: Tess Jaffe / Markus Demleitner</div> <div id="magicdomid7">Attendance: 14</div> <div id="magicdomid9"> *Background:* </div> <div id="magicdomid10">    </div> <div id="magicdomid11">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.</div> <div id="magicdomid13">Issue that spawned this: https://github.com/astropy/pyvo/issues/238 </div> <div id="magicdomid14">Markus' branch with changes: https://github.com/msdemlei/pyvo/tree/add-discoverdata </div> <div id="magicdomid15">NAVO's notebooks: https://github.com/nasa-navo/navo-workshop </div> <div id="magicdomid18"> *Major changes with the discover data branch:* </div> <div id="magicdomid19">   Returned columns are entirely changed; returns resources vs services. </div> <div id="magicdomid20">   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. </div> <div id="magicdomid23"> *Challenges and obstacles :* </div> <div id="magicdomid24">
   * Tess: Most changes can be rewritten around in the notebooks. 1 issue - if we're not setting #aux inclusion as the default (a good idea, because jargon), we need a way to include these capabilities: in some new function? without jargon?
</div> <div id="magicdomid25">
   * Tom & Adrian: current search requires a lot of understanding of registry internals.... is this an opportunity to create a higher-level interface?
</div> <div id="magicdomid26">
   * We are moving from plain programmatic access to interactive access, with the notebooks.
</div> <div id="magicdomid27">
   * Compatibility: do old queries from old notebooks return the same data?
</div> <div id="magicdomid28">
   * We could register the notebooks! http://dc.g-vo.org/VOTT per https://ivoa.net/documents/Notes/EDU/index.html
</div> <div id="magicdomid29">
   * Hendrik: The type for this may have a last-checked timestamp to curate for stale resources.
</div> <div id="magicdomid31"> *Markus reviews suggested new workflow:* </div> <div id="magicdomid32">       "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?) </div> <div id="magicdomid33">       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?)</div> <div id="magicdomid35"> *Takeaways:* </div> <div id="magicdomid36">
   * #includeaux version already in pyvo regsearch from first stab at this should be removed when we have a better solution, no matter what it is
</div> <div id="magicdomid37">
   * This could be an opportunity for higher-level data discovery workflow and functionality?
</div> <div id="magicdomid38">
   * Having parallel functionality is probably necessary, will need documentation/communication about the different modes.
</div> <div id="magicdomid39">
   * Action on ???: Test backward compatibility: not just unit tests but existing queries and workflows
</div> <div id="magicdomid40">
   * Action on NAVO: Translate notebooks to Markus' workflow and see what works well, see what works best
</div> <div id="magicdomid41">
   * Action on Theresa: Attempt registering notebooks http://dc.g-vo.org/VOTT per https://ivoa.net/documents/Notes/EDU/index.html
</div> <div id="magicdomid42">
   * Action on Theresa: follow up on Note, other interest in this recently. Endorsed note or doc?
</div>
This topic: IVOA > WebHome > WebPreferences > InterOpNov2021 > IVOANov3RegistryEtherpad
Topic revision: r1 - 2021-11-11 - TheresaDower