[Dachs-support] TAP only catalogue
Yannick Roehlly
yannick.roehlly at lam.fr
Fri Apr 15 12:40:00 CEST 2022
Hi Markus,
As usual, thanks for the quick answer.
In fact, I changed my mind and I'm publishing a cone search as it may be
useful for scientists to query just a location in the simulation. I just added
a note in the service description stating that the positions are not actual
ones.
Nevertheless, my initial concern is an interesting one.
Le vendredi 15 avril 2022, 11:45:04 CEST Markus Demleitner a écrit :
> 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).
I didn't know I could add a publish tag at the table level.
First, I thought about using a nullCore after looking at your gdr2mock
descriptor. Then I switched to a dbCore that allowed be a add a form on the
web interface. Then I switched to the full scsCore. ;-)
> 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.
Well, that's quite interesting and I will have a look at that.
I take the opportunity to ask more questions. ;-)
I used to publish the form renderers as `ivo_managed` in addition to
`local` as it's in the SCS RD skeleton. Is this useful to do that?
I mean it won't be used by software like Topcat and the only use case
I can see is someone querying the registry to get the link to the web
forms, and I think it's not easily feasible.
When a column is a Boolean and is used in the web form it appears as an
unchecked box (i.e. meaning false). If nothing is changed in the form, the
result page states that the column is used as a parameter (e.g. `qFlag:
False`) but the condition is not taken into account in the results. If I check
the radio button, the parameter is changed to `qFlag: True` and the results
are correct.
I think I raise the issue some times ago because it was impossible to use a
Boolean column in the search form as DaCHS was giving the proper answer with
the false value and it was impossible to query for "any value". Maybe you
changed something but now it's impossible to query on the false value.
Would it be difficult to render a Boolean column with radio buttons or a
select with "true / false / any"? Note that it is not a big issue.
Thanks again for the answer.
Best,
Yannick
[1] https://dachs-doc.readthedocs.io/ref.html?highlight=index#element-index
--
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
-- Isaac Asimov
More information about the Dachs-support
mailing list