[Dachs-support] TAP only catalogue

Markus Demleitner msdemlei at ari.uni-heidelberg.de
Fri Apr 15 11:45:04 CEST 2022


Hi Yannick,

On Thu, Apr 14, 2022 at 08:39:08PM +0200, Yannick Roehlly wrote:
> I have a simulated catalogue.  There's no need to use a simple cone search on 
> it as the positions are simulated.  If I write a resource descriptor as I do 
> usually for catalogues omitting the SCS part, I end up with a descriptor with 
> no service associated.
> 
> Will it appear on the registries? Does it do something when I
> "dachs publish"?

Actually, it will, kind of, as long as the TAP service is published.
That is because the table metadata will go with the TAP service's
metadata.  But that is rather weak metadata; apart from the column
metadata itself, that's the title and the description of the table
(and hence no authors, subject, source, coverage, etc).

Hence, for almost all resources of this kind, you should put
<publish sets="ivo_managed,local"/> (the "local" puts a metadata link
on the root page; if you don't need/want that, a simple <publish/>
would do, too) into the table element
(http://docs.g-vo.org/DaCHS/ref.html#element-publish-data).

By the way, if you have a more complex schema, you can build a data
element with all tables belonging to it and publish that (cf., e.g.,
http://svn.ari.uni-heidelberg.de/svn/gavo/hdinputs/arigfh/q.rd, the
gfhtables element) -- that way, you have one resource in the registry 
with all tables belonging to the schema (or "data model", if you
will) in one place.

As usual, to tell DaCHS you mean it, you still have to run dachs pub
q once on such an RD, and it's only legal to do that if the TAP
service itself is published, because the table (or data) record will
have a reference to the TAP service.

Thanks,

           Markus


More information about the Dachs-support mailing list