ObsTAP.creator_name multiplicity

[Louys Mireille]

Hi Guillaume , Hi DMers,

Obscore V1.0 initially considers simple data products.
It seems you are dealing with products combined from several observations.
Could you provide an example so that we could check what kind of 
multiplicity you have to handle?
In Obscore , the N to M relation Observation <---------> 
Observation.Dataset was not fully described .
ObservationDatasets stemming from the Same Observation were supposed to 
share the same ObservationID.

The same situation occurs in the CTA project.
This is an interesting issue to take into account but needs more details 
to be checked against existing models.
ImageDM disentangle the two concepts of Observation vs Observation 
dataset ( data products).

Cheers , Mireille.


Le 09/12/2014 09:34, Guillaume Mella a écrit :
> Hi,
>
>   We are building a portal of observations from multiples facilities 
> on top of ObsTAP.
>
>
> One of our issue is that given some inputs we would have to ingest 
> some records with multiple names in the 'obs_creator_name' column.
> But the multiplicity of this field is not addressed in the ObsTAPV1.0 
> doc (B3.1 and B3.6 are duplicated).
> This column renamed 'creator' in VODML also get a 0..1 multiplicity 
> looking at 
> https://volute.googlecode.com/svn/trunk/projects/dm/vo-dml/models/obscore/ObsCore.html#DataID.Creator 
> .
>
>
> As a first workaround, we plan to use the same convention proposed in 
> the creator_seq column of the RegTap.
> If it is a wrong choice, why and what would be the proper guideline to 
> follow ?
>
> Cheers,
> -- 
> Guillaume
>


-- 
Dr Mireille Louys, assistant professor
Ecole Telecom physique Strasbourg, Icube
CDS, Observatoire de strasbourg, France