Add a UAT registry constraint

[msdemlei]

This PR adds a constraint for doing keyword searches over the controlled vocabulary of the terms supposed to be in rr.res_subject. The rationale and a lot more is discussed in https://blog.g-vo.org/a-new-constraint-class-in-pyvo-s-registry-api-uat.html

[codecov]

Codecov Report

Attention: Patch coverage is 34.61538% with 17 lines in your changes missing coverage. Please review.

Project coverage is 82.30%. Comparing base (093f2d2) to head (a89d1d0).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pyvo/registry/rtcons.py	34.61%	17 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #649      +/-   ##
==========================================
- Coverage   82.47%   82.30%   -0.17%     
==========================================
  Files          72       72              
  Lines        7480     7506      +26     
==========================================
+ Hits         6169     6178       +9     
- Misses       1311     1328      +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bsipocz]

Some comments for the failing tests

[bsipocz]

This won't work, the #doctest commands should be added at the end of the lines (each one of them) that are affected. But this example already has it.

[bsipocz]

Can we have some tests that query the remote service rather than the mock version? (OTOH, if you say the doctests should be enough for that, I would be signing off on it)

[bsipocz]

Somehow this throws an error, even though cepheid-variable-stars are in the list on the referred website

_____________________________ [doctest] index.rst ______________________________
102 constraints is generally preferable with more complex queries.
103 An advantage of using explicit constraints is that you can pass
104 additional parameters to the constraints.  For instance, the UAT
105 constraint can optionally expand your keyword to narrower or wider
106 concepts.  When looking for resources talking about Cepheids of all
107 kinds, you can thus say:
108 
109 .. doctest-remote-data::
110 
111   >>> resources = registry.search(
UNEXPECTED EXCEPTION: DALQueryError: cepheid-variable-stars does not identify an IVOA uat concept (see http://www.ivoa.net/rdf/uat).
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.11.11/x64/lib/python3.11/doctest.py", line 1355, in __run
    exec(compile(example.source, filename, "single",
  File "<doctest index.rst[4]>", line 2, in <module>
  File "/home/runner/work/pyvo/pyvo/.tox/py311-test-alldeps-online/lib/python3.11/site-packages/pyvo/registry/rtcons.py", line 713, in __init__
    raise dalq.DALQueryError(
pyvo.dal.exceptions.DALQueryError: cepheid-variable-stars does not identify an IVOA uat concept (see http://www.ivoa.net/rdf/uat).
/home/runner/work/pyvo/pyvo/docs/registry/index.rst:111: UnexpectedException
=========================== short test summary info ============================

[msdemlei]

On Thu, Feb 13, 2025 at 09:20:00AM -0800, Brigitta Sipőcz wrote: > @@ -154,7 +170,7 @@ interactive data discovery, however, it is usually preferable to use the And to look for tap resources *in* a specific cone, you would do -.. doctest-remote-data:: +.. doctest-remote-data:: # doctest: +IGNORE_OUTPUT This won't work, the #doctest commands should be added at the end of the lines (each one of them) that are affected. But this example already has it.

Ah... hu... Sorry about this. I wonder why I felt the need to shut this one up, then. I've reverted that change.

Can we have some tests that query the remote service rather than the mock version? (OTOH, if you say the doctests should be enough for that, I would be signing off on it)

Well... I would have preferred using a mock vocabulary because we shouldn't be testing the UAT as such. But as the comment to the following commit says, having artificial mock vocabularies is tricky due to the heavy caching involved. Hence, the tests now to use the remote vocabulary, and the expense of always pulling the UAT (700k in desise) in new installations. That's moderately painful for CIs (but free for local tests). But then the doctest would have pulled the full UAT anyway, so that's what it is now.

+ >>> resources = registry.search( + ... registry.UAT("cepheid-variable-stars", expand_down=3)) Somehow this throws an error, even though `cepheid-variable-stars` are in the list on the referred website

Yeah, that was a stale cache with the mock vocabulary. Thanks for the early review. It think this PR is now good to go. Could you have another look? Thanks!

[bsipocz]

The test failures look relevant, lots of VocabularyErrors