NAVO registry missing SIA services

[trjaffe]

As described in #1, the NAVO registry is returning 0 to this query:

"select count(*) as cnt from rr.capability where standard_id like '%sia%'"

Most likely it's not the right query. This is just a proof of concept issue.

[trjaffe]

I take it back. I think this is an issue in the MAST RegTAP service:

querystart = """
    select * from rr.capability 
    where ivoid = 'ivo://archive.stsci.edu/sia/galex' 
    and standard_id ilike 
    """
## Works
galex_sia = navo_regtap.search(f"{querystart} '%/std/sia'")

## Does not work without forward slash before 'std'?
galex_sia = navo_regtap.search(f"{querystart} '%std/sia'")

[trjaffe]

This is the wrong RegTAP service? But it's the one still listed in http://rofr.ivoa.net/. But as Markus pointed out, https://vao.stsci.edu/RegTAP/TapService.aspx works.

[msdemlei]

On Mon, Mar 03, 2025 at 07:06:41AM -0800, trjaffe wrote: trjaffe left a comment (ivoa/registry-housekeeping#4) This is the wrong RegTAP service? But it's the one still listed in http://rofr.ivoa.net/. But as Markus pointed out, https://vao.stsci.edu/RegTAP/TapService.aspx works.

Hm... so, I just pulled it from the Registry, as in from pyvo import registry print(registry.search(datamodel="regtap")) Not sure what the RofR does, but I'd suspect Theresa should know all the history.

[trjaffe]

So where does this come from? (From http://rofr.ivoa.net/)

[tsdower]

Hello!

MAST is in a slightly awkward spot moving all TAP and registry content from C# services on vao.stsci.edu service to new Python infrastructure. For RegTAP, the preferred URL is now https://mast.stsci.edu/vo-tap/api/v0.1/registry. OAI-PMH is still on the old system.

Projects I am currently working on with my developer hat on include creating a new OAI-PMH service in Python with Joshua and hopefully folks who just built a publishing registry at NOIRLab, and moving traffic that used to go to vao.stsci.edu TAP services to the new infrastructure. I am working on a pyvo PR to update the links once CI passes. I'm currently working in https://github.com/tsdower/pyvo/tree/update_MAST_alt_registry

[tsdower]

As it does pertain to this issue, both vao.stsci.edu/regtap and mast.stsci.edu/vo-tap/api/v0.1/registry do access the same database and share some ADQL parsing code, so it should be expected they give the same results.

[trjaffe]

Huh. Then it's the newer service that has a parsing issue? This gives zero in the new service and 410 in the old URL.

navo_regtap = vo.dal.TAPService('https://mast.stsci.edu/vo-tap/api/v0.1/registry')
query = "select * from rr.capability where standard_id like '%sia%'"
len(navo_regtap.search(query))

[tsdower]

I just picked this back up, and while I haven't fixed the issue yet, the breaking factor appears to be queries with more than one % wildcard. I suspect some python escaping problem.

In any case, the following finds all sia1, sia2, and sia#aux capabilities.
navo_regtap = vo.dal.TAPService('https://mast.stsci.edu/vo-tap/api/v0.1/registry') navo_regtap.search("select * from rr.capability where standard_id like 'ivo://ivoa.net/std/sia%'")