Obscore dataproduct_type question

[Patrick Dowler]

Guilty as charged :-)

Our underlying data model (CAOM2) has catalog as a valid type and I
recall some of us trying to get catalog into the vocabulary back
before 1.0.... I can easily fix this because ObsCore is a view on
CAOM2, with the cost being that people can't find all the products via
ObsCore. But for ASKAP, if they implement ObsCore directly then they
would be left with no way to provide discovery of catalog products.

The DM rationale is that ObsCore is a list of products (it is a
flattened view of Observation+Product where there is a 1..* relation).
As such, there are certainly other kinds of things that can be created
from data (besides just more data). Do such things belong in ObsCore?
I obviously think they do so IMO we should add to the vocabulary and
I've either been meaning to request it or forgot about that little
non-compliance.

The alternative that I see if that access to the catalog would be a
link in a DataLink response with semantics="derivation"... and then
probably augment the DataLink vocabulary to be able to ay catalog...
and then still not be able to discover them via a data discovery
query. DataLink *is* awesome and all, but that doesn't seem so great.

So: can we add "catalog" to the ObsCore-1.1 vocabulary for
datapoduct_type? +1 from me



On 15 April 2016 at 05:21, Mark Taylor <M.B.Taylor at bristol.ac.uk> wrote:
> James,
>
> it looks like you're not the only one to hit this.  If I use the
> ObsTAP service at http://www.cadc.hia.nrc.gc.ca/tap to run:
>
>    select distinct top 100
>           dataproduct_type, obs_collection
>    from ivoa.obscore
>    where dataproduct_type not in
>        ('image', 'cube', 'spectrum', 'sed',
>         'timeseries', 'visibility', 'event')
>
> I get
>
>    +------------------+----------------+
>    | dataproduct_type | obs_collection |
>    +------------------+----------------+
>    | catalog          | APASS          |
>    | catalog          | CFHTTERAPIX    |
>    | catalog          | JCMT           |
>    +------------------+----------------+
>
> (note this is one of the tests run by taplint, currently failing at CADC).
>
> Mark
>
> On Fri, 15 Apr 2016, James.Dempsey at csiro.au wrote:
>
>> Hi,
>>
>> In ObsCore v1.0 and 1.1 the dataproduct_type field has a defined list of values. We currently advertise our ASKAP catalogue data products in our ObsCore table, but have to leave the dataproduct_type field blank for these records as none of the possible types match.
>>
>> Has the inclusion of a catalogue type been considered before? If not, would it be possible to include in ObsCore v1.1?
>>
>> Cheers,
>> James Dempsey
>>
>
> --
> Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
> m.b.taylor at bris.ac.uk +44-117-9288776  http://www.star.bris.ac.uk/~mbt/



-- 
Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada